You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The addition of flight conditions with the adflow wrapper should be standardized so that we can use the common naming convention with other aero solvers. currently, adflow still uses aeroproblems during configure and this requires extra manual connections.
Also with these changes, we can clean up the wrapper a bit and remove the unnecessary methods that were called in configure.
This only applies to the MPhys wrapper which is moved to ADflow in #196 . This issue is moved from the MPhys repo: OpenMDAO/mphys#61
The text was updated successfully, but these errors were encountered:
Description of feature
The addition of flight conditions with the adflow wrapper should be standardized so that we can use the common naming convention with other aero solvers. currently, adflow still uses aeroproblems during configure and this requires extra manual connections.
Also with these changes, we can clean up the wrapper a bit and remove the unnecessary methods that were called in configure.
This only applies to the MPhys wrapper which is moved to ADflow in #196 . This issue is moved from the MPhys repo: OpenMDAO/mphys#61
The text was updated successfully, but these errors were encountered: