Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Split mandatory and not mandatory metrics #401

Closed
3 tasks
dladrichem opened this issue Apr 5, 2024 · 0 comments · Fixed by #477
Closed
3 tasks

Split mandatory and not mandatory metrics #401

dladrichem opened this issue Apr 5, 2024 · 0 comments · Fixed by #477
Assignees
Labels
Feature New feature request Needs refinement Issues that still need to be discusses, made more concrete or prioritised

Comments

@dladrichem
Copy link
Contributor

Kind of request

Changing existing functionality

Enhancement Description

Some metrics are mandatory since they are used by other parts of the system (i.e. the benefits calculation using the expected damages). These should always be calculated. Some other metrics are only indicative to the user. These are not mandatory and also can be changed/added/removed by the user. These two groups should be in different files.

Side note, it is mandatory to calculate these metrics. It is not mandatory to also show them in the GUI

Task list

  • Check which metrics are mandatory
  • Split the file
  • Implement reading and stacking both files

Use case

No response

Additional Context

No response

@dladrichem dladrichem added Feature New feature request Needs refinement Issues that still need to be discusses, made more concrete or prioritised labels Apr 5, 2024
@dladrichem dladrichem self-assigned this Apr 5, 2024
@dladrichem dladrichem added this to the September 2024 release milestone Apr 5, 2024
@dladrichem dladrichem linked a pull request Jul 3, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature New feature request Needs refinement Issues that still need to be discusses, made more concrete or prioritised
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant