List view
o The ability to pause the simulation and save its state to persistent storage and then restart the simulation from that persistent state at another time. o The primary use case for this is plan final conditions to subsequent plan initial conditions with the initial conditions modified based on the most recent spacecraft telemetry. o Out of all capabilities Taifun believes needs to be replaced in SeqGen, she sees this as the highest risk item. We know we will have to do it, so why not buy down risk and do it now.
Due by September 30, 2024o The ability to pause the simulation and save its state to persistent storage and then restart the simulation from that persistent state at another time. o The primary use case for this is plan final conditions to subsequent plan initial conditions with the initial conditions modified based on the most recent spacecraft telemetry. o Out of all capabilities Taifun believes needs to be replaced in SeqGen, she sees this as the highest risk item. We know we will have to do it, so why not buy down risk and do it now.
Due by June 30, 2024•0/1 issues closedo The ability for Aerie to understand changes to a plan and only re-simulate resources effected by the change. o We already have a prototype for this built by a 397 GS (Brad Clement) with his own time, but that prototype will need to be significantly modified for us to feel comfortable including this capability in Aerie. o Nonetheless, the prototype has already bought down a lot of risk in understanding the scope of this work. o This capability offers A LOT of value when it comes to both simulation and scheduling performance, which will provide a ton of value to all customers
Due by September 30, 2024o The ability for Aerie to understand changes to a plan and only re-simulate resources effected by the change. o We already have a prototype for this built by a 397 GS (Brad Clement) with his own time, but that prototype will need to be significantly modified for us to feel comfortable including this capability in Aerie. o Nonetheless, the prototype has already bought down a lot of risk in understanding the scope of this work. o This capability offers A LOT of value when it comes to both simulation and scheduling performance, which will provide a ton of value to all customers
Due by June 30, 2024o Treat collections of activities as a single group and provide a user interface for creating groups, which requires defining the relationship between activities in the group. o UI could support collapsing groups in the timeline and moving groups as a single unit. o We have heard this request from many customers/potential customers including Clipper, LASP, and Dragonfly
Due by September 30, 2024o Treat collections of activities as a single group and provide a user interface for creating groups, which requires defining the relationship between activities in the group. o UI could support collapsing groups in the timeline and moving groups as a single unit. o We have heard this request from many customers/potential customers including Clipper, LASP, and Dragonfly
Due by June 30, 2024List of bug fixes in work or complete in FY24 Q4
Due by October 4, 2024•6/6 issues closedList of bug fixes in work or complete in FY24 Q3
Due by July 4, 2024•14/14 issues closedImprovements performed during `FY24 Q4` that address customer requests that do not fit into other planned milestones.
Due by October 4, 2024•10/10 issues closedImprovements performed during `FY24 Q3` that address customer requests that do not fit into other planned milestones.
Due by July 4, 2024•21/21 issues closedRevisit design and implementation of how constraints and scheduling goals can be shared across plans for a given mission model. Document how these constructs can be migrated from one mission model to the next.
Due by December 31, 2023•3/3 issues closedDuring branch creation allow users to checkout a temporal subset of a plan.
No due dateScheduling eDSL (co-existence goal) can specify start time of activities anchored to another activity in the plan.
Due by June 30, 2024•2/2 issues closedCurrently Clipper pre-computes geometric resources and loads them into every simulation through simconfig mechanism so that activities can be scheduled wrt geometric resources. These resources are then written to the database as a simulation result even though they don't change with every simulation. The proposal is to upload pre-computed geometric resources once per plan, update only when necessary. And allow scheduling goals to reference external resource profiles.
Due by June 30, 2024•1/1 issues closedLook for and implement efficiencies to the scheduling process to improve the performance of scheduling runs.
Due by September 30, 2024On mission model side there is a template model, and a several small examples that demonstrate modeling concepts. Would be worth expanding on these and highlighting best practices.
Due by September 30, 2024•3/3 issues closedImprovements to the initial release of the procedural scheduling capability: - Dynamic linking of jars so each procedural doesn't require all dependencies - Bulk procedure upload - Multiple instances of parameterized procedures - Support for optional parameters, validation, ordering
Due by September 30, 2024•1/1 issues closedImprovements performed during `FY24 Q2` that address customer requests that do not fit into other planned milestones.
Due by March 31, 2024•13/13 issues closedList of bug fixes in work or complete in FY24 Q2
Due by March 31, 2024•7/7 issues closedPart of expressiveness of EDSL For example, count cumulative uses of an instrument in last N minutes
Due by March 31, 2024•2/2 issues closedIdentify simulation performance bottlenecks, provide solutions and better guidance for making use of Aerie in a performant manner.
Due by March 31, 2024•2/2 issues closedList of bug fixes in work or complete in FY24 Q1
Due by December 31, 2023•8/8 issues closedAllow writing scheduling goals can query Aerie activity plan and simulation data, and determine schedule of activities through internal computations that are not restricted to Aerie scheduling API, and return the resulting activities as plan inputs.
Due by December 31, 2023•16/16 issues closedUsers can benefit from a reporting of current simulation time as it progresses.
Due by December 31, 2023•3/3 issues closedCancel in-progress simulation or scheduling run. This is especially helpful if simulation or scheduling is taking longer than the user expects.
Due by December 31, 2023•3/3 issues closedMechanism to register Extension/Helper endpoints that can be invoked via Aerie UI. Extension would be registered with a URL, a display name, and an optional output location via Aerie API and once registered would show as a menu item within Aerie. Selecting the menu item would call the Extension/Helper endpoint and the endpoint could optionally return a web page to show in a modal, new browser tab, or within one of the Aerie views. The helper could also generate external datasets and push the results back into aerie.
Due by December 31, 2023•2/2 issues closedImprovements performed during `FY24 Q1` that address customer requests that do not fit into other planned milestones.
Due by December 31, 2023•19/19 issues closed- Due by October 13, 2023•1/1 issues closed
List of bugs planned to be addressed in `FY23 Q2`
Due by April 25, 2023•14/14 issues closedList of bug fixes in work or complete in `FY23 Q4`
Due by October 13, 2023•26/26 issues closedList of bugs in work or fixed during `FY23 Q3`
Due by July 11, 2023•14/14 issues closedThis milestone groups ad hoc improvement issues for FY23 Q4.
Due by October 13, 2023•47/47 issues closedAllow undo per activity instance for a limited stack. One approach to deconflict undo action in a multi user web application is to support “undo” per activity directive. Gives a more granular undo ability compared to snapshots. Limits actions that can be undone (scheduling spec edits, sim config edits won’t be covered)
Due by October 13, 2023•1/1 issues closedActivity directives, sim config, scheduling spec, plan constraints should be stored as a snapshot on demand. Potentially, all the above should be stored for every simulation run either automatically or on demand. Users can revert the plan to a snapshot. Users can review past simulation run results, revert plan to that snapshot if exists.
Due by October 13, 2023•2/2 issues closedThis milestone groups ad hoc improvement issues for `FY23 Q3`. Started on `04/17/23`.
Due by July 11, 2023•60/60 issues closedDatasets (mission model, plan, simulation results, expansion rules, expansion sets, constraints, scheduling goals) will need metadata to indicate author, date created, date updated, updated by and similar information that can be captured by Aerie automatically. When applicable, user provided metadata such as description, sub-system, category should be captured as well. Clients should be able to filter / search data based on these metadata fields. Started on `04/17/23`.
Due by July 11, 2023•4/4 issues closedRegulate access to data sets and actions at role level. See the [Hasura documentation on authorization](https://hasura.io/docs/latest/auth/authorization/index/) for how we will do this. Related UI milestone: https://github.com/NASA-AMMOS/aerie-ui/milestone/13 Started on `04/05/23`.
Due by July 11, 2023•10/10 issues closedExcluding epoch relative and command complete time tags, this milestone is to convert relative time tags to absolute and time sort commands in single expanded sequences that multiple simulated activities target. See [this presentation](https://docs.google.com/presentation/d/1zzCVbUgA4DH0TfdTcK_QqHOxnSVwwDiAsUpY1n6W15o/edit?usp=sharing) for more information. Started on `04/03/23`.
Due by July 11, 2023•3/3 issues closedThis milestone groups ad hoc improvement issues for `FY23 Q2`. Started on `02/06/23`.
Due by April 25, 2023•44/44 issues closedStart a simulation from a mid-point using resource values calculated from a previous run. Started on `02/21/23`.
Due by April 25, 2023•4/4 issues closedAllow uploading a group of preset (aka template) arguments per activity type, such that users can select from the presets. The desire is to make presets available to both scheduling goals and manual planning. Started on `02/21/23`.
Due by April 25, 2023•3/3 issues closedThis is an epic issue that groups ad hoc improvement issues for `1.1.0`. Started on `11/08/2022`.
Due by February 6, 2023•40/40 issues closedThis is an epic issue that groups bug fix issues for `1.1.0`. Started on `12/05/2022`.
Due by February 6, 2023•10/10 issues closedThis is an epic issue that groups time management issues for `1.1.0`. Started on `12/06/2022`.
Due by February 6, 2023•1/1 issues closedThis is an epic issue that groups formal release documentation issues for `1.1.0`. Started on `01/10/2023`.
Due by February 6, 2023•2/2 issues closedThis is an epic issue that groups documentation update issues for `1.1.0`. Started on `11/08/2022`.
Due by February 6, 2023•17/17 issues closedThis is an epic issue that groups event and epoch relative planning issues for `1.1.0`. For more information about what events are see [this presentation](https://docs.google.com/presentation/d/1ywHcoSDLiVRdu2oQp0teHsRXyONQ7JOVH5k-eE82TII/edit#slide=id.g17628a708ad_0_28). Started on `11/08/2022`.
Due by February 6, 2023•6/6 issues closedThis is an epic milestone that groups scheduling updates issues based on user feedback for `1.1.0`. Started on `12/01/2022`.
Due by February 6, 2023•8/8 issues closed