-
Notifications
You must be signed in to change notification settings - Fork 33
Add ndtypes from ndx-pose, ndx-photometry, ndx-fiber-photometry #1665
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
base: master
Are you sure you want to change the base?
Changes from 1 commit
3e86325
da8c29b
3d7baea
00a60ad
1b99658
d360e2d
5e48759
21b1d99
20394ff
6ad64c1
0648a40
7dddd60
7fcddb8
c268842
9571b6b
bfc4553
60c21ab
f8490a9
4269177
c25e3d2
a6d1cb2
b784ba3
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -828,9 +828,9 @@ class Neurodatum(TypedDict): | |
| "technique": "fourier analysis technique", | ||
| "approach": None, | ||
| }, | ||
| "OptogeneticStimulusSIte": { | ||
| "OptogeneticStimulusSite": { | ||
| "module": "ogen", | ||
| "neurodata_type": "OptogeneticStimulusSIte", | ||
| "neurodata_type": "OptogeneticStimulusSite", | ||
| "technique": None, | ||
| "approach": "optogenetic approach", | ||
| }, | ||
|
|
@@ -840,6 +840,36 @@ class Neurodatum(TypedDict): | |
| "technique": None, | ||
| "approach": "optogenetic approach", | ||
| }, | ||
| "PoseEstimationSeries": { | ||
| "module": "ndx-pose", | ||
CodyCBakerPhD marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
| "neurodata_type": "PoseEstimationSeries", | ||
| "technique": "pose estimation technique", | ||
| "approach": "behavioral approach", | ||
| }, | ||
| "PoseEstimation": { | ||
| "module": "ndx-pose", | ||
rly marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
| "neurodata_type": "PoseEstimation", | ||
| "technique": "pose estimation technique", | ||
| "approach": "behavioral approach", | ||
| }, | ||
| "PoseTraining": { | ||
| "module": "ndx-pose", | ||
rly marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
| "neurodata_type": "PoseTraining", | ||
| "technique": "pose estimation technique", | ||
| "approach": "behavioral approach", | ||
|
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. on a more general note, i'm a bit confused about why pose training is a data type, as that doesn't seem to reflect behavior per se, and also why it is a pose estimation technique. some of these are direct measurement techniques or estimation techniques, but this one seems odd.
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. PoseTraining is a group consisting of training frames and source videos. A training frame refers to a frame from a source video and an the locations of each node of 1 or more skeletons, often from human labeling. So PoseTraining isn't exactly a data type but indicative of the NWB file containing training data for pose estimation methods. Should I pick out a different data type to detect instead?
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. we should consider data type as a broad umbrella of what data is generated from or used for (for example there is fourier analysis above). it could be associated with a "pose estimation training technique"
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. got it. that makes sense
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. @rly here we have 2 extensions listed to assist with importing https://github.com/dandi/dandi-cli/blob/HEAD/dandi/metadata/nwb.py#L99 -- should we also add extension information into this 'registry' and use it there too? or may be it is no longer even needed? |
||
| }, | ||
| "FiberPhotometryResponseSeries": { | ||
| "module": "ndx-fiber-photometry", | ||
rly marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
| "neurodata_type": "FiberPhotometryResponseSeries", | ||
| "technique": "fiber photometry technique; optical technique", | ||
| "approach": "calcium imaging; cell population imaging", | ||
| }, | ||
| "FiberPhotometryResponseSeries_old": { | ||
| "module": "ndx-photometry", # deprecated and replaced by ndx-fiber-photometry | ||
rly marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
| "neurodata_type": "FiberPhotometryResponseSeries", | ||
| "technique": "fiber photometry technique; optical technique", | ||
| "approach": "calcium imaging; cell population imaging", | ||
| }, | ||
| } | ||
|
|
||
|
|
||
|
|
||
Uh oh!
There was an error while loading. Please reload this page.