Advanced Linkage
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
Research direction
The issue does not name files, tests, or entry points. Start by locating the goal and coexistence-linkage implementation, then trace how activity parameters currently match instances. Done should mean goals can target a specific activity instance rather than every matching activity, with tests covering the described scheduling scenario.
Written by the indexing model from the issue text.
Description
Checked for duplicates
Yes - I've already checked
Alternatives considered
No - I haven't considered
Related problems
For many scheduling goals, there is the setup of having a 1x science activity placed via a 1x cardinality goal (within a constrained plan window) with several other coexistence goals that link activities to end before or start at the end of the primary activity. It is difficult to establish relations between specific activity instantiations of these goals.
Let's provide an example of the problem:
There is a 1x science activity placed via a 1x cardinality goal (within a constrained plan window). A GNC single turn and solar array fix that must take place before a select science activity type. If we wanted to start the array fix activity at the start of the more general linked GNC turn (instead of linking to endAt the unique science activity start) it is complicated. The coexistence goal would be written to hook the array activity to a GNC turn activity with specified parameters; however this would link the array activity to all turns in the plan with specified parameters, not just the one immediately prior the specific science activity.
Describe the feature request
Enable goals to hook to specific activity instances
- Dominant language
- Java
- Stars
- 128
- Forks
- 33
- Avg merge
- 1d 17h
- Merged PRs (30d)
- 12
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.
More from NASA-AMMOS/plandev
-
publish
NASA-AMMOS/plandev#1885 · 2 comments · 3 assignees ·
-
breaking change
Difficulty 4/5 3-5 days Newbie friendliness 20/100
NASA-AMMOS/plandev#1863 ·
-
bug
Difficulty 3/5 1-2 days Newbie friendliness 55/100
NASA-AMMOS/plandev#1830 ·
-
bug planning
NASA-AMMOS/plandev#1829 · 1 comment · 1 assignee ·
-
feature
Difficulty 5/5 Over a week Newbie friendliness 42/100
NASA-AMMOS/plandev#1828 ·
All issues in NASA-AMMOS/plandev
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
bug needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
Difficulty 1/5 Under an hour Newbie friendliness 94/100
objectionary/hone-maven-plugin#1061 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
spring-projects/spring-modulith#1895 ·