Implement some standardization of dealing with design variables amongst solvers. #183
kejacobson
started this conversation in
Ideas
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Although MPhys is designed to be modular, some of our runs scripts that swap multiple codes for the same discipline still end up with many
if {this_solver} then {do this}
blocks of code. One place where this tends to happen is dealing with design variables in independent variable components. If we can come up with a standard for this, that would simply our run scripts and user experience.Here's a version of how I've starting generalizing this for FUN3D and our VLM solver. Both solvers implement a
CaseDescription
class that has a method to add its variables to an independent variable component, and a method to get a list of the variable names which can be used to generalize connecting the IVC variables to other components.Example Usage:
Beta Was this translation helpful? Give feedback.
All reactions