You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Anytime we are opening a file to read data, we should ensure that the file matches an expected format so that it doesn't throw any weird exceptions.
For example, when checking NeuropixelsV2e gain correction files, an incorrectly formatted file leads to weird exceptions that are not very useful for the end user.
There are other areas where we pull data from files without checking if they match some expected format; we can use this issue as a meta-issue to track individual areas where this might be necessary to add some logic for checking file formats.
Related: All GUI functions that are touching the same files should not reimplement logic, but should call these new checking functions and loading functions from the base library.
The text was updated successfully, but these errors were encountered:
Anytime we are opening a file to read data, we should ensure that the file matches an expected format so that it doesn't throw any weird exceptions.
For example, when checking
NeuropixelsV2e
gain correction files, an incorrectly formatted file leads to weird exceptions that are not very useful for the end user.There are other areas where we pull data from files without checking if they match some expected format; we can use this issue as a meta-issue to track individual areas where this might be necessary to add some logic for checking file formats.
Related: All GUI functions that are touching the same files should not reimplement logic, but should call these new checking functions and loading functions from the base library.
The text was updated successfully, but these errors were encountered: