Open pauladkisson opened 1 year ago
Yeah, this is a tricky one because the environment in which the NWB Inspector is run is not necessarily one in which the ndx-photometry
extension would be installed, so it's hard to add a conditional skip statement to the check function of the form if isinstance(dynamic_table_target, FibersTable)
I guess we could maybe do something less sophisticated but less general, such as if type(dynamic_table_target).__name__ == "FibersTable"
?
I also don't know if it would be a good practice to add ndx-photometry
to the minimal requirements of the Inspector...
Any thoughts @rly @oruebel @bendichter? This is the first time we've seen such a clear interaction between the checks on core neurodata types and some extended ones
https://github.com/NeurodataWithoutBorders/pynwb/issues/1777 could be the second one with ndx-miniscope
, but that turns out to be a validation error
What happened?
Current Behavior
When running nwbinspector on files containing ndx-photometry data, it flags a BEST_PRACTICE_VIOLATION for each ROIResponseSeries with message:
Expected Behavior
nwbinspector should not flag any violations since ndx-photometry data does not use PlaneSegmentation tables.
Minimal code to reproduce
See ndx-photometry tutorial to generate the nwbfile and then run in CLI
Operating System
macOS
Python Version
3.11
Were you streaming with ROS3?
No
Package Versions
Code of Conduct