NASA-AMMOS / NASA-AMMOS/plandev

Explainability issue when a scheduling rule fails because of invisible simulation data

Open
#763 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

clipper scheduling
Dominant language
Java
Stars
128
Forks
33
Avg merge
1d 17h
Merged PRs (30d)
12

Description

nsims
https://jira.jpl.nasa.gov/browse/AERIEQS-426
Moderate
Here is an example to illustrate the point:

If I wrote a scheduling rule to add an instance of activity type X (e.g. UVS_Power_On) an hour before the start of each instance of activity type Y (e.g. UVS_Power_Off), but NOT during times when activity Z (SUDA_Decontamination) is also occurring... The scheduler would be unable to add the activity, but wouldn't be able to tell me why â nor would that be immediately visible to me.

The reason it would be unable to add the activity is because SUDA_Decontamination has a duration (once simulated) that would extend beyond the window specified in my scheduling goal. Because the scheduler runs its own internal simulation, it would know not to place an activity there. But I would have to run my own simulation in the UI to gain access to that context.

EDIT(dailis): This may be alleviated if #723 gets through

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the example in this issue and the linked AERIEQS-426 ticket, then trace how the scheduler reports an activity that cannot be placed and how the UI presents that result. Done means the user can see when invisible simulated data caused the failure and understand the relevant scheduling context.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
backend, frontend
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.