NASA-AMMOS / NASA-AMMOS/plandev
Within the constraint or plotting systems, allow for access of internal values of resources or activity parameters.
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 128
- Forks
- 33
- Avg merge
- 1d 17h
- Merged PRs (30d)
- 12
Description
swieso
https://jira.jpl.nasa.gov/browse/AERIEQS-442
Moderate
{quote}From Slack Thread:
Sloan Swieso:
Within the constraints system is there a way to access the value of a Discrete class instance and potentially create a Real instance from it using the Real.Value() constructor? E.g. we have an Activity with a 3 vector parameter that within the constraint system generates a Discrete parameter with a {x: number; y: number, z: number} schema. I want to grab the x value from that and check if it is less than something, but can't do that while it's a Discrete. Is there any way to do that or will we have to edit the Activity itself so that the parameter gets created as a Real instance from that start?
Matt Dailis:
I don't believe that's currently possible - your workaround is probably the best option for now.I think this would be a valuable feature though - digging into structured parameters, as well as structured resources - both in Constraints and in the UI (e.g. plot a time series of {{{}someResource.x{}}}).
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 constraints system and the plotting/UI paths; the issue names no files, tests, or entry points. Clarify whether the feature must expose fields from structured Discrete parameters, structured resources, or both, and define done as supporting the requested value access and plotting behavior with tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- full-stack
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100