Rewrite the reports to support multimission
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 287
- Forks
- 140
- Avg merge
- 6d 14h
- Merged PRs (30d)
- 18
Description
Desired capability or behavior.
See note in subsystem_report() of interface/reports.py from Jason: We need to rewrite the reports to support mul-timission. This may require standardizing how all attributes work in AviaryProblem (things like prob.model.get_val don't work with multi-mission but does for normal problems). End goal is to loop through each mission and get reports for each mission. Show in dashboard in nested tabs (new tab for each mission containing its own subsystems). Currently only getting reports for subsystems in first mission.
See note # 1186 in interface/reports.py and in interface/test/test_interface_bugs.py.
Suggested implementation.
No response
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the note in interface/reports.py at subsystem_report(), then read the related coverage in interface/test/test_interface_bugs.py. Trace how reports currently select subsystems and run the relevant interface tests. Done means reports are generated for every mission and the dashboard shows each mission in its own nested tab.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- analytics, frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100