search

OpenMDAO / Aviary

NASA's aircraft analysis, design, and optimization tool
https://openmdao.github.io/Aviary/
Other
107 stars 51 forks source link

Options Traceability #405

Open jkirk5 opened 5 days ago

jkirk5 commented 5 days ago

Desired capability or behavior.

A major issue facing both users and developers is difficulty determining where options are used, and determining what options are used by a component. It is desired to stop bulk passing all options via aviary_options and instead only pass options that are actually used by the component, however that presents significant technical challenges that may also require development on the openMDAO side

Is your feature request related to a problem? Please describe.

No response

Associated Bug Report

No response

jkirk5 commented 5 days ago

From @erikdolsonva: Problem.model_options can be used to set options at the problem level and have them automatically filter down to any component that needs them. This feature could be used to set aviary_options at the problem level and it would be available to any component that uses it without having to manually pass it down through successive groups to get to the components that use it.

Example: self.prob.model_options['*'] = {'aviary_options': get_flops_inputs(case_name)}