v0.5.3: [0.5.3] - 2019-01-12

Minor hot bugfix release

Fixed
- Do not shorten spaces in the dates while pretty printing .json

v0.5.2: [0.5.2] - 2019-01-04

A variety of bugfixes

Changed
- Reproin heuristic: `__dup` indices would now be assigned incrementally
  individually per each sequence, so there is a chance to properly treat
  associate for multi-file (e.g. `fmap`) sequences
- Reproin heuristic: also split StudyDescription by space not only by ^
- `tests/` moved under `heudiconv/tests` to ease maintenance and facilitate
  testing of an installed heudiconv
- Protocol name will also be accessed from private Siemens
  csa.tProtocolName header field if not present in public one
- nipype>=0.12.0 is required now

Fixed
- Multiple files produced by dcm2niix are first sorted to guarantee
  correct order e.g. of magnitude files in fieldmaps, which otherwise
  resulted in incorrect according to BIDS ordering of them
- Aggregated top level .json files now would contain only the fields
  with the same values from all scanned files. In prior versions,
  those files were not regenerated after an initial conversion
- Unicode handling in anonimization scripts

Heudiconv v0.5.1

[0.5.1] - 2018-06-29

Bugfix release

Added

• Video tutorial / updated slides
• Helper to set metadata restrictions correctly
• Usage is now shown when run without arguments
• New fields to Seqinfo
  • series_uid
• Reproin heuristic support for xnat

Changed

• Dockerfile updated to use dcm2niix v1.0.20180622
• Conversion table will be regenerated if heurisic has changed
• Do not touch existing BIDS files
  • events.tsv
  • task JSON

Fixed

• Python 2.7.8 and older installation
• Support for updated packages
  • Datalad 0.10
  • pydicom 1.0.2
• Later versions of pydicom are prioritized first
• JSON pretty print should not remove spaces
• Phasediff fieldmaps behavior
  • ensure phasediff exists
  • support for single magnitude acquisitions

v0.4: A "usable" release!

Since v0.3 a number of fixes (permissions settings, handling of datalad
support, etc).

TODO: We need to establishg a ChangeLog ;)