Skip to content

Update reports to run after run_model - #1322

Open
cmbenne3 wants to merge 2 commits into
OpenMDAO:mainfrom
cmbenne3:issue1269
Open

cmbenne3 wants to merge 2 commits into
OpenMDAO:mainfrom
cmbenne3:issue1269

Conversation

@cmbenne3

Copy link
Copy Markdown
Contributor

Summary

Here is current list of reports in Aviary/aviary/interface/reports.py:

name_of_report Current Call Method New Call Method Notes
subsystems post run_driver() post run_model()
post run_driver()
Subsystem reports will be valid after run_model too!
mission post run_driver() No Change Mission report doesn't really make sense without solving the trajectory
timeseries post_run_driver() No Change As above the timeseries doesn't make sense without solving the trajectory
run_status post run_driver() No change As above run_status doesn't make sense for run_model
sizing_results post run_driver() No Change Sizing results would only make sense to save after an actual completed sixing mission
input_checks post final_setup() No Change None needed - final_setup is before run_model
overridden_variables post final_setup()
post run_model
post run_driver()
No Change No change required
list_options post run_driver() post final_setup()
post run_model()
post run_driver()
list options can be done after final_setup()

Related Issues

Backwards incompatibilities

None

AI Usage

None

This branch has not been deployed

No deployments
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

Successfully merging this pull request may close these issues.

Many reports do not run when using run_model

2 participants