Closed harisankarsadasivan closed 5 years ago
From the error messages it sounds like a protocol is already running - this will cause errors in both set_sample_id
and start_protocol
Have you tried opening the UI and checking if a protocol is running for the selected sequencing device?
You could call protocol.get_current_protocol_run
before the start protocol to check (this function throws if there is no protocol running)
@jorj1988 how do I open the UI from the command line? Pls note I have a test cell loaded and not a flow cell. Will this be any different with a test cell?
Hi, Problem solved. Thanks to @iiSeymour and @jorj1988 for the timely help. However, I have one final question for this thread. I can now start and stop the runs succesfully. I can also see the output directory being created with a test cell loaded. But I do not see basecalling or anything else initiated although I was running 1 of th2 protocols with basecalling. Will this happen on terminal once I actually load a real flow cell?
My MinION-106 is connected to the machine and is detected when I use
list_devices.py
. I am trying to see if I can establish a communication channel to do a run until feedback to MinION. But, when I runstart_protocol.py
, I get the following error when I try to set sample id (note: the minion is loaded only with the configuration test cell):But, even if I comment the sample id set-up line and proceed, the run fails to start and I get an unknown status back. Following is the error in this case:
I am wondering if this will be resolved when I load the flowcell? I want to do a stop_protocol after starting to see that my run until mini-model is successful. @jorj1988 @iiSeymour