-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
MRG: Restructure fNIRS IO tutorial #9408
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
larsoner
reviewed
May 19, 2021
Co-authored-by: Eric Larson <larson.eric.d@gmail.com>
@agramfort @drammock @larsoner please merge if happy. |
rob-luke
changed the title
WIP: Restructure fNIRS IO tutorial
MRG: Restructure fNIRS IO tutorial
May 20, 2021
agramfort
approved these changes
May 20, 2021
Thanks @rob-luke ! |
drammock
reviewed
May 20, 2021
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
dang... was in the middle of a review. well, this is as far as I got.
Comment on lines
+9
to
+25
MNE includes various functions and utilities for reading fNIRS | ||
data and optode locations. Regardless of the manufacturer and file format, | ||
MNE stores both the measurement data and metadata in a consistent manner. | ||
|
||
fNIRS devices consist of light sources and light detectors, | ||
often also termed emitter/transmitter and receiver respectively. | ||
A channel is formed by source-detector pairs, and MNE represents the | ||
channel location as the midpoint between source and detector. | ||
MNE stores the location of the channels, sources, and | ||
detectors. | ||
There are a variety of fNIRS data types which can be represented in MNE. | ||
For continuous wave fNIRS data this includes amplitude, optical density, | ||
oxyhaemoglobin, and deoxyhemoglobin. | ||
And for frequency domain fNIRS this additionally includes | ||
AC amplitude and phase. | ||
Different vendors save the data as different data types, and MNE will load | ||
the data as the appropriate type. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Suggested change
MNE includes various functions and utilities for reading fNIRS | |
data and optode locations. Regardless of the manufacturer and file format, | |
MNE stores both the measurement data and metadata in a consistent manner. | |
fNIRS devices consist of light sources and light detectors, | |
often also termed emitter/transmitter and receiver respectively. | |
A channel is formed by source-detector pairs, and MNE represents the | |
channel location as the midpoint between source and detector. | |
MNE stores the location of the channels, sources, and | |
detectors. | |
There are a variety of fNIRS data types which can be represented in MNE. | |
For continuous wave fNIRS data this includes amplitude, optical density, | |
oxyhaemoglobin, and deoxyhemoglobin. | |
And for frequency domain fNIRS this additionally includes | |
AC amplitude and phase. | |
Different vendors save the data as different data types, and MNE will load | |
the data as the appropriate type. | |
fNIRS devices consist of two kinds of optodes: light sources (AKA "emitters" or | |
"transmitters") and light detectors (AKA "receivers"). Channels are defined as | |
source-detector pairs, and channel locations are defined as the midpoint | |
between source and detector. | |
MNE-Python provides functions for reading fNIRS data and optode locations from | |
several file formats. Regardless of the device manufacturer or file format, | |
MNE-Python's fNIRS functions will internally store the measurement data and its | |
metadata in the same way (e.g., data values are always converted into SI | |
units). Supported measurement types include amplitude, optical density, | |
oxyhaemoglobin concentration, and deoxyhemoglobin concentration (for continuous | |
wave fNIRS), and AC amplitude and phase (for frequency domain fNIRS). |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Reference issue
None
What does this implement/fix?
Reordering and expanding the information in the fNIRS data type tutorial. As its had lots of growth lately but not much structure.