-
Notifications
You must be signed in to change notification settings - Fork 112
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
Import of VSP Model for aerostructural analysis #396
Comments
I believe the optimization setup (i.e., whether aero or aerostruct) doesn't matter for |
But I will look into the plot_wingbox file to see if it is a plotting error. |
Hello, I just wanted to ask whether there is an update on if the problem also occurs for you/other users. |
Sorry Tim, we don't have time to work on this issue for a while. |
I have figured out the issue. The mesh that is being generated in the generate_vsp_surfaces function located in the utils folder needs to be of a different convention for the aerostructural case compared to the aerodynamic case. I achieved this by including the following lines: and modifying: This creates the right mesh format needed for the aerostructural case. |
I finally had time to reproduce the bug by myself. I consider this bug to be of aerostructural analysis rather than the VSP import. I'll close this issue and open another one. |
Description
When importing a wing into openaerostruct using the generate_vsp function, the wing from OpenVSP gets overlapped with another straight unswept wing. This only happens for aerostructural optimization with a wingbox and not for an aerodynamic optimization, here the generate_vsp functionality works great.
Steps to reproduce issue
Attached you will find the code I have used for this issue.
To recreate this code:
Current behavior
A rectangular wing is added at the end of the wingtips connecting the originally imported wing.
Expected behavior
The imported wing was expected to be correctly represented, just like in OpenVSP
Code versions
###Code
Code file: TestWingbox.txt
The text was updated successfully, but these errors were encountered: