Skip to content

Conversation

@bendhouseart
Copy link
Collaborator

@bendhouseart bendhouseart commented Apr 18, 2025

This closes #52 and tells the user how to (potentially) fix issues with T1w's or how to ignore them by using the exclude flag for future attempts at defacing.


📚 Documentation preview 📚: https://petdeface--54.org.readthedocs.build/en/54/

A t1w file not found error would get caught by a try except that's now
been fixed by tracking all not found t1w errors and halting the pipeline
while alerting the user.
@bendhouseart bendhouseart requested a review from mnoergaard May 22, 2025 22:15
@bendhouseart
Copy link
Collaborator Author

Added a validator check using the newer validator to screeeeeaam if the dataset isn't valid. Aka, it will crash on any error returned from bids-validator, still ignores warnings but I think that's fine.

@bendhouseart
Copy link
Collaborator Author

@bendhouseart add test data

@bendhouseart
Copy link
Collaborator Author

@mnoergaard this is gtg

Copy link
Collaborator

@mnoergaard mnoergaard left a comment

Choose a reason for hiding this comment

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

LGTM - thanks, Anthony!

@bendhouseart bendhouseart merged commit 8f4bd9d into main Jun 3, 2025
1 check passed
@bendhouseart bendhouseart deleted the 52-pipeline-should-halt-if-bad-t1ws-are-present-or-more-generally-if-not-bids-valid branch June 3, 2025 13:47
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.

Pipeline Should Halt if Bad T1w's are present; Or more generally if not bids valid

3 participants