Closed HenrikBengtsson closed 6 years ago
This is most likely because of https://github.com/UCSF-Costello-Lab/LG3_Pipeline/blob/38405cf4b8352aa82c1e87c727cf3d412c7eb113/scripts/Germline.sh#L36-L51:
INPUTS=$(for i in ${bamdir}/*.bam
do
echo -n "-I $i "
done)
echo "$INPUTS"
### $JAVA -Xmx16g \
### -nct 3 -nt 8 \
if [ ! -e "${patientID}.UG.snps.raw.vcf" ]; then
echo "[Germline] Running Unified Genotyper..."
$JAVA -Xmx64g \
-jar $GATK \
--analysis_type UnifiedGenotyper \
--genotype_likelihoods_model SNP \
--genotyping_mode DISCOVERY \
"$INPUTS" \ <===
I've fixed scripts/Germline.sh
and scripts/UG.sh
in the develop branch.
@ivan108, please do git pull
and relaunch tests.
Found yet more cases of this from manually inspection of the remaining scripts/*.sh files. Do another git pull.
Great, thanks for fixing this so quick. I guess I introduced that bug when I quoted "INPUTS" ...
However, this is not the only problem we have. Before that Recal pipeline (scripts/Recal_bigmem.sh) quietly failed on line 214, right after "Indel realignment" step but before deleting intermediate files (rm -f "${patientID}.merged.bam") ...
I also noticed "${inputs}" on line 46 of scripts/Recal_bigmem.sh, it seems we don't need them, but shellcheck insists on that?
... we don't need quotes?
I did remove those quotes in scripts/Recal_bigmem.sh as well, cf. commit 16c4c7d5.
... we don't need quotes?
We should not use quotes around ${inputs}
and $INPUTS
, but ideally we should probably quote each individual -I <file>
as -I "<file>"
when we construct those two variables/strings. I ignored that for now, but we could add it do our todo list.
Moved the remaining part of this to Issue #9.
which comes from one of these following files: