FIX: Ordering of ITK displacements fields when reading and writing#266
FIX: Ordering of ITK displacements fields when reading and writing#266
Conversation
e4e2b0a to
076c4fa
Compare
|
@feilong apologies for the noise of the force-pushes |
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #266 +/- ##
==========================================
- Coverage 94.90% 0.00% -94.91%
==========================================
Files 16 16
Lines 1982 1991 +9
Branches 265 0 -265
==========================================
- Hits 1881 0 -1881
- Misses 78 1991 +1913
+ Partials 23 0 -23
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
|
@oesteban No worries. Happy to see the issue fixed in nitransforms. |
961a020 to
b807020
Compare
|
It doesn't look this transposition is the right answer (pictures extracted within the |
b807020 to
eee5a4e
Compare
449d396 to
3aeb18e
Compare
b20e1d9 to
1820103
Compare
ENH: Add unit test on dense fields (extracted from #266)
51672ed to
6d32a6f
Compare
Resolves: #267.
|
Keeping the branch for provenance purposes and for reference. |


Transposes data as suggested by @feilong when reading and writing ITK displacements fields.
Tests have been added to ensure round-trip consistency.
Related-to: #171.