Closed willros closed 1 year ago
Hi @willros
It seems that ReadBouncer cannot connect to the given flowcell port. Did you set up the simulated device MS00000
in MinKNOW?
Hi @JensUweUlrich
Yes, I set up the simulated device MS0000
as instructed in your github repo.
I also did not change the default value for the ports for guppy
and minKNOW
.
I can see the simulated the devide in minKNOW and start a dry run inside there, but readbouncer is not able to connect.
Just to be sure we don't miss anything: Are you running MinKNOW and ReadBouncer on the same machine? And you have installed the latest ReadBouncer version (version 1.2.2)?
Hi,
I was running version 1.1 (from the master branch). I will try to download the latest and see if it works. Thank you!
Ah ok, that's probably the issue. ReadBouncer 1.1 is not compatible with MinKNOW 5.x. Using the latest ReadBouncer version should solve your problem.
That doesn't depend on the base caller. When the sequencing run has finished or has been stopped by the user via MinKNOW, ReadBouncer will also stop running.
Hey I just ran into this same issue. The download link for Linux posted in your Readme.md points to the 1.1 build of ReadBouncer by the way.
@jamesemery Which versions of MinKNOW and ReadBouncer are you using?
I found that switching to Read bouncer 1.2 fixed this issue, I just fell into the trap of downloading the wrong version from the README. MinKNOW 22.08.9
Hi,
I get the following message when trying to run ReadBouncer:
I am using the latest ReadBouncer for linux x86. I am using minKNOW 22.10.7 with MinKNOW core: 5.3.1 Guppy: 6.3.8 Bream: 7.3.2 Script Configuration: 5.3.7
The minknow daemon is up and running, controlled by:
The config.toml file:
Any idea what I can try or what is going on?
Thanks a lot, William