WriteNWB Needs to be used by non-mesoscope data #1749
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Overview:
This is a response to the LIMS issue that appeared this morning. LIMS Job 1056188052 in BEHAVIOR_OPHYS_WRITE_NWB_QUEUE failed because
imaging_plane_groupwas not in the data. This is expected, so we altered the code to account for non-mesoscope data, which will not have this parameter.Addresses:
Type of Fix:
functionality to not work as expected)
Solution:
get_imaging_plane_group will now return None if not dealing with mesoscope data
Changes:
Validation:
Screenshots:
Unit Tests:
Script to reproduce error and fix:
Configuration details:
I ran the tests locally and they passed
Checklist
Allen Institute Contribution Guidelines
Numpy Standards
appropriate
rc/x.y.z as its merge target
Notes: