ENH: Add Shimadzu Labnirs 3-wavelength raw recording, in .snirf format #130
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.
Test file required for mne-tools/mne-python#13408.
Some fNIRS data was recorded using a Shimadzu Labnirs device, then exported using the proprietary Labnirs software to a text file, which was then converted to .snirf with a custom converter (https://github.com/zEdS15B3GCwq/labnirs2snirf).
The data has 45 columns (15 S-D pairs * 3 wavelengths) and 250 time points. With a sampling rate around 20 Hz (19.6) the filter used in the scalp-coupling index calculation is >210 points long, so it's better to have more points than that to avoid a warning (and failed tests as a result).
Optode positions are "fake": optodes i and i+1 are 1 cm apart for the same types of optodes, and source i is 3 cm away from detector i.
Besides being unusual for having 3 wavelengths, another perhaps atypical feature is that the S-D pairs are not in increasing order: the first pair is S2-D2, then S1-S2, S1-D1, S9-D1, etc. This does not seem to cause any issues with processing.
The file is (to my knowledge) fully compliant with the SNIRF standard.