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

validate: provide likely reasons for typical validation errors #76

Open
yarikoptic opened this issue Apr 9, 2020 · 0 comments
Open

Comments

@yarikoptic
Copy link
Member

E.g., as reported on slack, there was a bunch of

TimeSeries/data (processing/spikes/Sweep_27): argument missing

validation errors. Thanks to the feedback from @rly on nwb slack channel:

from the path, i guess that the user wishes to store spike times in a TimeSeries. the most straightforward way to do that right now is to put the spike times in the timestamps array, but the data array is still required. here, until we implement a proper Events type (see NeurodataWithoutBorders/nwb-schema#301), i recommend the user create a dummy array data consisting of ones for every value in the timestamps array.

Which gave me an idea that we might want to post-process some of the pynwb validation errors and provide guesses on what could have lead to them and how to mitigate.

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

2 participants