Make the reservoir pump-stop scenarios reusable
Maintainers usually reply within 3 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 55/100
Research direction
Start in the reservoir lifecycle test, where the one- and two-second pump-stop scenarios are currently built, and trace how the random pump command sample is generated. Move that setup into a reusable function that returns the sample, results and histories. Done when both injection times are checked to lie on the simulation time grid and the same sample can be reused across scenarios. The issue is part of #277, so check that tracking issue for context.
Written by the indexing model from the issue text.
Description
Expose the one- and two-second pump stops currently built inside the reservoir lifecycle test. Return the sample, results and histories so users can compare the same random pump commands across scenarios. Check that both injection times are on the simulation grid.
Part of #277.
- Dominant language
- HTML
- Stars
- 61
- Forks
- 20
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 8
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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/fmdtools
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
nasa/fmdtools#357 · 2 comments ·
Maintainers usually reply within 3 days
-
Difficulty 3/5 1-2 days Newbie friendliness 55/100
Maintainers usually reply within 3 days
-
Difficulty 4/5 3-5 days Newbie friendliness 18/100
Maintainers usually reply within 3 days
-
Difficulty 4/5 3-5 days Newbie friendliness 28/100
Maintainers usually reply within 3 days
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
Maintainers usually reply within 3 days
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
ranacseruet/vaice#139 ·
Maintainers usually reply within 1 day
-
area:frontend bug FE P3
Difficulty 1/5 Under an hour Newbie friendliness 72/100
klasolsson81/jobbliggaren#2288 ·
Maintainers usually reply within 1 day
-
documentation evals good first issue priority:p1
Difficulty 2/5 Half a day Newbie friendliness 72/100
mobeloper/better-oss#17 ·
-
kind:defect
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
mux-labs/mux-frontend#1240 ·
Maintainers usually reply within 1 day