NASA-AMMOS / NASA-AMMOS/plandev

Reporting gaps in resource profiles

Open
#1,232 1 comment 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

feature merlin framework simulation
Dominant language
Java
Stars
128
Forks
33
Avg merge
1d 17h
Merged PRs (30d)
12

Description

Checked for duplicates

Yes - I've already checked

Alternatives considered

Yes - and alternatives don't suffice

Related problems

No response

Describe the feature request

There are some instances where it doesn't make sense for a model to report a resource value. At the moment, we have two use cases:

  1. A resource is not applicable to the current circumstances. For example, a resource tracking where on the ground a surface-observing instrument is pointed should be "N/A" or some equivalent if the instrument is not currently pointed at the ground.
  2. A resource has failed, but the simulation continues. For example, the telecom model might fail while the power model continues working, and we'd like to report values for the power resources.

In both of these cases, we'd like to report either a "gap" in the resource profile, or some different type of value, distinct from normal values for that resource.

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 by locating the resource-profile entry point and the path that reports resource values; the issue names no files or tests. Done means the project has a defined way to distinguish unavailable or failed resource values from normal values while allowing other simulation resources to continue reporting.

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
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.