[Add Check]: ElectricalSeries of dtype int16 with conversion=1.0 and offset=0.0 is potentially wrong? #395
Assignees
Labels
category: new check
a new best practices check to apply to all NWBFiles and their contents
Comments
CodyCBakerPhD
added
the
category: new check
|
Good question. I think it is highly unlikely to be correct because I cannot think of a situation where electrodes in a neurophysiology experiment would be recording in integer volts. I think that should be invalid. Not sure about preventing DANDI upload. We could err on a stricter rule and relax it if an unexpected use case comes to our attention. |
|
I agree, int data with a conversion of 1.0 is likely an error. |
|
Hi Cody. This seams an error. Where this data is from ? |
|
@samuelgarcia Default TDT and SpikeGadgets v1 both default to 'placeholder' gains in neo/SI For the GUIDE support for those, we're therefore making the |
4 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What would you like to see added to the NWBInspector?
More of a question for either @alejoe91 or @samuelgarcia based on their experience
If you saw an ElectricalSeries that was of dtype
uint16orint16and the conversion factor (spikeinterface 'gain_to_uV') was all1.0and offset0.0, this is most likely incorrect, right?If so, how strongly incorrect is it?
@bendichter @rly @oruebel Would/Should it technically count as being invalid? Should it prevent DANDI upload?
Pseudocode or other logic of the check
No response
Do you have any interest in helping implement the check function?
Yes.
Code of Conduct
The text was updated successfully, but these errors were encountered: