-
Notifications
You must be signed in to change notification settings - Fork 62
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
Check whether input files/output paths exist #225
Comments
Example where user was confused (most likely), and error reporting didn't help as much as it could: #250 (comment) |
che85
added a commit
to che85/dcmqi
that referenced
this issue
May 19, 2017
…ICR#225) * cerr upon missing file/directory and EXIT_FAILURE
che85
added a commit
to che85/dcmqi
that referenced
this issue
May 19, 2017
che85
added a commit
to che85/dcmqi
that referenced
this issue
May 23, 2017
che85
added a commit
to che85/dcmqi
that referenced
this issue
May 23, 2017
…ICR#225) * also added methods for checking if required inputs were defined * cerr upon missing file/directory and EXIT_FAILURE
fedorov
added a commit
that referenced
this issue
May 25, 2017
ENH: adding checks for existence of file/files in file list (issue #225)
fedorov
pushed a commit
that referenced
this issue
Jun 29, 2017
* also added methods for checking if required inputs were defined * cerr upon missing file/directory and EXIT_FAILURE
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Tell users if they don't exist to help troubleshoot problems. Print absolute path for the input filenames/directories passed by the user.
The text was updated successfully, but these errors were encountered: