-
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! |
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: