NOTICE! This is a static HTML version of a legacy ImageJ Trac ticket.

The ImageJ project now uses GitHub Issues for issue tracking.

Please file all new issues there.

Ticket #1703 (closed defect: fixed)

Opened 2013-03-19T14:31:03-05:00

Last modified 2013-06-04T11:40:44-05:00

Automatic binary image conversion can be unexpected

Reported by: bdezonia Owned by: bdezonia
Priority: major Milestone: imagej2-b7-ndim-data
Component: Legacy Compatibility Version:
Severity: serious Keywords:
Cc: Blocked By:
Blocking: #1563


Create a new 8-bit unsigned image filling with either White or Black only. Now run Image > Properties command and hit OK (no changes to fields necessary). Now Save Image As: it fails with an error message about unsupported pixel type.

Debugging one can see that the underlying data type of the Img is BitType. After the Properties command runs the Harmonizer determines that the image is a binary image in IJ1's terms (8-bit with all pixels 0 or 255). So the image is converted to 1-bit. In this case the user probably doesn't want this.

Determine whether to do this kind of conversion in the harmonization step. We made a point of adding it but perhaps we were hasty in our decision.

Change History

comment:1 Changed 2013-03-19T14:31:36-05:00 by bdezonia

  • Blocking 1563 added

comment:2 Changed 2013-04-03T13:49:44-05:00 by bdezonia

  • Priority changed from major to minor

comment:3 Changed 2013-04-03T13:50:19-05:00 by bdezonia

  • Priority changed from minor to major

comment:4 Changed 2013-05-17T15:02:56-05:00 by bdezonia

Automatic conversion to 1-bit ImageJ2 data is no longer in place on the scifiocells branch. Once that code is merged this ticket can be considered fixed.

comment:5 Changed 2013-06-04T11:40:44-05:00 by bdezonia

  • Status changed from new to closed
  • Resolution set to fixed

Code merged. Closing.