Sein Jeung

Hi @rwblair, so far I have been trying to follow the document on contributing to BIDS validator and changed the .json schema and regexps for file names. Do you have...

Hello @rwblair! Thank you so much for the touch-up work. I found some missing fields in the validator and fixed issues with the example data along with reflecting changes in...

Hello @rwblair, I'd appreciate some help from you here, because I am stuck at the task of testing my validator version. With the older version that I used to run...

> @sjeung I went ahead and did the rebase with master, I can churn through them pretty quick (even though I made a couple mistakes). > > I'll review the...

Hello @rwblair, hope you are doing well! Are there any questions about the motion spec? There is an additional [motion + EEG example data](https://github.com/bids-standard/bids-examples/pull/329) that is being reviewed. Me and...

Thanks a lot @rwblair , looks great. To reply to your previous comment - >TrackingSystemCount was required in validator, I removed it from the required list. It is not listed...

Hi @rwblair, both examples should now check out without irrelevant errors or warnings in the validator output. Relevant error & warning - the channel type validation for channels.tsv is not...

Yeah there are definitely some limitations to relying on the sampling frequency value. We made a distinction between nominal sampling rate (SamplingFrequency) that is used as hardware spec description and...

It's nice to see the two cases clearly written out like that. "Synchronisation and latency channel" section in this [Motion-BIDS preprint ](https://osf.io/preprints/psyarxiv/w6z79) is describing those cases, depending on the availability...

> where "" can be anything such as latency, timestamp, time or index (depending on what section of the specs is being discussed and could even be left open to...