Replies: 1 comment 1 reply
-
Hello Sebastian, Yes I removed it because it was not possible to generalize it for HoleUD since the definition was not clear. It implicitly assumed that all magnets are rectangular and that "height" makes sense. Let's also imagine a Hole with several magnets with different height, what should be returned ? I think that one day we will have a comp_height_active method for Hole that would work the same way as the one for Slot works (which would be a step forward using Holes as closed slot): The distance between two circles that contains the active part. For instance in pyleecan/Functions/FEMM/comp_FEMM_dict.py, I now use comp_height instead of get_magnet_height. Best regards, |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hello @BonneelP ,
with c483b58 you removed the get_magnet_height methods for HoleMx.
Can you recall if this was intentional?
Best regards, Sebastian
Beta Was this translation helpful? Give feedback.
All reactions