Skip to content
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

Pre-emptive error notices. #36

Open
AnnaBeers opened this issue Nov 19, 2018 · 2 comments
Open

Pre-emptive error notices. #36

AnnaBeers opened this issue Nov 19, 2018 · 2 comments
Assignees

Comments

@AnnaBeers
Copy link
Member

A certain art when writing code is making sure that when your code hits an error, you have a vague understanding of why that error occurred. I have not yet mastered that art.

There are several instances in DeepNeuro where you may hit a bug because you had a typo in your inputs, or otherwise formatted your data incorrectly. The fact that you did this may not be obvious. Here are some common ones that I will address in the future.

  • Filepath checking. Always check and raise errors if a provided folder or filepath does not exist.
  • Datasize checking. Raise errors if different channels of input data do not much in dimensions before downstream errors.

We should all add more types of these errors to catch in advance to this issue; I will post updates as they are addressed.

@AnnaBeers AnnaBeers self-assigned this Nov 19, 2018
@AnnaBeers
Copy link
Member Author

Referenced in #23

@AnnaBeers
Copy link
Member Author

Most relevant sections for error-checking:

The data submodule, which could check and catch data format errors early,
And the utilities submodule, which could catch filepath errors earlier.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant