@@ -9,10 +9,6 @@ NiBabel Development Changelog
99NiBabel is the successor to the much-loved PyNifti package. Here we list the
1010releases for both packages.
1111
12- 'Close gh-' statements refer to GitHub issues that are available at::
13-
14- http://github.com/nipy/nibabel/issues
15-
1612The full VCS changelog is available here:
1713
1814 http://github.com/nipy/nibabel/commits/master
@@ -23,8 +19,8 @@ Releases
2319NiBabel
2420+++++++
2521
26- Most work on NiBabel so far has been by Matthew Brett (MB) and Michael Hanke
27- (MH) and Stephan Gerhard (SG).
22+ Most work on NiBabel so far has been by Matthew Brett (MB), Michael Hanke (MH)
23+ and Stephan Gerhard (SG).
2824
2925* 2.0.0 (soon)
3026
@@ -33,30 +29,35 @@ Most work on NiBabel so far has been by Matthew Brett (MB) and Michael Hanke
3329
3430 * New feature, bugfix release with minor API breakage;
3531 * Minor API breakage: default write of NIfTI / Analyze image data offset
36- value changed from keeping the value as read from file, to shrinking the
37- offset the minimum necessary to make room for the header and any
38- extensions;
39- * Minor API breakage: data scaling in NIfTI / Analyze now set to NaN when
40- reading images. To read the original data scaling you need to look at the
41- `` slope `` and `` inter `` properties of the image `` dataobj `` attribute;
42- * Minor API breakage: image data offset in NIfTI / Analyze now set to zero
43- when reading images. TO read the original data offset use the ``offset ``
32+ value. The data offset is the number of bytes from the beginning of file
33+ to skip before reading the image data. Nibabel behavior changed from
34+ keeping the value as read from file, to setting the offset to zero on
35+ read, and setting the offset when writing the header. The value of the
36+ offset will now be the minimum value necessary to make room for the header
37+ and any extensions when writing the file. You can override the default
38+ offset by setting value explicitly to some value other than zero. To read
39+ the original data offset as read from the header, use the ``offset ``
4440 property of the image ``dataobj `` attribute;
41+ * Minor API breakage: data scaling in NIfTI / Analyze now set to NaN when
42+ reading images. Data scaling refers to the data intercept and slope
43+ values in the NIfTI / Analyze header. To read the original data scaling
44+ you need to look at the ``slope `` and ``inter `` properties of the image
45+ ``dataobj `` attribute. You can set scaling explicitly by setting the
46+ slope and intercept values in the header to values other than NaN;
4547 * New API for managing image caching; images have an ``in_memory `` property
4648 that is true if the image data has been loaded into cache, or is already
4749 an array in memory; ``get_data `` has new keyword argument ``caching `` to
4850 specify whether the cache should be filled by ``get_data ``;
49- * Images now have properties ``dataobj ``, ``affine ``, ``header ``; we will
51+ * Images now have properties ``dataobj ``, ``affine ``, ``header ``. We will
5052 slowly phase out the ``get_affine `` and ``get_header `` image methods;
5153 * The image ``dataobj `` can be sliced using an efficient algorithm to avoid
52- reading unneccesary data from disk. This makes it possible to do very
54+ reading unnecessary data from disk. This makes it possible to do very
5355 efficient reads of single volumes from a time series;
54- * You can now set NIfTI / Analyze data scaling explicitly to force this
55- scaling to be written into the header;
5656 * NIfTI2 read / write support;
5757 * Read support for MINC2;
58- * Much extended read support for PAR / REC, largely due to the work of Eric
59- Larson and Gregory R. Lee giving new code, advice and code review;
58+ * Much extended read support for PAR / REC, largely due to work from Eric
59+ Larson and Gregory R. Lee on new code, advice and code review. Thanks also
60+ to Jeff Stevenson and Bennett Landman for helpful discussion;
6061 * ``parrec2nii `` script outputs images in LAS voxel orientation, which
6162 appears to be necessary for compatibility with FSL ``dtifit `` /
6263 ``fslview `` diffusion analysis pipeline;
@@ -65,19 +66,19 @@ Most work on NiBabel so far has been by Matthew Brett (MB) and Michael Hanke
6566 * New function to save Freesurfer annotation files (by Github user ohinds);
6667 * Method to return MGH format ``vox2ras_tkr `` affine (Eric Larson);
6768 * A new API for reading unscaled data from NIfTI and other images, using
68- ``img.dataobj.get_unscaled() ``; deprecate previous way of doing this with
69- ``read_img_data `` function;
70- * Bug fix replacing NaN values with zero when writing floating point data as
71- integers. If the input floating point data range did not include zero,
72- then NaN would not get written to a value corresponding to zero in the
73- output;
69+ ``img.dataobj.get_unscaled() ``. Deprecate previous way of doing this,
70+ which was to read data with the ``read_img_data `` function;
71+ * Fix for bug when replacing NaN values with zero when writing floating
72+ point data as integers. If the input floating point data range did not
73+ include zero, then NaN would not get written to a value corresponding to
74+ zero in the output;
7475 * Improvements and bug fixes to image orientation calculation and DICOM
7576 wrappers by Brendan Moloney;
76- * Bug fix writing GIfTI files with base64 encoding that didn't match the
77- spec, and the wrong field name for the endian code. Thanks to Basile
78- Pinsard and Russ Poldrack for diagnosis and fixes;
79- * Bug fix in freesurfer.read_annot with orig_ids=False when annot contains
80- vertices with no label (Alexandre Gramfort);
77+ * Bug fixes writing GIfTI files. We were using a base64 encoding that didn't
78+ match the spec, and the wrong field name for the endian code. Thanks to
79+ Basile Pinsard and Russ Poldrack for diagnosis and fixes;
80+ * Bug fix in `` freesurfer.read_annot `` with `` orig_ids=False `` when annot
81+ contains vertices with no label (Alexandre Gramfort);
8182 * More tutorials in the documentation, including introductory tutorial on
8283 DICOM, and on coordinate systems;
8384 * Lots of code refactoring, including moving to common code-base for Python
0 commit comments