-
Notifications
You must be signed in to change notification settings - Fork 163
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
Are event files required for MEG data? #1922
Comments
which version of the validator are you using? I modified this example by removing the events.tsv: https://github.com/bids-standard/bids-examples/tree/master/ds000248
Using a fairly recent version of the validator bids-validator --version
*bids-validator v1.14.7-dev.0-249-g93ca7a02 I get (amongst other things) this:
|
Thank you for looking into it, in that case we will investigate a bit more. We were using 1.14.8, I will try with a different validator and let you know what happens. |
oh wait, I was unclear: I was using the validator based on deno that uses the BIDS schema. So install deno: https://docs.deno.com/runtime/fundamentals/installation/ deno install -Agf https://github.com/bids-standard/bids-validator/raw/deno-build/bids-validator.js |
I would recommend using the distributed version, not the javascript build: deno run -A jsr:@bids/validator $DATASET This should line up with what's on the website. @Remi-Gau's command will get you the version based on the latest If you want an install: deno install -Agf -n bids-validator jsr:@bids/validator |
This works, is this the validator you recommend now, or will the old one still be updated? |
The old one will be entirely phased out and we will stop updating it. We may be able to package the new one so that people installing through npm can get an identical experience, but I'm not sure about that. We're planning to write a blog post to help people understand and navigate the transition soon. |
We recently found when running the bids validator that there are no warnings for missing event files with MEG data (when the task is not rest). Going over the specification it is not entirely clear to me whether they are required like they are for task fMRI. On MRI it says the following: "For task based fMRI, a corresponding task events file (see below) MUST be provided (please note that this file is not necessary for resting state scans)." But similar language is not used on the pages describing MEG or EEG data. So I am not sure if that is the case or if this is an issue in the validator.
I cannot currently share the data we validated, but I found a case on OpenNeuro where there is also no warning although the task is not rest and there are no event files: https://openneuro.org/datasets/ds004738/versions/1.0.1
The text was updated successfully, but these errors were encountered: