-
Notifications
You must be signed in to change notification settings - Fork 0
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
Improve error handling when files don't exist, e.g. in engine run #3
Comments
Handled by 56bf942#diff-887fdaa62ac183543d9080bb224bc9de Does not currently check if executables have the |
Probably… By extension or by content? The former is easier but can be onerous. The latter can be hard to do.
…--
David A. C. Beck, Ph.D.
dacb@uw.edu
http://faculty.washington.edu/dacb/
Research Associate Professor, Dept. of Chemical Engineering
Director of Research & Senior Data Science Fellow - eScience Institute
Adjunct Associate Professor of Paul G. Allen School of Computer Science & Engineering
Adjunct Research Associate Professor, Env. and Occ. Health Sciences
Associate Director - NRT Data Intensive Research Enabling Clean Technologies
University of Washington, Seattle
On Sep 21, 2018, at 1:26 PM, mpesesky ***@***.***> wrote:
Do we currently (or want to) check file type (ie. fastq, fasta, gff)?
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub <#3 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AGL1-gMmgQ9XVOxa48xrhWlJZG1OAe_uks5udUtpgaJpZM4WzPeV>.
|
I put that in the wrong place, but since we're talking about it – I was thinking content. We could avoid it and just pass along the errors from the constituent programs as they run into format issues. |
Can we leverage biopython for this vs reinventing our own validators? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In an environment without some of the paths listed in the config, e.g.
/work/software
directory,engine run
will throw an error that should probably be caught and handled. E.g.,This maybe part of a larger question about where and when these options should be validated. Probably in
barrelseq/config.py:validate
?The text was updated successfully, but these errors were encountered: