We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I've been hearing questions from people who would like to use the new NEB VarSkip primer scheme with this workflow.
I can get things working if I suggest that people download a custom scheme directory and call a command like this:
artic minion --strict --threads 8 --read-file reads.fastq --scheme-directory schemes --scheme-version 1a NEB_VarSkip reads --skip-nanopolish --medaka --medaka-model r941_min_fast_g303
with a custom scheme structure like this:
schemes/NEB_VarSkip/V1a schemes/NEB_VarSkip/V1a/NEB_VarSkip.scheme.bed schemes/NEB_VarSkip/V1a/NEB_VarSkip.reference.fasta schemes/NEB_VarSkip/V1a/NEB_VarSkip.reference.fasta.fai
I'd like to submit a PR to this repository that would allow simpler operation and avoid requiring people to download and organize a scheme directory.
artic minion --strict --threads 8 --read-file reads.fastq NEB_VarSkip reads --skip-nanopolish --medaka --medaka-model r941_min_fast_g303
This doesn't match very well with your naming hierarchy which expects a nCoV-2019 directory, and a simple numeric version selector.
What's the best path forward here? allow string version numbers to artic-tools so I can add something like this
schemes/nCoV-2019 schemes/nCoV-2019/VNEB-VarSkip-1a schemes/nCoV-2019/VNEB-VarSkip-1a/nCoV-2019.reference.fasta.fai schemes/nCoV-2019/VNEB-VarSkip-1a/nCoV-2019.reference.fasta schemes/nCoV-2019/VNEB-VarSkip-1a/nCoV-2019.scheme.bed
or maybe break out of the organism based organization?
The text was updated successfully, but these errors were encountered:
Bump... we would like this functionality as well. Thank you!
Sorry, something went wrong.
@nickloman: any chance you can advise on how to proceed?
No branches or pull requests
I've been hearing questions from people who would like to use the new NEB VarSkip primer scheme with this workflow.
I can get things working if I suggest that people download a custom scheme directory and call a command like this:
with a custom scheme structure like this:
I'd like to submit a PR to this repository that would allow simpler operation and avoid requiring people to download and organize a scheme directory.
This doesn't match very well with your naming hierarchy which expects a nCoV-2019 directory, and a simple numeric version selector.
What's the best path forward here? allow string version numbers to artic-tools so I can add something like this
or maybe break out of the organism based organization?
The text was updated successfully, but these errors were encountered: