Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

JSON exceptions #99

Open
Lestropie opened this issue Sep 8, 2021 · 2 comments
Open

JSON exceptions #99

Lestropie opened this issue Sep 8, 2021 · 2 comments

Comments

@Lestropie
Copy link
Collaborator

If a JSON is malformed, which can occur when manually adding the IntendedFor field to fmap/ files, the resulting Python exception is unhandled, and so a catastrophic crash occurs. It would be preferable to catch such and give a more informative error message.

@treanus
Copy link

treanus commented Sep 9, 2021

It also seems that the IntendedFor field can only have 1 entry.
The case "IntendedFor": ["dwi/sub-01_acq-b1000_dwi.nii.gz", "dwi/sub-01_acq-b3000_dwi.nii.gz"] e.g. throws an error.
An fmap could be used for sdc for more than 1 dwi dataset, no?

@Lestropie
Copy link
Collaborator Author

Code here is intended to deal with the prospect of IntendedFor being either a string or a list of strings. If that's not working, that's worthy of its own issue listing.

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

No branches or pull requests

2 participants