ScanImage r3.5.1 is an incremental release, relative to r3.5. It is being co-released with ScanImage r3.6, primarily as a benefit to legacy users. The most notable change is a restoration of Cycle mode functionality, which had been broken in r3.5. Cycle mode is a feature allowing a sequence of acquisitions to be obtained at a list of pre-defined motor positions.
For users already using Cycle mode or requiring such functionality in their work, ScanImage r3.5.1 should now be used. All other users, both new and old should migrate/adopt ScanImage r3.6 instead.
Find below a listing of all notable enhancements/changes/bugixes in r3.5.1. Refer further below to the ScanImage 3.5.0 README for information on the original r3.5 release.
Enhancements
- Trigger time is now logged with increased accuracy to the TIF header file
- LOOP periods timing now occurs with greater accuracy
- Spine counting analysis software has been added to the distribution, and is accessible as scim_spineAnalysis()
- RepeatPeriod and RepeatsTotal values are now stored to image header
- Double-move is avoided during cycle operations when both a cycle and stack home are defined, saving inter-Repeat time
- The number of cycles to execute can now be specified in the Cycle Controls window
Changes
- Distribution has a new directory structure, consisting of 2 directories – ScanImage and scim. The latter directory contains various utility functions beginning with prefix scim that are intended/available for the user. The new directory structure matches that of r3.6.
- The standard_model.INI file now contains only those values which can or need to be edited by user for their rig. The remaining values, not to be user-edited, are now stored in a separate internal.INI file as part of the distribution. This new scheme matches that of r3.6.
Bugfixes
- Cycle mode was completely unoperational in r3.5 with a show-stopper bug.
- The UserFcn GUI was not working properly due to a case-sensitivity bug.
- The option for 'safe' hot-keys in the User Preferences dialog was being ignored
- Saving USR file was not correctly saving the currently active Configuration (CFG File)
- GUI controls would be blanked out when FOCUS mode acquisition ended by timeout, rather than explicit Abort
- High pixel value in LUTs could be below low pixel value
- Resets of merge window following configuration changes had dimensions transposed