-
Notifications
You must be signed in to change notification settings - Fork 57
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
Unrecognised model in goland test case #143
Comments
Hi Alessandro, Thanks for raising this. This is a result of us changing the input settings and forgetting to update the input files accordingly...the simulation will run fine, since it is just ignoring legacy settings that were previously used and that no longer affect the solution process. I will update it but in the mean time you can keep running it as is. If you encounter more of these warnings (you very well may) just ignore them. We are going to turn them into errors so hopefully we'll get rid of all those for the next stable release. Thanks and best regards, |
Hello Norberto, Thanks again and best regards, |
Hi Alessandro, These are the updated Goland test cases (the actual test and the Jupyter notebook): I just tested that these will both work on the released version of SHARPy and should not contain any deprecated settings. You have a full description of what the settings are in the docs in the solvers page and for the linear modules used in the Hope this helps, |
This has been fixed in #148. Deprecated/unrecognised settings raise an error and all examples and templates have been updated to reflect the latest settings. It will be available at the next SHARPy release, for the moment, available in the |
Hello,
I just started playing with SHARPy, and to start I downloaded the Goland wing test case and run it on my machine (using the Docker application).
During the simulation, some warning occured of unrecognised setting:
I checked on the webpage and those messages don't appear in the simulation results mentioned on the doc, so I would like to ask if there is something I am missing.
For completeness I attach the whole messages out of the simulation.
Best regards,
Alessandro Sgueglia
goland_log.log
The text was updated successfully, but these errors were encountered: