You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have been trying to run roary as part of a Snakemake workflow, and was trying to use query_pan_genome to identify the core genome of subsets of samples in the run.
Trying to run
'query_pan_genome -a intersection -o path/to/output -g run_tag/annotations/roary/clustered_proteins run_tag/annotations/prokka/file1.gff,run_tag/annotations/prokka/file2.gff'
All of the paths are relative to the working directory of the pipeline, and a double checked that they all existed and were formatted correctly for the program.
The files in the roary and prokka directories were generated by roary and prokka, respectively, and I have not deleted any of the files they produced (though I did move the roary files into their appropriate directory to bypass issue #404, using the standard bash 'mv' command)
Let me know if you need any other details or information regarding this issue!
Best Regards,
Kalum
P.S. Forgot to mention I had also tried providing full, explicit paths for all directories (rather than paths relative to the working directory); this also did not work.
The text was updated successfully, but these errors were encountered:
I just tried it out; as long as all the symlinks for the gff files are in the same folder it will work happilly. The roary protein_cluster file can be in a different directory, however, which is a bit unusual.
Hello Developers,
I have been trying to run roary as part of a Snakemake workflow, and was trying to use query_pan_genome to identify the core genome of subsets of samples in the run.
Trying to run
Results in the following error:
All of the paths are relative to the working directory of the pipeline, and a double checked that they all existed and were formatted correctly for the program.
The files in the roary and prokka directories were generated by roary and prokka, respectively, and I have not deleted any of the files they produced (though I did move the roary files into their appropriate directory to bypass issue #404, using the standard bash 'mv' command)
Let me know if you need any other details or information regarding this issue!
Best Regards,
Kalum
P.S. Forgot to mention I had also tried providing full, explicit paths for all directories (rather than paths relative to the working directory); this also did not work.
The text was updated successfully, but these errors were encountered: