-
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
Please use set -e (ideally set -euo pipefail) in smaltalign*.sh shell scripts to make them fail early & loudly #13
Comments
I just had a very silent failure which is probably a dependency problem, but smaltalign.sh crashed way later than the original error
|
Thank you for sharing, could you please send me the dataset that causes the error by email? |
Sorry I don't have that data set at hand right now, but we will keep observing and keep you posted. But in general, I think it would make sense for the script/pipeline to exit as soon as possible when anything expected happened. Today I did another run, on a fastq file with samples of the env region (I think... and I had only an R1 but no R2 file, so no paired reads...) and everything seemed to go fine, all scripts reported exit code 0, but no merged_lofreq_indel_hq.vcf file was produced... |
Ideally, prefix the shell script with sth like
see http://redsymbol.net/articles/unofficial-bash-strict-mode/
The text was updated successfully, but these errors were encountered: