Closed shigdon closed 5 days ago
Sorry to hear you're having issues @shigdon!
There should be no need to use an sbatch
script to run the nextflow pipeline; nextflow will automatically do all the required job submissions if you run with the appropriate profile (in this case ctmr_gandalf
). You can just run nextflow in a tmux session on the login node, that's perfectly ok!
I agree that it sounds as if the prokka environment isn't working as intended. Perhaps a version change could work, did you have time to try that yet?
Another thing I've been thinking of is to add container directives to the config of all modules so we can use already available biocontainers for all these packages, that should make the pipeline more robust overall and easier to execute in different compute environments.
As the Gandalf HPC is discontinued and we are moving towards replacing the conda envs with containers, I close this issue.
Hello,
I was attempting BACTpipe runs on ctmr-gandalf with a test set of 2 isolate pe-fastq samples when unexpectedly the system encountered an error during the Prokka module. The Git Repo was pulled fresh yesterday, Feb 7, 2022. I initially submitted the jobs via the following
sbatch
script:This produced the following error during prokka module:
I then reran after modifying the nextflow command by substituting the
-profile
flag for:Where the only change I made to the config was to specify a specific version of prokka to Conda:
Rerunning with this change in configuration profile did not solve the issue and produced the same error.
I am not sure how to proceed in fixing this but my next logical step would be to downgrade the prokka version. Any thoughts or suggestions are much appreciated.
Thanks!