NASA-AMMOS / NASA-AMMOS/plandev
Constraint Variables
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 128
- Forks
- 33
- Avg merge
- 1d 17h
- Merged PRs (30d)
- 12
Description
ccamargo
https://jira.jpl.nasa.gov/browse/AERIEQS-208
Low
Some constraints for Clipper use the same logic but differ only by variables. This request is to create a feature that allows for defining constraint variables separately from the constraints themselves. The variables should be stored separately from the constraint, and we should be able to connect the variables to the constraint before the execution of the constraint.
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 constraint model and the execution path described in the issue, then consult the linked AERIEQS-208 Jira item for additional context. Done means constraint variables can be stored independently, connected to a constraint before execution, and reused by constraints that share logic.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100