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 feature to convert CGNS meshes to OAS meshes with camberline #330

Open
marcomangano opened this issue Aug 22, 2020 · 4 comments
Open

Comments

@marcomangano
Copy link

Type of issue

  • New feature (non-breaking change which adds functionality)

Description

As per title, we should add and document a script that allows to "translate" a CGNS mesh used by ADflow to an equivalent input file for OpenAeroStruct

@kanekosh
Copy link
Contributor

Sounds good, will you need that for your project @marcomangano?
OAS meshes are just panels but not distinct upper/lower wing surface. The planform and camber are represented by the mesh (which is defined by the vertex coordinates of VLM panels).
The sectional thickness and the chordwise location of max thickness cannot be stored in the OAS meshes, instead, we need explicit representation via t_over_c_cp and c_max_t. The spanwise distribution of t/c (and maybe of c_max_t as well?) is controlled by b-spline.

@marcomangano
Copy link
Author

I opened this issue (together with many others) because it was part of the TODO list from 2yrs ago that @nwu63 mentioned during the presentation today. It is not part of my research unfortunately but I am happy to offer feedback if necessary!!
I see how there are some challenges involved into this, especially when non-conventional airfoils are used as wing sections. I think this is going to be a nice feature when implemented, that could further increase OAS usage even in multifidelity contexts.

@ewu63
Copy link
Collaborator

ewu63 commented Aug 25, 2020

So, just to be clear, I implemented this about two years ago when I needed this. However, in classic research fashion, I did not document the process and the code is either deprecated or lost. I do not have time to work on this myself, but would be happy to provide support, and if I can find my old code that could be a good starting process.

@kanekosh
Copy link
Contributor

Thanks Neil! I don't have time to implement this anytime soon, but good to keep the idea here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants