-
Notifications
You must be signed in to change notification settings - Fork 31
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
Setting up another guppy server #39
Comments
@tchrisboles If I understand you correctly, yes. You can setup another [caller_settings]
config_name = "dna_r9.4.1_450bps_fast"
host = "127.0.0.1"
port = 5556 To set up the server I would start a $ /path/to/guppy_basecall_server --config dna_r9.4.1_450bps_fast.cfg \
--port 5556 --log_path . --ipc_threads 1 --max_queued_reads 2000 \
--chunks_per_runner 48 --num_callers 1 -x cuda:all --gpu_runners_per_device 2 |
Great - will try it today and tomorrow and report. Thanks |
Changing to guppy server 3.4.5 seems to solve this issue - see my post in question #44. |
Alex - in view of progress on question #44 - I think this one is closed. |
Alex and Matt,
If one has a linux box running new Minion-nc, AND new guppy (version 3.5.x) in a different directory (say home/local/bin), one could run basecalling "remote" using the local/bin copy in server mode as long as the toml file is properly configured (port other than 5555). Is that correct? I think that Alex had a diagram for some thing close to this in an earlier reply to someone setting up ru on a gridion. I want to set this up for a minion, and was wondering if running basecalling server on the same machine (but different installation directory) would work. Any advice on setting up basecalling server or toml file for this case?
Originally posted by @tchrisboles in #30 (comment)
The text was updated successfully, but these errors were encountered: