Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add method to check whether region crosses into airgap #387

Open
JackB-Ansys opened this issue Sep 25, 2024 · 2 comments
Open

Add method to check whether region crosses into airgap #387

JackB-Ansys opened this issue Sep 25, 2024 · 2 comments
Labels
enhancement New features or code improvements

Comments

@JackB-Ansys
Copy link
Collaborator

JackB-Ansys commented Sep 25, 2024

📝 Description of the feature

Add functionality to PyMotorCAD to be able to detect the case where a region crosses the rotor/stator boundary into airgap

Throw an exception if this happens

💡 Steps for implementing the feature

No response

🔗 Useful links and references

No response

@JackB-Ansys JackB-Ansys added the enhancement New features or code improvements label Sep 25, 2024
@jgsdavies
Copy link
Collaborator

@matthewAnsys is this fixed with the latest Motor-CAD release geom checks?

@EmilCallerfjord
Copy link

Hello @jgsdavies , @matthewAnsys.

Any updates regarding this feature?

How would I go on and implement this geometry airgap check when using OptiSLang? Currently I have created a script where I iterate the coordinates in my entities and if they cross the rotor diameter in polar coordinates an error gets raised. But it is still possible to run simulations.

I was thinking of somehow writing "success = 0" in the optiSlang script when my geometry enters the airgap but I do not know how to use the adaptive template python script inside MotorCAD together with the Optimization Script created for optiSLang.

Best regards,
Emil

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New features or code improvements
Projects
None yet
Development

No branches or pull requests

3 participants