I (probably at my own peril) never use multiqc or deconstruct variants within my graph building pipelines, so don't have these tools installed. pggb runs fine without them, so hopefully this guards against errors when users do want those analyses but don't have the tools installed, but still leaves flexibility for others.
On a related note, I have wfmash etc compiled for our compute nodes which gives "illegal instruction" errors on our head nodes due to different architectures. The command -v wfmash returns happily saying it is installed but then the program just exits silently, not even creating the output directory. Something like wfmash --version catches this, but not all tools have that hook (like vcfwave), so this is probably a user problem rather than something pggb should handle gracefully.
I (probably at my own peril) never use multiqc or deconstruct variants within my graph building pipelines, so don't have these tools installed. pggb runs fine without them, so hopefully this guards against errors when users do want those analyses but don't have the tools installed, but still leaves flexibility for others.
On a related note, I have wfmash etc compiled for our compute nodes which gives "illegal instruction" errors on our head nodes due to different architectures. The
command -v wfmash
returns happily saying it is installed but then the program just exits silently, not even creating the output directory. Something likewfmash --version
catches this, but not all tools have that hook (like vcfwave), so this is probably a user problem rather than something pggb should handle gracefully.