nanoporetech / nanoporetech/minknow_api
Detecting Run Failures and Machine Crashes in MinKNOW
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 73
- Forks
- 16
- PR merge metrics
- No merged PRs in 30d
Description
We are building an automated nanopore data processing pipeline and would like advice on detecting failures programmatically.
Specifically:
- Are there recommended ways in MinKNOW to real-time detect run failures or error states for automated monitoring?
- How can machine-level failures be detected? We have encountered cases where the machine powered off or crashed during run, causing downstream data transfer failed even though data and reports were generated locally.
Any guidance or documentation would be greatly appreciated.
Contributor guide
No contributing guide indexed for this repository
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.
Research direction
Start with the MinKNOW API documentation and its run-status, error-state, and data-transfer entry points; the issue does not identify specific files or tests. Done means documenting reliable ways to detect run failures and machine-level crashes, including the case where local data exists but transfer fails.
Written by the indexing model from the issue text.
Assessment
- Domain
- api, documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100