-
Notifications
You must be signed in to change notification settings - Fork 35
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
Adding support for [email protected] #95
Comments
Hi @llk578496, This is on our TODO list. |
I am getting a related issue. @cjw85 could please explain where the models are being retrieved from? The docker image of medaka or somewhere else? I am recieving this #104 error again. Trying to debug where/what is happening. The model I am trying to run is |
@cjw85 @mattdmem Sorry to bug you guys, we've switched over to r10 but I'm struggling to get the pipeline to use the medaka r10 models. We're running the docker images in such a way that they can't access the internet. I think I have identified the issue, the wf-artic docker image comes with only Could the docker image please be updated to include r10 which is standard now? Using the latest docker image:
using the 7month old one specified in the nextflow config:
|
Hi @llk578496 and @ammaraziz, the workflow and image have been updated. Could you please confirm if this fixes the issue? Thanks! |
Will test out this week or next. Thanks Julibeg! |
I am sorry for not replying as promised. The new updated docker image has newer models but not the old one:
output:
This causes a whole set of new problems: there is no r9 models but the default medaka model for this pipeline is the r9 model. |
@ammaraziz I'm not involved with the epi2me workflows anymore, but a quick hint: Medaka will download models if necessary:
Does this not work on your end? |
Unfortunately, there's no Internet connection on my system and medaka doesn't allow specifying path to models. I flagged this previously that the docker image itself needs the models to be available. |
I see. If you need a solution quickly you could make a custom image for the time being I suppose. On a machine with internet connection create a
and run
Then, export as tar and transfer to the other machine. There, import with You will also need a custom config file to tell nextflow which image to use
Finally, run the command with I haven't tested the above, but with some luck it should work. |
@julibeg I can not thank you enough. My knowledge of docker is abysmal (I have to learn it one of these days), so I had no idea you can build upon docker images like this. Your instructions were excellent, though they were missing how to export:
I also pushed the docker image to my personal account https://hub.docker.com/r/ammaraziz/my-artic. theres a few more tweaks to the nextflow config to make so it will accept the models I want, but overall I think this is a decent solution (for me at least!). |
Is your feature related to a problem?
The latest supporting model for
--basecaller_cfg
is[email protected]
.Describe the solution you'd like
Is it possible to add the model
[email protected]
in the--basecaller_cfg
? Thanks a lot.Describe alternatives you've considered
Additional context
No response
The text was updated successfully, but these errors were encountered: