-
Notifications
You must be signed in to change notification settings - Fork 46
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
Workflow error from V-pipe dry run #160
Comments
Hi (and sorry for the slow answer, I was on holiday). I notice that you're giving absolute paths in you configuration file (begining with a slash
And thus, V-pipe is trying to read and write file on the root directory of your workstation:
see directories I presume you should be using paths relative to your current working directory, like the tutorials do, so without a leading
|
Another problem is that currently V-pipe doesn't provide any informations about Little Cherry Virus (See here for a list of available resources for viruses ) So this part is not going to work:
You will need to provide your own. And change the configuration file accordingly. for example: # create a resource directory in the current working directory:
mkdir -p resources/LChV-2/
# copy the files in there
cp …somewhere_where_you_have_the_files…/LChV-2/reference.fasta resources/LChV-2/
cp …somewhere_where_you_have_the_files…/LChV-2/genomic.gff resources/LChV-2/ and then edit the configuration file to point to this new resource directory you created: input:
# …
reference: "resources/LChV-2/reference.fasta"
genes_gff: "resources/LChV-2/genomic.gff"
# ^- no leading '/': search in the current working directory. (Of course you could also install the files into your local copy of V-pipe, in which case you would have to fix a missing input:
# …
# '..' missing here --------vv
reference: "{VPIPE_BASEDIR}/../resources/LChV-2/reference.fasta"
genes_gff: "{VPIPE_BASEDIR}/../resources/LChV-2/genomic.gff" (NOTE: if you decide to modify V-pipe to add support for LChV-2, we would be interested in your pull request) |
Thanks so much for your response! I hope you had a pleasant holiday :) I made the necessary modifications to the directory paths in my config file, however I am still getting the same error message config file: input: output: error message: As for the reference, gff file locations etc. I did have them in the 'V-pipe/workflow' directory, so the pathing should have worked. However I did as you recommended and moved them into the 'resources' directory, and changed my config file to reflect the pathing (see above). Thanks in advance for your patience. I'm a novice on the command line, so there may be something basic that I'm missing. |
Describe the bug
I am analyzing data from plant (cherry) samples hoping to determine viral quasispecies of Little Cherry Virus
I set up my v-pipe workflow based on the sars-cov2 tutorial
However, when I attempt to run v-pipe, either through a dry run or fully, I get a "workflow error"
My questions:
I'm curious why there is a "missing input file" (for sam2bam and gunzip). I was not instructed to give any other files except the fastq.
Is the workflow error a bug, or something I am missing in my input/config files?
To Reproduce
Expected behavior
Due to following the setup tutorial, and sars-cov2 tutorial, I expected to get an output message indicating I either had everything in the right place in my config file, or indicating where I would need to make changes
Desktop
The text was updated successfully, but these errors were encountered: