My labmate and I have encountered an issue with the SLURM version of Juicer v.1.6. We are using a Linux computing cluster:
LSB Version: :core-4.1-amd64:core-4.1-noarch
Distributor ID: CentOS
Description: CentOS Linux release 7.9.2009 (Core)
Release: 7.9.2009
It appears that the alignment step and all subsequent steps do not wait for the FASTQ splitting step to finish. To investigate, I made some modifications at line 700 in the juicer.sh script:
Here is the relevant output from my modified copy of juicer.sh:
dependsplit = afterok:7647558:7647559
Tue Feb 8 16:12:00 EST 2022
starting wait srun
srun -c 1 -p general-compute -t 1 -o /projects/academic/tkrabben/NJCB/ca_gen_1_juicer_purged_new_pipeline_02-08-2022/debug/wait-%j.out -e /projects/academic/tkrabben/NJCB/ca_gen_1_juicer_purged_new_pipeline_02-08-2022/debug/wait-%j.err -d afterok:7647558:7647559 -J a1644354720_wait sleep 1
Tue Feb 8 16:12:02 EST 2022
finished wait srun
The "srun" command should hold until the splitting batch jobs are complete. However, this does not seem to function properly. In the job queue, we can see 2 splitting jobs running simultaneously with an align job. From my understanding, this should not happen.
This is a problem because the remaining Juicer steps only use a subset of the total reads. In ./aligned/inter.txt we see that Juicer only uses the first chunk of 22,500,000 read pairs.
If we run Juicer again using previously generated split FASTQ files, Juicer functions properly and ./aligned/inter.txt reports 205,807,309 read pairs.
Do you have any advice on how to proceed? Is it possible this is a bug in the SLURM version of Juicer.sh? Happy to share our files and scripts if needed.
My labmate and I have encountered an issue with the SLURM version of Juicer v.1.6. We are using a Linux computing cluster: LSB Version: :core-4.1-amd64:core-4.1-noarch Distributor ID: CentOS Description: CentOS Linux release 7.9.2009 (Core) Release: 7.9.2009
It appears that the alignment step and all subsequent steps do not wait for the FASTQ splitting step to finish. To investigate, I made some modifications at line 700 in the juicer.sh script:
Here is the relevant output from my modified copy of juicer.sh:
The "srun" command should hold until the splitting batch jobs are complete. However, this does not seem to function properly. In the job queue, we can see 2 splitting jobs running simultaneously with an align job. From my understanding, this should not happen.
This is a problem because the remaining Juicer steps only use a subset of the total reads. In ./aligned/inter.txt we see that Juicer only uses the first chunk of 22,500,000 read pairs.
If we run Juicer again using previously generated split FASTQ files, Juicer functions properly and ./aligned/inter.txt reports 205,807,309 read pairs.
I noticed at least one other user might have a similar issue, considering their inter.txt file also reports exactly 22,500,000 read pairs (https://groups.google.com/u/1/g/3d-genomics/c/3_Ok2-CydmU/m/almfv6tjAAAJ).
Do you have any advice on how to proceed? Is it possible this is a bug in the SLURM version of Juicer.sh? Happy to share our files and scripts if needed.