Closed kleighwill closed 7 months ago
Hi @kleighwill thanks you for using wf-human-variation. Can you please try the following:
nextflow pull epi2me-labs/wf-human-variation -r 1.9.0
NXF_SINGULARITY_CACHEDIR
and SINGULARITY_TMPDIR
to a custom directory, where the singularity images will be stored; for instance, looking at your path:
mkdir /scratch/groups/greicius/RUSH_AD/nextflow/.singularity
export NXF_SINGULARITY_CACHEDIR=/scratch/groups/greicius/RUSH_AD/nextflow/.singularity
export SINGULARITY_TMPDIR=/scratch/groups/greicius/RUSH_AD/nextflow/.singularity
and try the run again.
Andrea
Hi Andrea,
It looks like this (and the removal of the bed file in my command) worked for me. Thanks for your help!
Regards,
Kennedy
From: Andrea Talenti @.> Sent: Monday, November 20, 2023 2:01 AM To: epi2me-labs/wf-human-variation @.> Cc: Kennedy Williams @.>; Mention @.> Subject: Re: [epi2me-labs/wf-human-variation] The --snp workflow is halted due to a mosdepth/bedtools error: "command not found" (Issue #116)
Hi @kleighwillhttps://github.com/kleighwill thanks you for using wf-human-variation. Can you please try the following:
mkdir /scratch/groups/greicius/RUSH_AD/nextflow/.singularity export NXF_SINGULARITY_CACHEDIR=/scratch/groups/greicius/RUSH_AD/nextflow/.singularity export SINGULARITY_TMPDIR=/scratch/groups/greicius/RUSH_AD/nextflow/.singularity
and try the run again.
Andrea
— Reply to this email directly, view it on GitHubhttps://github.com/epi2me-labs/wf-human-variation/issues/116#issuecomment-1818729190, or unsubscribehttps://github.com/notifications/unsubscribe-auth/BB5I36HX5UZKIXKYX656F2LYFMS7RAVCNFSM6AAAAAA7QM2EEWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMJYG4ZDSMJZGA. You are receiving this because you were mentioned.Message ID: @.***>
Operating System
Ubuntu 22.04
Other Linux
No response
Workflow Version
v1.8.3
Workflow Execution
Command line
EPI2ME Version
No response
CLI command run
command is written inside of an sbatch script
Workflow Execution - CLI Execution Profile
singularity
What happened?
I'm currently trying to run the pipeline with only the --snp flag for one participant's pod5 files that have already been basecalled (so the pipeline is starting with the basecalled but unaligned bam). Most of the processes are executing normally, but the mosdepth input process has failed with the error message below. Any assistance would be greatly appreciated--thanks!
Relevant log output
Application activity log entry
No response