-
Notifications
You must be signed in to change notification settings - Fork 32
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
Failure to fetch Singularity image #106
Comments
Hi, can you successfully run the workflow with the demo data provided with singularity? |
Hi, no the demo data does not work with singularity. I get the following error: FATAL: While making image from oci registry: error fetching image to cache: while building SIF from layers: while creating squashfs: create command failed |
And can you normally run a programme such as hello world with singularity on your cluster?? It looks like it could be an issue with your singularity set up and you might want to contact your cluster administrator. |
Hi @sarahjeeeze, I managed to successfully run the workflow with the demo data with Singularity. However, when running the workflow on my actual samples, I am running into an issue where there seems to be a problem with parsing a bam file. The full output is attached here for your reference: And here is the relevant error message: ERROR ~ Error executing process > 'pipeline:differential_expression:map_transcriptome (2)' Caused by: Command executed: minimap2 -t 4 -ax splice -uf -p 1.0 "genome_index.mmi" "seqs.fastq.gz" | samtools view -Sb > "output.bam" Command exit status: Command output: Command error: |
To help me recreate your error - where did you get the reference genome and annotation files from? Could you point me at the exact files? Also your reads are definitely --direct_rna not cdna? |
I got the reference genome and annotation files from GENCODE (https://www.gencodegenes.org/human/release_46.html). Specifically, I am using the GRCh38.p14 genome assembly and the basic gene annotation gtf file. And yes, my reads are direct RNA, not cDNA. Here is the exact command I am running: nextflow run epi2me-labs/wf-transcriptomes |
hmm inputs seem fine - To rule out if being a memory error could you add this to the nextflow.config - at the end of the file
|
Hi @sarahjeeeze, I am still getting the same error so it doesn't seem like it's a memory error? Could you let me know if there's any test I can run to see why samtools view seems to be having issues reading the header of the sam file? Is there a particular file that I should go look at to see if it might be malformed? I could also send you the input data to see if you can recreate the error on your end. |
hi, to your input cmd can you try adding for ref_genome are you using |
Hi Sarah, just to update you, I ended up resolving this issue by increasing the memory allocated to minimap2 to 48 GB in the nextflow.config file. Thank you so much for all your help, I really appreciate it! |
Great thanks, we are working on some memory improvements for minimap steps. |
Operating System
macOS
Other Linux
No response
Workflow Version
v23.04.3
Workflow Execution
Command line (Cluster)
Other workflow execution
No response
EPI2ME Version
No response
CLI command run
nextflow run epi2me-labs/wf-transcriptomes --de_analysis --direct_rna --fastq differential_expression/reads/ --minimum_mapping_quality 20 --ref_annotation differential_expression/GRCh38.gtf --ref_genome differential_expression/GRCh38.fa --sample_sheet differential_expression/sample_sheet.csv -profile singularity
Workflow Execution - CLI Execution Profile
singularity
What happened?
When trying to run the workflow through Singularity, I got an error where the image could not be fetched since there was no descriptor found for the reference (see log output below). I also looked for a log file output from Nextflow but it seems that there was none generated in the directory from which I ran the command. I'd appreciate any help troubleshooting!
Relevant log output
Application activity log entry
No response
Were you able to successfully run the latest version of the workflow with the demo data?
yes
Other demo data information
No response
The text was updated successfully, but these errors were encountered: