-
Notifications
You must be signed in to change notification settings - Fork 151
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
AIBS_ecephys NWB extension suggestions #1330
Labels
Comments
fyi @rly |
Merged
@isaak-willett were all of these points addressed? |
@isaak-willett @kschelonka can we please re-open this? |
Yes, although we may want to separate some of these points into different issues. |
This was referenced Mar 12, 2020
Closing this issue in favor of the children issues that were created. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Here are a few suggestions for you extension:
AllenSDK/allensdk/brain_observatory/ecephys/nwb/AIBS_ecephys_extension.yaml
Lines 2 to 3 in a040661
I would categorize a neuropixel
EcephysProbe
as aDevice
, not anElectrodeGroup
.AllenSDK/allensdk/brain_observatory/ecephys/nwb/AIBS_ecephys_extension.yaml
Lines 6 to 8 in a040661
The "help" attribute is no longer required, so you may wish to remove it.
AllenSDK/allensdk/brain_observatory/ecephys/nwb/AIBS_ecephys_extension.yaml
Lines 16 to 18 in a040661
We generally record the sampling rate as part of the
ElectricalSeries
, not the probe. This attribute is really a feature of the voltage measurements themselves. Also, it is possible for a probe to collect data at varying sampling rates.AllenSDK/allensdk/brain_observatory/ecephys/nwb/AIBS_ecephys_extension.yaml
Lines 19 to 21 in a040661
We would generally keep track of the LFP sampling rate in
/processing/ecephys/LFP/ElectricalSeries/starting_time.rate
. Again, this is really a feature of that data, not of the neuropixel probe. You choose when you downsample what the resulting rate should be, so it is very feasible to have different LFP sampling rates for the same probe.AllenSDK/allensdk/brain_observatory/ecephys/nwb/AIBS_ecephys_extension.yaml
Lines 29 to 50 in a040661
You have included subject information in your
EcephysLabMetaData
object. This information would be better inSubject
. In fact, there are already fields for"sex"
,"strain"
,"genotype"
, and"date_of_birth"
in theSubject
object. If you want to pre-compute the'age_in_days"
and provide that as an attribute, the best way to do that would be to extendSubject
.AllenSDK/allensdk/brain_observatory/ecephys/nwb/AIBS_ecephys_namespace.yaml
Lines 1 to 6 in a040661
You extension does not have a doc, an author, an author email, or a version number. Without a version number, it can be difficult to make adjustments to your extension and retain the ability to validate an NWB file, use visualization and query tools based on your extension, and open your extension across programming languages.
https://github.com/AllenInstitute/AllenSDK/blob/internal/allensdk/brain_observatory/ecephys/nwb/__init__.py
In your
__init__.py
, you define custom API classes for the extensions you have created, but it's not clear why. It looks like you would have gotten the same result by replacing this entire file withWe advise that you use
lfp_writer.write(nwbfile, cache_spec=True)
. This caches the extension in the NWB file and makes it easier for others to read your data (without having toimport allensdk.brain_observatory.ecephys.nwb
)The text was updated successfully, but these errors were encountered: