Version 5.0.2 (R14SP2) Image Processing Toolbox™ :: Image Processing Toolbox™ Release Notes (Image Processing Toolbox™)

Version 5.0.2 (R14SP2) Image Processing Toolbox™ Release Notes

Version 5.1 (R14SP3) Image Processing Toolbox™

Version 5.0.1 (R14SP1) Image Processing Toolbox™

Version 5.0.2 (R14SP2) Image Processing Toolbox™

This table summarizes what's new in Version 5.0.2 (R14SP2):

New Features and Changes	Version Compatibility Considerations	Fixed Bugs and Known Problems	Related Documentation at Web Site
No	Yes—Details labeled as Compatibility Considerations, below. See also Summary.	Bug fixes Details	No

New features and changes introduced in this version are

Major Bug Fixes

This release contains the following bug fixes.

Major Revisions to Fan-Beam Functions

This release includes numerous updates and improvements to the fan-beam functions: fanbeam, ifanbeam, fan2para, and para2fan. The fixes include improved calculations, improved documentation, and examples.

For example, fanbeam now returns the correct sensor locations when the geometry is 'line'. The ifanbeam and fan2para now consistently use the correct default value for the 'FanSensorSpacing' parameter. If you tried the fan-beam functions in a previous release, you might try them again to take advantage of these improvements.

In addition to the functional changes, many improvements to the documentation of the fan-beam functions have been made.

fanbeam help now includes

An example that shows how to extract projection data at a specific rotation angle from the fan-beam data returned
An explanation of how fanbeam calculates the number of rows and columns in F, the fan-beam data returned
The default value for the 'FanSensorSpacing' parameter for both 'line' and 'arc' geometries
Guidelines for setting the value of the D parameter

The help for the ifanbeam function now includes an example that shows how to use the 'minimal' coverage parameter.

Compatilbility Considerations. Results computed with earlier versions of the fan-beam functions cannot be used with the new versions of these functions.

Changes to the DICOM Functions

The following fixes have been made to the dicomread and dicomwrite functions.

Function	Bug Fixes
`dicomread`	No longer errors when reading files that contain extraneous pixel data; instead, `dicomread` issues a warning message. However, if the file does not contain enough pixel data, `dicomread` issues an error.
`dicomwrite`	No longer is case sensitive when parsing input parameters. For example, you can specify either `'CreateMode'` or `'createmode'`. Preserves the full precision of data converted to decimal string metadata. Previously, `dicomwrite` limited precision to six digits. No longer errors when writing files with metadata values that must be stored as a decimal string or integer string. Now, when writing private data attributes (attributes that are not listed in the DICOM data dictionary), `dicomwrite` assigns the attributes the type `UN` (for unknown) and writes the data to the file as a byte-for-byte copy of its in-memory representation. Because `dicomwrite` writes the file with explicit value representation (VR), the file might have a different VR value, but the data will be the same. Includes the `TriggerTime` field for additional values of `ScanOptions`, including `'CT'`. Previously, `dicomwrite` only included the `TriggerTime` attribute if the `ScanOptions` field indicated a gated heart MR. No longer issues an `Unsupported SOP class` error message if, when `'create'` mode is specified, semantic verification is not available for an information object. Instead, `dicomwrite` issues a more helpful message indicating that it might be able to write the data if the mode was `'copy`', rather than `'create'`. In `'copy'` mode, `dicomwrite` only performs syntactic checking, not semantic verification. Consequently, `dicomwrite` can write many more types of DICOM files in `'copy'` mode than it can in `'create'` mode. See the `dicomwrite` reference page for important information about data integrity.

Function

Bug Fixes

dicomread

No longer errors when reading files that contain extraneous pixel data; instead, dicomread issues a warning message. However, if the file does not contain enough pixel data, dicomread issues an error.

dicomwrite

No longer is case sensitive when parsing input parameters. For example, you can specify either 'CreateMode' or 'createmode'.
Preserves the full precision of data converted to decimal string metadata. Previously, dicomwrite limited precision to six digits.
No longer errors when writing files with metadata values that must be stored as a decimal string or integer string. Now, when writing private data attributes (attributes that are not listed in the DICOM data dictionary), dicomwrite assigns the attributes the type UN (for unknown) and writes the data to the file as a byte-for-byte copy of its in-memory representation. Because dicomwrite writes the file with explicit value representation (VR), the file might have a different VR value, but the data will be the same.
Includes the TriggerTime field for additional values of ScanOptions, including 'CT'. Previously, dicomwrite only included the TriggerTime attribute if the ScanOptions field indicated a gated heart MR.
No longer issues an Unsupported SOP class error message if, when 'create' mode is specified, semantic verification is not available for an information object. Instead, dicomwrite issues a more helpful message indicating that it might be able to write the data if the mode was 'copy', rather than 'create'. In 'copy' mode, dicomwrite only performs syntactic checking, not semantic verification. Consequently, dicomwrite can write many more types of DICOM files in 'copy' mode than it can in 'create' mode. See the dicomwrite reference page for important information about data integrity.

Changes to Image Tool and Modular Interactive Tools

The following fixes have been made to the Image Tool and other modular interactive tools:

The Image Tool now always makes the Open and Import from Workspace options available on its File menu. Previously, the Image Tool disabled these options if the tool contained an image. If the Image Tool contains an image, the newly imported image is displayed in a new Image Tool using the default preferences.
The Image Tool zoom buttons can now be used on an image that has superimposed vector data.
The Image Tool toolbar buttons no longer create multiple versions of the modular interactive tools when clicked rapidly in quick succession.
The Image Information tool now displays correctly on Linux^® systems. Previously, it displayed as a blank window.
The Overview tool can now be resized from any corner. Previously, resizing the tool using a corner other than the lower left caused the image to become progressively smaller until it disappeared.
The Overview tool zoom buttons now provide an affordance that informs users when they cannot use these buttons to zoom in or out on the image displayed in the associated scroll panel.
The Pixel Region tool now displays floating-point values correctly. Previously, the pixel value text strings displayed spilled over into adjacent pixels for some floating-point images.
The Pixel Region tool now works correctly with images displayed in subplots.
The Pixel Region tool no longer causes the target image to become tiny and move to a different position in the figure.

Changes to the imshow Function

The imshow function no longer overwrites nondefault axes in a figure.
The imshow function ignores any initial magnification value you specify when used to display an image in a figure that is docked (the figure's WindowStyle property is set to 'docked'). In these cases, imshow displays the image at the largest magnification that fits the window ('fit' magnification) and issues a warning.

Fixes to Other Functions

The following tables lists fixes that have been done to other toolbox functions.

Function	Enhancement
`applycform`	Now correctly handles profiles that contain a `gamut` tag.
`cpcorr`	Now is more numerically robust. For this release, the subfunction `findpeak`, which `cpcorr` calls, has been improved and is now a private function, rather than a subfunction.
`imhist`	No longer causes a docked figure window to become undocked.
`imrotate`	Now correctly rotates N-dimensional arrays, where N is greater than 3. In previous releases, `imrotate` would accept N-D arrays but only return a 3-D array.
`normxcorr2`	Now always returns real values. In previous releases, due to roundoff error, some sets of input data caused the `normxcorr2` function to return a complex valued matrix of correlation coefficients.
`pixval`	Now works correctly with binary images.
`rgb2ind`	Now returns a correct output image when called with the syntax rgb2ind(rgb,n,'nodither') where `n` is greater than 256.

Fixes to Image Processing Toolbox™ Deployment Issues

Performance issues that occurred when deploying compiled image processing toolbox functions that call IPPL routines have been fixed.

Running compiled versions of imtool and some of the other modular interactive tools no longer generates the following warning messages about classes not being cleared:

Warning: Objects of graphics.linkprop class exist - not clearing
this class or any of its super-classes.
Warning: An object instance still exists. Use the objectdirectory
command to see a count of existing instances.

Compatibility Considerations

The Image Processing Toolbox™ software now requires the following new directory on the MATLAB^® path:

toolbox\shared\imageslib

Version 5.1 (R14SP3) Image Processing Toolbox™

Version 5.0.1 (R14SP1) Image Processing Toolbox™