NASA-AMMOS / NASA-AMMOS/plandev

Fix bug where child activity types are not visible in plan UI when parent is placed with scheduling

Open
#887 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

This issue has come up while testing Europa Clipper scheduling goals (on clipper-aerie main) on a local aerie deployment. I have noticed that when running the scheduler for goals that have multiple activity types, the children of the parent types do not show up in the plan window after successful scheduling + simulation. However, the children do show up in the "Simulated Activities Table". I have manually placed the individual parents in the plan and simulated and the children do show up in that case.

Attached below is a screenshot of a goal SUDA_Solar_Noise_Cal after scheduling and simulation. You are able to see the parents in the UI, but the children of GNC_Single_Turn, SUDA_All_Characterization, and GNC_Roll do not show up. But they are shown in the table below the plan view with expected start times and durations.
image

This bug can be reproduced by writing a scheduling goal that places a set of varied activity types (that have children) and running the scheduler, simulating, and assessing the UI view and simulated activities table.

Workaround

Use table view

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

Reproduce the issue with a scheduling goal containing varied activity types with children, then run scheduling and simulation. Compare the plan window with the Simulated Activities Table: done means child activities appear in the plan UI as they already do in the table, without relying on the table-view workaround.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
frontend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.