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

Distinguish "Mux_Scan" and "Sequencing" state #22

Open
JensUweUlrich opened this issue May 14, 2021 · 2 comments
Open

Distinguish "Mux_Scan" and "Sequencing" state #22

JensUweUlrich opened this issue May 14, 2021 · 2 comments

Comments

@JensUweUlrich
Copy link

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

@0x55555555
Copy link
Contributor

Hi @JensUweUlrich,

There is currently some state that isn't exposed to users (see also #15). We are looking at resolving this in a future release, but currently there is no simple way to find this state from outside minknow.

  • George

@JensUweUlrich
Copy link
Author

Thanks for the answer. Looking forward for future releases ;-)

Jens

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants