nanoporetech / nanoporetech/minknow_api
Distinguish "Mux_Scan" and "Sequencing" state
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 73
- Forks
- 16
- PR merge metrics
- No merged PRs in 30d
Description
Hi,
I just have a short question: How can I distinguish the current state of the sequencing run using the API? I would like to determine if the device is currently performing a "MUX_SCAN" or if the status has changed to "Sequencing". I'm actually using the Acquisition::MinknowStatus to see if the run has been started, is processing or is finished. But the status "Processing" is returned when the MinION performs a "MUX_SCAN". Any suggestions for a workaround are much appreciated.
Best regards
Jens
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 Acquisition::MinknowStatus entry point in the protobuf/gRPC API specifications and determine what state values are exposed during a run. Check whether MUX_SCAN and Sequencing are distinguishable; done would require a documented API distinction or a confirmed limitation and workaround.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- grpc, python
- Domain
- api
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100