BIDS sample and value columns will be considered "arbitrary" columns soon

[sappelhoff]

as discussed in:

• ENH: Clarify sample column values to be 0-based and possibly non-integer bids-standard/bids-specification#1441

and implemented in:

• [FIX] Demote sample and value columns in events.tsv from OPTIONAL to arbitrary bids-standard/bids-specification#1457

the currently OPTIONAL sample and value columns in *_events.tsv files will be demoted to "arbitrary" columns in BIDS 1.9.0.

Practically this means, that mne-bids should write entries into *_events.json, defining how we use sample and value.

Otherwise, datasets produced by mne-bids might soon generate a "warning" (not an error 😉 ) that sample and value are undefined.

[agramfort]

thanks for the update. I guess we will need a few PRs :)

…

On Tue, Apr 11, 2023 at 3:10 PM Stefan Appelhoff ***@***.***> wrote: as discussed in: - bids-standard/bids-specification#1441 <bids-standard/bids-specification#1441> and implemented in: - bids-standard/bids-specification#1457 <bids-standard/bids-specification#1457> the currently OPTIONAL sample and value columns in *_events.tsv files will be demoted to "arbitrary" columns in BIDS 1.9.0. Practically this means, that mne-bids should write entries into *_events.json, defining how *we* use sample and value. Otherwise, datasets produced by mne-bids might soon generate a "warning" (not an error 😉 ) that sample and value are undefined. — Reply to this email directly, view it on GitHub <#1130>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AABHKHHEE3HYBPICN5GDB7LXAVJ3VANCNFSM6AAAAAAW2IHALQ> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>