search

NASA-AMMOS / aerie

A software framework for modeling spacecraft.
https://nasa-ammos.github.io/aerie-docs/
MIT License
73 stars 19 forks source link

"This Plan brought to you by files X, Y, and Z" Traceability in the UI #1383

Open cchouina opened 7 months ago

cchouina commented 7 months ago

Checked for duplicates

Yes - I've already checked

Alternatives considered

Yes - and alternatives don't suffice

Related problems

There are related ideas in https://github.com/NASA-AMMOS/aerie/issues/1318

Describe the feature request

As a planner and plan reviewer, I would like to be looking at a Plan and know what files (especially what file versions) are being used to create the generated elements in the Plan and be able to trace Activities and Resource impacts back to the source files.

It would be nice to have a way to view in the AERIE UI a kind of "this Plan brought to you by files x, y, and z" final credits-like info and follow Parent->Child spawn and Scheduler Goal links back to a source file (if there is one) or other source.

Traceability will be particularly helpful when source files are no longer valid or have changed and all the scheduled descendants need to be wiped out or shifted within a Plan.

bradNASA commented 6 months ago

Great idea! Plans often come in different pieces with their own versions like epochs, viewperiods, station allocations (SAF), maneuvers, . . .