Check volume loss and repeatability for the calibrated pump
Maintainers usually reply within 3 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 18/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Active
- Tech stack
- python
- Domain
- testing-qa
Research direction
The issue names no files or tests; it refers to a calibrated pump model, its FMEA expected shortfall, and copy, reset and staged propagation behaviour. Start by locating the pump model and its existing histories in the fmdtools repository, and find the seeded simulation runs they depend on. Done would mean the final volumes match the known outputs and repeated runs with the same seed give identical results, but the issue is part of #277 and needs maintainer direction on scope first.
Written by the indexing model from the issue text.
Description
Compare the fitted pump’s final volumes with its histories and the FMEA expected shortfall. Verify copy, reset and staged propagation against known outputs and repeated runs with the same seed.
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 3/5 1-2 days Newbie friendliness 55/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