Repository navigation
Write NIfTI data in the byte order the header declares - #1061
Merged
Merged
Conversation
effigies
approved these changes
Sep 18, 2026
effigies
added
the
backport candidate
effigies
pushed a commit
that referenced
this pull request
Sep 28, 2026
effigies
pushed a commit
that referenced
this pull request
Oct 2, 2026
effigies
added a commit
that referenced
this pull request
Oct 2, 2026
1.14.5 (October 02, 2026) Patch release in the 1.14.x series. * FIX: Collect data interactions with sessions and bids filters (#1063) * FIX: Write NIfTI data in the byte order the header declares (#1061) * FIX: Drop bids_filters entries with no matching query (#1058) * FIX: Disable colorbar after default switch (#1057) * FIX: Use rigid affine initialization for BOLD mask (#1064)
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Closes #1029. array_to_file wrote the array in native byte order while the header kept its own, so a big-endian header produced little-endian data; passing header.get_data_dtype() keeps them consistent.