Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision 		Previous revision
hardware:controller [2020/03/24 20:22]
Melissa Glidewell [Stage Scanning] added discussion on stage scan blurring 		hardware:controller [2024/02/16 17:54] (current)
Jon Daniels [Firmware]
Line 8: Line 8:
 In general firmware updates add new functionality and fix bugs while retaining backwards compatibility, though on rare occasion backward compatibility is compromised.  If you are not using Micro-Manager, you should double-check with the vendor of the acquisition software before updating firmware.  If you are using Micro-Manager, you should generally download the latest nightly build whenever you update firmware.  Conversely, if you are having problems with a recent build of Micro-Manager make sure that the controller firmware is the latest. In general firmware updates add new functionality and fix bugs while retaining backwards compatibility, though on rare occasion backward compatibility is compromised.  If you are not using Micro-Manager, you should double-check with the vendor of the acquisition software before updating firmware.  If you are using Micro-Manager, you should generally download the latest nightly build whenever you update firmware.  Conversely, if you are having problems with a recent build of Micro-Manager make sure that the controller firmware is the latest.
  
 +** Warning: these instructions are for iSPIM and diSPIM only.  If you have another type of ASI light sheet microscope (e.g. oSPIM or single-objective light sheet) contact ASI for guidance and for the proper firmware files.  **
 ==== Before you begin ==== ==== Before you begin ====
  
Line 15: Line 16:
 ==== Required software and instructions ==== ==== Required software and instructions ====
  
-To update the firmware you need the [[http://www.asiimaging.com/index.php/support/downloads/tiger-controller-console/|ASI Tiger Console]] software and the [[https://www.dropbox.com/sh/r5cabcfytu0e88f/AAD3IlCEpKInWmm2h4oh5_z6a?dl=1|latest diSPIM firmware package from ASI]] (last updated 2019-01-01, firmware version 3.23), or from the [[https://www.dropbox.com/sh/tpl82yahjz41nil/AABnSsCRDR_gRhxTiOi0srUJa?dl=0|diSPIM firmware archive]].  Use [[http://7zip.org|7zip]] to decompress. This firmware should work for diSPIM systems sold 2014 or later.  A link to download firmware for the oSPIM is found on the [[docs:ospim|oSPIM page]].+To update the firmware you need the [[http://www.asiimaging.com/index.php/support/downloads/tiger-controller-console/|ASI Tiger Console]] software and the [[https://www.dropbox.com/sh/r5cabcfytu0e88f/AAD3IlCEpKInWmm2h4oh5_z6a?dl=1|latest diSPIM firmware package from ASI]] (dated 2020-10-05, firmware version 3.33), or from the [[https://www.dropbox.com/sh/tpl82yahjz41nil/AABnSsCRDR_gRhxTiOi0srUJa?dl=0|diSPIM firmware archive]].  Use [[http://7zip.org|7zip]] to decompress. This firmware should work for diSPIM systems sold 2014 or later.  A link to download firmware for the oSPIM is found on the [[docs:ospim|oSPIM page]].
  
 General instructions for using the ASI Tiger Console software for updating the firmware are [[https://www.dropbox.com/s/j85783gltskreth/Using%20Dwayne%27s%20Tiger%20Console.pdf?dl=0|here]]. General instructions for using the ASI Tiger Console software for updating the firmware are [[https://www.dropbox.com/s/j85783gltskreth/Using%20Dwayne%27s%20Tiger%20Console.pdf?dl=0|here]].
Line 105: Line 106:
   * An alternative to deskewing is reslicing.  This can be as simple as reshuffling pixels in memory if the stage translation speed is chosen to be an integer number of pixels. Reslicing along the stage direction spreads the optical low-resolution between 2 axes but reduces the empty regions created by deskewing, particularly for long stage-scan stacks.  The following diagram hopefully helps:{{ :hardware:deskew_vs_reslice.jpg?600 |}}   * An alternative to deskewing is reslicing.  This can be as simple as reshuffling pixels in memory if the stage translation speed is chosen to be an integer number of pixels. Reslicing along the stage direction spreads the optical low-resolution between 2 axes but reduces the empty regions created by deskewing, particularly for long stage-scan stacks.  The following diagram hopefully helps:{{ :hardware:deskew_vs_reslice.jpg?600 |}}
   * It would be highly desirable for analysis and viewing software to be able to handle the deskew operation in memory and on the fly.  To date the only software known with this capability is FIJI's Big Data Viewer. Lobby your favorite software provider for this and make life better for everyone (many light sheet microscopes including lattice light sheet also require the same deskew step).   * It would be highly desirable for analysis and viewing software to be able to handle the deskew operation in memory and on the fly.  To date the only software known with this capability is FIJI's Big Data Viewer. Lobby your favorite software provider for this and make life better for everyone (many light sheet microscopes including lattice light sheet also require the same deskew step).
 +  * Micro-Manager 2.0 has a helpful ability to reslice data (an "Image Processor" added mid-2023) which is helpful especially for stage scanning data. The GPU version of the algorithm can operate on datasets up to 1/4 of the GPU memory, e.g. 2 GB datasets can be processed on a GPU with 8 GB of working memory.  The GPU version does interpolation and the CPU version is faster but doesn't do any interpolation.
 ==== Micro-Manager Implementation Notes ==== ==== Micro-Manager Implementation Notes ====
   * The spacing between slices is specified in the plugin, so the stage moves sqrt(2) times that distance per slice for 45 degree geometry (the actual angle can be set as of March 2018). There may be very small rounding errors (which would come out in normal post-processing) but the metadata should contain the actual slice spacing instead of the user-specified one.  Rounding errors were reduced as of the 2018-03-15 nightly build.   * The spacing between slices is specified in the plugin, so the stage moves sqrt(2) times that distance per slice for 45 degree geometry (the actual angle can be set as of March 2018). There may be very small rounding errors (which would come out in normal post-processing) but the metadata should contain the actual slice spacing instead of the user-specified one.  Rounding errors were reduced as of the 2018-03-15 nightly build.

Trace: