Can DAFoam ( mphys"scenario_aerostructural") support one wall patch for aerostruct opt, another patch for aerodynamic opt simultaneously?

[NUAA-qinfei]

I have two wall patch, "wing" and "nacelle", and have two FFD blocks,one FFD controls the "wing"shape, another FFD controls the "nacelle" position, and the "wing" patch have struct mesh , but "nacelle" patch no struct, I konw for the "wing" opt should use "scenario_aerostructural" ,but for the "nacelle" just the "scenario_areodynamic",I want to know if DAFoam can support this opt simultaneously,or "scenario_aerostructural" support pure aerodynamic opt ? I do this but always have error. (if no wing struct,I do it successfully,just like the picture show,but now,I want to couple the wing struct to consider the wing static aeroelasticity)

[friedenhe]

As I understand, you are trying to do an aerostructure optimization for a full aircraft configuration. You generate CFD meshes for the entire aircraft, but you have FEM (structural) mesh for the wing only. This should be doable. What you need to do is to use ["wing", "nacelle"] for the "designSurfaces" key in daOption, and use "couplingSurfaceGroups": {"wingGroup": ["wing"] } for the "couplingInfo" key in daOption. Note that the aero-structural coupling patches can be different from the designSurface patches.

[NUAA-qinfei]

Thanks for prof,I do it as you say ,but always have error,and how to understand " the aero-structural coupling patches can be different from the designSurface patches.",why different?

[NUAA-qinfei]

I do it as you say,always have this error after reading the bdf,

[friedenhe]

The above should work.. If not, maybe there is a bug somewhere in the code.. A temporal workaround is to use ["wing", "nacelle"] for both the designSurfaces and "couplingSurfaceGroups"-"wingGroup". The load transfer component uses the nearest N points (controlled by n=xx in MeldBuilder) to interpolate the force, so if your nacelle is far from the wing, its force should not impact the wing loading by a lot. Again, this is not a perfect solution, but it should get the case running.