ENH: Add PET info to nipreps.json #942
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@mnoergaard This is being released in 1.13.3 right now. |
effigies
added a commit
that referenced
this pull request
May 9, 2025
1.13.3 (May 09, 2025) Patch release in the 1.13.x series. This release resolves import errors introduced by excluding excess files in the previous release. Only test modules were affected. * ENH: Add PET info to nipreps.json (#942)
|
Great - many thanks @effigies |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR closes issue #941 adding PET information to the nipreps.json file, allowing workflows that are using niworkflows to use the BIDS interface and Derivatives DataSink to create output paths.