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

sessions.json #1923

Open
achilleasNP opened this issue Apr 2, 2024 · 0 comments
Open

sessions.json #1923

achilleasNP opened this issue Apr 2, 2024 · 0 comments

Comments

@achilleasNP
Copy link

achilleasNP commented Apr 2, 2024

Hi everyone,
I am getting the two messages below while validating a single bids directory
which seem to contradict each other. I interpret the error to say that I shouldn't have a sessions.json file and the
warning to say that I should add a sessions.json.

1: [ERR] Files with such naming scheme are not part of BIDS specification. This error is most commonly caused by typos in file names that make them not BIDS compatible. Please consult the specification and make sure your files are named correctly. If this is not a file naming issue (for example when including files not yet covered by the BIDS specification) you should include a ".bidsignore" file in your dataset (see https://github.com/bids-standard/bids-validator#bidsignore for details). Please note that derived (processed) data should be placed in /derivatives folder and source data (such as DICOMS or behavioural logs in proprietary formats) should be placed in the /sourcedata folder. (code: 1 - NOT_INCLUDED)
	./sessions.json
		Evidence: sessions.json

and that:
2: [WARN] Tabular file contains custom columns not described in a data dictionary (code: 82 - CUSTOM_COLUMN_WITHOUT_DESCRIPTION)
./sub-10/sub-10_sessions.tsv
Evidence: Columns: comments not defined, please define in: /sessions.json, /sub-10/sub-10_sessions.json

I am using bids version 1.14.4 on Linux.

Thanks in advance,
Achilleas

@effigies effigies added the bug label Apr 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants