-
Notifications
You must be signed in to change notification settings - Fork 1
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
WGBS:bam_statistics always fails with Docker profile #11
Comments
Thanks for posting! At some point previously we were encountering an issue where the I will investigate further this afternoon. In the meantime, is it possible for you to test it instead with conda and see if this is resolved there for you? |
As discussed in issue #7, this seems solved now by simplifying L458 in lib/wgbs.nf as per 17d09d1. When running with Singularity/Docker, this was previously creating an empty header file which resulted in a truncated subset.bam file. The file could then not be parsed by the WGBS:bam_statistics process resulting in this error. |
I'm not savvy enough to understand how to run the pipeline with a commit that hasn't been issued in a release. I've been running this: NXF_VER=20.07.1 /home/shared/nextflow run epidiverse/wgbs -profile test,docker But, now I see this message rightly indicating that I'm working with a release which is behind the most current commit:
If you don't mind giving me some guidance on how to use the version with the newest commit, I'll happily test this out! Thanks! |
Sorry, I should have thought this through first before responding! So, to use the most current version available, I cloned the repo. Then called the pipeline by specifying path to the cloned repo. In my case, it looks like this: NXF_VER=20.07.1 /home/shared/nextflow run /home/shared/epidiverse-pipelines/wgbs-current -profile test,docker Will report back when test run and actual run using some of our data are complete! |
Well, this is still failing in when running the test profile, using the most recent commits. Confirm I'm using most recent version of repo:
Side note: I don't see that revision in the repo commit log, so does that reference something else?
Here's what's in that working directory: sampleA/ sorted.bam subset.bam@ Both of the BAMs present look good. Here's head of
Corresponding stats file in the
Any thoughts? |
Tested with conda and the test profile runs without issue. I've updated the issue name to specifically reflect that the failure is a Docker-specific problem. With that said, I'll probably just move forward with the conda environment and ditch using Docker (for now). |
My bad, I jumped the gun a bit here as the other issue was closely intertwined - but #7 should at least be fixed for you now as of the last commit 17d09d1? I managed to isolate the present issue with the Docker container and rebuilt the image now with a fix. Seems like there were a couple of things going on here which obscured the situation somewhat. To verify, you can add the option Thanks again for your help here! |
No worries at all! In fact, it's even easier than that. If you ever want to get the latest version of any Nextflow pipeline hosted on Github you can simply do e.g. |
This part of the pipeline always fails, for all samples. After a few different runs with different data sets, this always happens. However, the stats files actually are generated, but I'm not sure what aspect of this part constitutes failure.
Here's an example from a recent run. Error message from
.nexflow.log
:Here's what I see in
/home/shared/8TB_HDD_01/sam/analyses/20220715-olur-nextflow_epidiverse-wgbs/work/36/5380cd17196a4057ec8d5af0975f15
:proc.erne-bs5.bam@ sorted.bam zr1394_11_s456/
Then, if I look in the
zr1394_11_s456/
directory:stats/ zr1394_11_s456.bam.stats
A quick glance at the
zr1394_11_s456.bam.stats
looks good:So, it seems like BAM stats were generated...
Any ideas on what might be happening?
The text was updated successfully, but these errors were encountered: