Skip to content
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

Aux time series dimensionality limit #107

Closed
samuelpowell opened this issue Apr 16, 2022 · 3 comments · Fixed by #116
Closed

Aux time series dimensionality limit #107

samuelpowell opened this issue Apr 16, 2022 · 3 comments · Fixed by #116

Comments

@samuelpowell
Copy link
Collaborator

We are examining how best to 'fit' auxiliary data from LUMO into a valid SNIRF file, pertinent examples of which are:

  1. Up to 54 individual time series of 6- or 9-axis MPU data at 100Hz
  2. Per-channel time series data metrics/flags, such as coupling quality

The most natural way for us to achieve this would be to write these data in the /aux group, which I note (from #86) is intended for the storage of arbitrary time series data. As specified, the auxiliary time series are limited to being vectors:

/nirs(i)/aux(j)/dataTimeSeries

  • Presence: optional; required if aux is used
  • Type: numeric 1-D array
  • Location: /nirs(i)/aux(j)/dataTimeSeries

If we are limited to a vector, the former example could require up to 486 auxiliary time series, and the latter two orders of magnitude more!

Might it be possible to extend the specification to permit (manufacturer specific) auxiliary data to be a matrix?

@sstucker
Copy link
Collaborator

Including this in the overhaul I am working on re: #103

@samuelpowell
Copy link
Collaborator Author

Thanks @sstucker

@sstucker sstucker added the v2.0 Things to be considered for version 2 label May 30, 2022
@sstucker sstucker removed the v2.0 Things to be considered for version 2 label Jun 1, 2022
@sstucker
Copy link
Collaborator

sstucker commented Jun 1, 2022

See above for a proposed change

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants