David Boas

@samuelpowell , excellent issue you are raising. This is very important to resolve. Can you take a look at the [channel descriptor tsv file specification](https://bids-specification--802.org.readthedocs.build/en/802/04-modality-specific-files/11-functional-near-infrared-spectroscopy.html#channels-description-_channelstsv) in the BIDS fNIRS specification....

@samuelpowell , I was arguing to keep the array representation of the measurement list information, but several others were in support of the specification now adopted by SNIRF. The rationale...

@sstucker and I were discussing that one possible solution to the overhead issue is to have the option that each element of `/nirs(i)/data(j)/measurementList(k)` could be comprised of arrays for `/nirs(i)/data(j)/measurementList(k)/sourceIndex`,...

@zahraaghajani , I recall that the original thinking was that the numeric number would be the power of the moment. Moments are calculated as \integral t^n I(t) dt. So n=0...

I have now clarified the definition of momentOrders as suggested above

I am reopening this issue because we need to be more clear in the definition of the moment order. The text we just added to the spec is accurate for...

i agree. Can you make a pull request with these edits? From: Zahra M. Aghajan ***@***.***> Date: Friday, August 6, 2021 at 12:31 PM To: fNIRS/snirf ***@***.***> Cc: Boas, David...

@rob-luke and @fangq , this is just clarifying the spec for time domain moments and won't break anything, so I will just go ahead and accept this PR when it...

Good discussion on this so far. I am in favor of leaving the spec as is for backward compatibility in particular but also because some of the contributors to the...

I agree that no changes are needed. But as Rob says, I am curious about the ways in which people are using multiple runs per file. I would like to...