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

Tolerant option for bids.layout #11

Merged
merged 5 commits into from
Oct 1, 2020

Conversation

tanguyduval
Copy link
Contributor

No description provided.

@tanguyduval
Copy link
Contributor Author

tanguyduval commented Jul 23, 2019

This issue solves #7
Tolerance on:

  • dataset_description and .tsv files
  • parse image modalities that are not in BIDS yet (but in extension proposal for instance)
  • inconsistent data between subjects (currently it crashes if more images in one subject than another)

@Remi-Gau
Copy link
Collaborator

Nice.
Wouldn't it sense to have the inconsistency between subjects be the lowest level of tolerance: unless I am mistaken this does not make an invalid bids data set, where as the other 2 levels would.
Or am I missing something?

@tanguyduval
Copy link
Contributor Author

@Remi-Gau agreed, I just tried an inconsistent dataset with bids validator and it gives no error. Only a warning in case of inconsistent data between subjects:

Warning 2: [Code 38] INCONSISTENT_SUBJECTS
Not all subjects contain the same files. Each subject should contain the same number of files with the same naming unless some files are known to be missing.

I'll change that.
Best

@tanguyduval
Copy link
Contributor Author

@Remi-Gau this version accepts inconsistent data between subjects, even for files not officially in BIDS yet
tested on octave 5 and matlab.
Best

@Remi-Gau
Copy link
Collaborator

Thank. Will check things out during the weekend

@Remi-Gau
Copy link
Collaborator

  • add tests to check warning VS error handling of the tolerant option of layout

@Remi-Gau
Copy link
Collaborator

If that's with everyone I will start mergin those old pull-requests that have not been "vetoed".

  • bring the PR up to date with master
  • clean up and refactor if needed
  • create tests if needed or where easily possible
  • wait for 24 hours after CI gives the green light (in case anyone has any final thoughts before merging)
  • merge

@Remi-Gau
Copy link
Collaborator

On this one we would need some test to assert that a warning or an exception is thrown.

Not sure that our current framework allows this.

Copy link
Collaborator

@Remi-Gau Remi-Gau left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good with me

@Remi-Gau Remi-Gau merged commit f577ad4 into bids-standard:master Oct 1, 2020
@Remi-Gau Remi-Gau mentioned this pull request Oct 1, 2020
3 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants