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

Assigning multiple design surfaces for aerodynamic optimization #170

Closed
AbhijithMoni opened this issue Feb 2, 2024 · 2 comments
Closed

Comments

@AbhijithMoni
Copy link

Hi,

I would like to assign multiple design surfaces to the designSurfaceFamily option in adflow.

 aero_options = {

    "designSurfaceFamily":"wingu",
}

In the options, there is only a possibility to assign either a string or None to the designSurfaceFamily source. When I try to assign multiple surfaces I get an error which is expected based on the documentation (accepts only str).

baseclasses.utils.error.Error:
 | Error: Datatype for option designSurfaceFamily is not valid. Expected data   |
| type (<class 'str'>, <class 'NoneType'>). Received data type is <class       |
| 'list'>

In my CGNS mesh, the wing geometry that I would like to optimize contains multiple components which consist of surfaces namely: "wingu", "wingLE", "wingTE", "wingb". And fuselage and tail which are not a part of optimisation.

I would like to know if there is a workaround to solve this problem of assigning multiple design surfaces to the solver at once.

Attempting to consolidate all wing surfaces into a "wing" family using cgns_utils proved challenging due to the inherent complexity of handling multiblock meshes.

Coraser version of the mesh is attached.

uCRM_coarse.zip

Any help is appreciated.

Thanks

@AbhijithMoni AbhijithMoni changed the title Assigning multiple design surfaces for aerodynamic optimization ADflow. Assigning multiple design surfaces for aerodynamic optimization Feb 2, 2024
@Asthelen
Copy link
Collaborator

Hello, this sounds like an issue with ADflow and not MPhys. Perhaps you can try posting the issue/question there (https://github.com/mdolab/adflow) instead?

@AbhijithMoni
Copy link
Author

It's been a couple of months since I posted my question on the ADflow platform, unfortunately, I haven't received any comments or answers. Hoping for more visibility, I brought my query here, assuming that since ADflow is an integral component of MPhys, it might get attention.

mdolab/adflow#334 (comment)

Thank you for your response. I'll take your suggestion and re-post my query in the ADflow forum.

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

2 participants