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

SIDECAR_KEY_REQUIRED not documented #2140

Open
jens-k opened this issue Sep 17, 2024 · 7 comments
Open

SIDECAR_KEY_REQUIRED not documented #2140

jens-k opened this issue Sep 17, 2024 · 7 comments
Labels

Comments

@jens-k
Copy link

jens-k commented Sep 17, 2024

I ran the BIDS validator on a super simple dataset (one subject, one session, just for testing) and got the error "SIDECAR_KEY_REQUIRED (SoftwareFilters)".

I cannot find any information about this issue. The validator provides a link but (as for any error or warning I have ever encountered), the content behind the link seems unrelated to my issue or too cryptic to make sense of it.

I therefore tried to look for "SIDECAR_KEY_REQUIRED" and "SIDECAR_KEY" (which is the type of error, so it should be way more common than the particular one I got about software filters) on the following websites:

I have no hits for any of the terms. As this seems to be an entirely undocumented requirement/tag/error, I thought this might be considered a bug. I found a cryptic description of "SoftwareFilters" here: https://bids-specification.readthedocs.io/en/stable/glossary.html#softwarefilters-metadata but a normal user cannot be expected to understand this schema, and it does not fit to how I solved the problem.

The answer the user should get is:
In the sidecar file "*****.json", we would have expected a key called "SoftwareFilters". This key is specific for the eeg datatype. You can fix the issue by adding another line
"SoftwareFilters": "anystringiguess",
to the json file.

Is there an effort to fix these error messages? If so, I'd be glad to contribute.

Copy link
Contributor

Thank you for your issue. Give us a little time to review it.

PS. You might want to check the FAQ if you haven't done so already.

This is an automated reply, generated by FAQtory

@Remi-Gau
Copy link
Contributor

Hey @jens-k

Thanks for the report.

This metadata is also mentioned in the tables for the required metadata for EEG, ieeg and MEG.

https://bids-specification.readthedocs.io/en/stable/modality-specific-files/electroencephalography.html#sidecar-json-_eegjson

Though I admit those hits were at the bottom of the search when putting SoftwareFilters in the search bar of the bids specification.

For the improvement of the error message I think you should probably reopen this issue in the repo of the bids validator.

@Remi-Gau
Copy link
Contributor

Will transfer the issue to the BIDS validator repo.

@Remi-Gau Remi-Gau transferred this issue from bids-standard/bids-starter-kit Sep 28, 2024
@effigies effigies added the schema label Oct 3, 2024
@effigies
Copy link
Collaborator

effigies commented Oct 4, 2024

You should see: "A data file's JSON sidecar is missing a key listed as required."

What error are you actually seeing?

@jens-k
Copy link
Author

jens-k commented Oct 5, 2024

"SIDECAR_KEY_REQUIRED (SoftwareFilters)"

@effigies
Copy link
Collaborator

effigies commented Oct 7, 2024

Oh, it doesn't even tell you what files that's happening in? Could you share a screenshot of the expanded error?

@jens-k
Copy link
Author

jens-k commented Oct 28, 2024

Sorry, we moved on with that project and I don't have the files anymore in the version that produced this error. In the end, we used the validator of openneuro to check the dataset, which gave us more information about each error and we were able to fix them swiftly.

If I had to summarize my experience with the bids-validator, I would say that I just did not receive the information I needed as a rather casual user to fix the problems and not in the language I could understand. Forwarding me to a forum on another website did not help me either.

Nevertheless, thanks for your response and the work you are doing!.

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

No branches or pull requests

3 participants