NASA-AMMOS / NASA-AMMOS/plandev
Cannot tell if extracted SEQ JSONs still reflect the current activity plan
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 128
- Forks
- 33
- Avg merge
- 1d 17h
- Merged PRs (30d)
- 12
Description
nsims
https://jira.jpl.nasa.gov/browse/AERIEQS-369
Moderate
The set of sequence IDs for an entire plan, as well as the expanded sequence JSON content, is wiped out if any user runs a new simulation. Without a history or the ability to freeze and lock a plan, it is difficult to guarantee that the expanded SEQ JSONs that were extracted from Aerie/Merlin still reflect the current activity plan.
Contributor guide
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 by reviewing the nsims implementation and the Aerie/Merlin flow that produces the sequence IDs and expanded SEQ JSON content. Determine whether the intended result is history across simulations, a freeze/lock mechanism, or both; done should ensure extracted data can be verified against the current activity plan.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100