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
docs:mm_dispim_plugin_user_guide [2019/10/26 00:07]
Jon Daniels [Data Analysis Tab] 		docs:mm_dispim_plugin_user_guide [2024/10/05 13:57] (current)
Jon Daniels [Save and Load]
Line 4: Line 4:
  
 If you are not familiar with Micro-Manager, please read the [[https://micro-manager.org/wiki/Micro-Manager_User%27s_Guide|User Guide]] and [[https://micro-manager.org/wiki/Micro-Manager_Configuration_Guide|Configuration Guide]] before running the plugin. Also, refer to the diSPIM manual: Getting started with Micro-Manager for guidance before aligning your diSPIM. If you are not familiar with Micro-Manager, please read the [[https://micro-manager.org/wiki/Micro-Manager_User%27s_Guide|User Guide]] and [[https://micro-manager.org/wiki/Micro-Manager_Configuration_Guide|Configuration Guide]] before running the plugin. Also, refer to the diSPIM manual: Getting started with Micro-Manager for guidance before aligning your diSPIM.
 +
 +Currently the diSPIM plugin is supported in 1.4.x only.  In 2023 there have been efforts to create a new plugin in Micro-Manager 2.0 called [[https://github.com/micro-manager/LightSheetManager|LightSheetManager]] that will operate the diSPIM as well as other types of light sheet microscopes.  Contributions to the effort of making this new plugin are appreciated.  As of August 2023 this is in alpha testing by the first few bleeding edge adopters, and we expect that by end of 2023 it will be ready for more adopters and a full replacement in 2024.
 +
 +You can download the nightly builds of Micro-manager 1.4 for Windows [[https://download.micro-manager.org/nightly/1.4/Windows/|here]]; the date is encoded in the file name and the latest date is at the top of the page.  Make sure to get the appropriate 32bit or 64bit depending on your computer.
  
 Before running the diSPIM plugin, create or load a Micro-Manager hardware configuration with all the relevant devices. The plugin is accessed through the Micro-Manager menu bar: **Plugins > Device Control > ASI diSPIM**. The plugin has 10 tabbed panels for different features and tasks. After opening the plugin, first configure the Devices Tab. Keep the main Micro-Manager window accessible; the plugin generally does not duplicate functionality already provided there. In addition to the tabbed panels, a sidebar provides a color coded “quick glance” indication of each axis’ position: Before running the diSPIM plugin, create or load a Micro-Manager hardware configuration with all the relevant devices. The plugin is accessed through the Micro-Manager menu bar: **Plugins > Device Control > ASI diSPIM**. The plugin has 10 tabbed panels for different features and tasks. After opening the plugin, first configure the Devices Tab. Keep the main Micro-Manager window accessible; the plugin generally does not duplicate functionality already provided there. In addition to the tabbed panels, a sidebar provides a color coded “quick glance” indication of each axis’ position:
Line 69: Line 73:
   - Click the green-bordered **Use these!** button to compute the slope and offset of the calibration relationship.   - Click the green-bordered **Use these!** button to compute the slope and offset of the calibration relationship.
   - Check the computed calibration using the up and down arrows in the upper right of the Setup tab (you may need to increase the step size).   - Check the computed calibration using the up and down arrows in the upper right of the Setup tab (you may need to increase the step size).
 +
 +For stage-scanning, the value of the calibration slope only matters if you want the value of the offset as measured in microns to match the physical world.  Normally you can just leave it at its default value.
  
 Generally the calibration slope will remain relatively constant but the offset can change slightly. It is easy to update the offset without changing the slope (e.g. when introducing a new sample): Generally the calibration slope will remain relatively constant but the offset can change slightly. It is easy to update the offset without changing the slope (e.g. when introducing a new sample):
Line 87: Line 93:
   - Use a very uniform sample, e.g. dye in solution.   - Use a very uniform sample, e.g. dye in solution.
   - Set the start/offset parameter to 0. This will be relatively close to the final value.   - Set the start/offset parameter to 0. This will be relatively close to the final value.
-  - While in live mode adjust the speed/slope parameter until the sheet exactly fills the field of view. This will be relatively close to the final value.+  - While in live mode adjust the speed/slope parameter until the sheet exactly fills the field of view. This will be relatively close to the final value.  With a Fusion camera this trick may yield half of the actually desired speed/slope parameter.
   - Run a test acquisition. Consider setting the acquisition mode to “No scan (fixed sheet)”. You should get images with some fluorescence. If only a short horizontal bright stripe appears then add a minus sign to the speed/slope parameter to invert the direction of the beam scanning.   - Run a test acquisition. Consider setting the acquisition mode to “No scan (fixed sheet)”. You should get images with some fluorescence. If only a short horizontal bright stripe appears then add a minus sign to the speed/slope parameter to invert the direction of the beam scanning.
   - Iteratively tune the two parameters by finding a best setting for one, adjusting the other, and so forth until you have zeroed in on the best setting. In each case the tuning procedure is to run a test acquisition, evaluate the results, and adjust the parameter again until you find the best setting where changing the setting in either direction gives worse results.   - Iteratively tune the two parameters by finding a best setting for one, adjusting the other, and so forth until you have zeroed in on the best setting. In each case the tuning procedure is to run a test acquisition, evaluate the results, and adjust the parameter again until you find the best setting where changing the setting in either direction gives worse results.
Line 124: Line 130:
 ===== Cameras Tab ===== ===== Cameras Tab =====
  
-The Region of Interest and camera triggering mode is specified in the Cameras tab. For Andor Zyla and Hamamatsu Flash4 cameras there is the possibility to have consecutive triggers determine the start and end of a image capture; this is termed respectively “Overlap” and “Synchronous” by the manufacturers but referred to uniformly as “Overlap” in the plugin. Because the image sensor is simultaneously read out and reset to begin the subsequent exposure, the camera overhead time is reduced and it allows for faster camera frame rates.8). The downside is that there can be slight “ghosting” or bleedthrough from frame to frame because the reset isn't quite complete. The same mode is not available with the PCO.edge or Photometrics Prime 95B. However, a new exposure can begin shortly after the readout starts which is a mode we refer to as “Pseudo Overlap”.+The Region of Interest and camera triggering mode is specified in the Cameras tab. For Andor Zyla and Hamamatsu Flash4 cameras there is the possibility to have consecutive triggers determine the start and end of a image capture; this is termed respectively "Overlap" and "Synchronous" by the manufacturers but referred to uniformly as “Overlap” in the plugin. Because the image sensor is simultaneously read out and reset to begin the subsequent exposure, the camera overhead time is reduced and it allows for faster camera frame rates. The downside is that there can be slight "ghosting" or bleedthrough from frame to frame because the reset isn't quite complete. The same mode is not available with the PCO.edge or Photometrics Prime 95B. However, a new exposure can begin shortly after the readout starts which is a mode we refer to as "Pseudo Overlap".  In cases where imaging speed is important it is usually a good idea to select "Overlap" or "Pseudo Overlap" camera modes.
  
 <imgcaption plugin_Cameras| The Cameras panel allows you to set the ROI and the acquisition trigger mode.>{{:docs:um-camerastab.png?600| diSPIM plugin Cameras tab}}</imgcaption> <imgcaption plugin_Cameras| The Cameras panel allows you to set the ROI and the acquisition trigger mode.>{{:docs:um-camerastab.png?600| diSPIM plugin Cameras tab}}</imgcaption>
  
 +==== Simultaneous Cameras ====
 +
 +This option was added so that multiple cameras could be used on the same path, e.g. a single-view SPIM with 4 different cameras to record each camera looking at a different spectral window at the same time.
 +
 +Due to Micro-Manager viewer limitations there are some oddities about this feature's implementation.  In simple cases with only 2 cameras it may be easier to instead use the setting on the Settings tab to record from 2 views simultaneously.  When using "Use simultaneous cameras on Path A" each "channel" in the dataset is a different camera as expected.  However if multiple channels are used also, each channel is assigned a portion of the resulting stack, and furthermore no time points are allowed.  For instance with 2 cameras and 3 sets of lasers and 50 slices in the stack the resulting dataset would have 2 channels and 150 slices.
 ===== Settings Tab ===== ===== Settings Tab =====
  
Line 138: Line 149:
 The scanner (micromirror) drive card has adjustable Bessel output filters to protect the filter from being driven near its mechanical resonance (usually 2 kHz). Settings as high as 0.8 kHz are usually acceptable, and in general the shorter the scan period (and faster frame rates) the more this matters. The scanner (micromirror) drive card has adjustable Bessel output filters to protect the filter from being driven near its mechanical resonance (usually 2 kHz). Settings as high as 0.8 kHz are usually acceptable, and in general the shorter the scan period (and faster frame rates) the more this matters.
  
 +==== Simultaneously acquire from both paths/cameras ====
  
 +This option was added to enable reflective imaging where cameras on both sides are triggered together (see https://www.nature.com/articles/s41467-017-01250-8).  Both cameras should be wired to the same trigger signal using e.g. a BNC "tee" at the Tiger controller output.
 +
 +Note this is similar but distinct from the option to acquire multiple cameras on Path A which is configured on the Cameras tab.  However in many cases either one can functionally be used.
 ===== Acquisition Tab ===== ===== Acquisition Tab =====
  
Line 186: Line 201:
 ==== Multiple Positions (XY) ==== ==== Multiple Positions (XY) ====
  
-If the box is checked, the plugin will use Micro-Manager’s position list to acquire volumes and multiple locations. For each time point, every position is visited once. See Micro-Manager User’s Guide for more details on the [[https://micro-manager.org/wiki/Micro-Manager_User%27s_Guide#Position_List_Dialog|Position List Dialog]].+If the box is checked, the plugin will use Micro-Manager’s position list to acquire volumes and multiple locations. For each time point, every position is visited once (i.e. the positions are an "inner loop" if both positions and time points are used). See Micro-Manager User’s Guide for more details on the [[https://micro-manager.org/wiki/Micro-Manager_User%27s_Guide#Position_List_Dialog|Position List Dialog]].
  
-For large samples there is a YZ grid creator (as of March 2018) so multiple strips can be collected covering a sample. Open the grid creator window by clicking on the "XYZ grid..." button.  Select the axes that you want to create the grid in and click the "Compute grid" button to set up the grid.  You can mark specific start/stop positions in live mode.  The delta for Y and Z can be entered manually, or if you click the button "Set" next to those fields then the value is populated based on the camera ROI and the overlap percentage setting.  Note that the X axis is used for stage scanning, so when you create a "grid" in X you are specifying start and stop positions and spacing between them in stage coordinates.+The XYZ grid creator facilitates acquisitions of multiple uniform strips to cover a large sample. Open the grid creator window by clicking on the "XYZ grid..." button.  The window houses a few other related features described below.
  
 +==== Using the Grid Creator ====
  
 +Select the axes that you want to create the grid in and click the "Compute grid" button to set up the grid.  For thin samples you do not need the Z grid.  You can mark specific start/stop positions in live mode using the corresponding "Set" buttons.  The delta for Y and Z can be entered manually, or if you click the "Set" button next to those fields then the value is populated based on the camera ROI and the overlap percentage setting.
  
-=== Overview Acquisition ===+The X axis is used for stage scanning, so when you create a "grid" in X you are specifying start and stop positions and spacing between them in stage coordinates.  If you enable "Slices from stage coordinates" in the XYZ grid window then the values "slices per side" and "slice step size" in the main acquisition window will be changed based on the settings in the XYZ grid window. 
 + 
 +The button "Compute Grid" will populate the position list with coordinates from the above settings.  This position list is in turn used with the Multiple Positions feature of the plugin. 
 + 
 + 
 + 
 +==== Overview Acquisition ====
  
 As of March 2019 there is a feature to acquire an overview acquisition.  This is useful when the entire sample is many times larger than the instantaneous field of view.  The overview image is a 2D image representing a thin slice of the sample which can be collected relatively quickly.  After acquisition, a rectangle is placed on the overview image representing the current stage position, and this rectangle moves with the stage as long as positions are being updated.  It is not intended for use with a Z grid but only XY grid. As of March 2019 there is a feature to acquire an overview acquisition.  This is useful when the entire sample is many times larger than the instantaneous field of view.  The overview image is a 2D image representing a thin slice of the sample which can be collected relatively quickly.  After acquisition, a rectangle is placed on the overview image representing the current stage position, and this rectangle moves with the stage as long as positions are being updated.  It is not intended for use with a Z grid but only XY grid.
  
-Settings for the overview acquisition reside on the "Data Analysis" tab.  These include the downsample factor for XY and for slice spacing.  The fractional thickness specifies how much of the entire image will be max projected to form the overview image.  You specify a channel and a side to run the overview acquisition with.+Some settings for the overview acquisition reside on the "Data Analysis" tab.  These include the downsample factor for XY and for slice spacing.  The fractional thickness specifies how much of the entire image will be max projected to form the overview image.  You specify a channel and a side to run the overview acquisition with. 
 + 
 +Running the overview acquisition with the thus-labeled button uses the current settings of the XYZ grid GUI for X and Y (if they are enabled) and will overwrite any existing position list. 
 + 
 + 
 +==== Planar Correction ==== 
 + 
 +This feature allows compensation for small deviations from completely horizontal sample mounting, which results in the sample leaving the FOV when X and Y are moved without moving Z.  When planar correction is enabled the Z position will very slightly move uniformly as the X position is scanned.  The slope is specified in Z movement proportional to X and Y positions plus an offset. 
 + 
 +The plugin can compute a the slopes and Z offset if you mark multiple XYZ positions where the sample is centered vertically and use the button "Compute correction from position list".  Alternatively the user can simply enter values themselves. 
 + 
 +Use requires BNC cable between PLogic #3 and TTL input of the Z axis card for proper triggering. 
 + 
 + 
 +==== XYZ Stage Limits ==== 
 + 
 +The purpose is to allow the user to define "limit planes" that need not be exactly along the X Y or Z axes.  This works in live mode based on the periodically-updated positions.  No provision is made to enforce these limits during acquisition. 
 + 
 +Specify the plane as satisfying a series of equations of form: A1*x + B1*y + C1*z < D1.  As a simple example, if you wanted to keep x between +1000 and -2000 then you would add the constraints 
 + 
 +A1=1, B1=C1=0, D1=1000 
 +A2=-1, B1=C1=0, D1=2000 
 + 
 + 
  
-Perform the overview acquisition using the button in the "XYZ grid..." window accessed from the acquisition tab.  Running the acquisition uses the current settings of the grid GUI for X and Y (if they are enabled) and will overwrite any existing position list. 
  
  
Line 204: Line 250:
  
 The channels feature is patterned after that of Micro-Manager’s [[https://micro-manager.org/wiki/Micro-Manager_User%27s_Guide#Multi-dimensional_acquisition|Multi-Dimensional Acquisition]]). It is most commonly used to take volumes with different illumination wavelengths (e.g. 488 nm and 561 nm for samples labeled with GFP and mCherry). Before using this feature, you must create and configure a group of presets containing the settings for that channel. The channels feature is patterned after that of Micro-Manager’s [[https://micro-manager.org/wiki/Micro-Manager_User%27s_Guide#Multi-dimensional_acquisition|Multi-Dimensional Acquisition]]). It is most commonly used to take volumes with different illumination wavelengths (e.g. 488 nm and 561 nm for samples labeled with GFP and mCherry). Before using this feature, you must create and configure a group of presets containing the settings for that channel.
-Simple per-volume channel switching is implemented unless a Programmable Logic Card (PLC) is present in the controller; this mode is generic and can be used with any Micro-Manager group. PLC-based channel switching is hardware-based, requiring extra setup time but then no delay during acquisition. Using the PLC, channel switching is possible on both a per-volume and per-slice basis. In this case the channel group must contain the property “Output Channel” which is used to select the correct laser to trigger; other properties in the channel group, if any, are ignored.+ 
 +Simple per-volume channel switching is generic and can be used with any Micro-Manager configuration group. Control of the acquisitions reverts to Micro-Manager between volumes so that Micro-Manager can e.g. move filter wheels to the specified positions, and then the ASI controller is re-triggered by Micro-Manager to collect the next volume.  The plugin requires a certain amount of time between finishing one volume and beginning the next so that the extra communication and control change can happen. 
 + 
 +Alternatively there are two hardware-based channel switching modes -- "Every volume (PLogic)" and "Every slice (PLogic)" -- which which leverage the PLC so that TTL triggering which happens within each volume continues across all volumes and control of the acquisition never returns to the host PC.  These hardware-based channel switching modes require a bit of extra setup time but no delay during acquisition.  The main limitation of the hardware-based channel modes is that they will only change the channel via the PLC property "Output Channel" which is used to select the correct laser to trigger (other properties in the channel group, if any, are ignored).  Mode "Every slice (PLogic)" interleaves the channels within the volume whereas "Every volume (PLogic)" changes channels between volumes.
  
 ==== Volume Settings ==== ==== Volume Settings ====
Line 219: Line 268:
  
 Distinguishing two nearby point sources of light is a classic problem in optics. If a camera’s pixels are so large that both points are read by the same pixel, you won't be able to tell them apart, regardless of how good the optics. The camera resolution must be at least twice the optical resolution to avoid being the limiting factor; essentially, a dark pixel must be between the two bright pixels. This is a manifestation of the Nyquist sampling theorem, which describes a fundamental mathematical relationship between continuous (or analog) and discrete (or digital) signals. Distinguishing two nearby point sources of light is a classic problem in optics. If a camera’s pixels are so large that both points are read by the same pixel, you won't be able to tell them apart, regardless of how good the optics. The camera resolution must be at least twice the optical resolution to avoid being the limiting factor; essentially, a dark pixel must be between the two bright pixels. This is a manifestation of the Nyquist sampling theorem, which describes a fundamental mathematical relationship between continuous (or analog) and discrete (or digital) signals.
-The standard formula for the optical lateral resolution is the Rayleigh criterion, a distance given by the formula: 0.61*lambda/NA (where lambda is the wavelength of light). For a 40X 0.8NA objective with 500 nm light, the lateral resolution is ~381 nm. That objective with a camera sensor that has a 6.5 um pixel pitch, is spatially sampling at (6.5 um/40X) ~162.5 nm pixel size, so we meet the Nyquist criteria (because 381 nm/162.5 nm = 2.34), but we wouldn't if we were using 400 nm light. + 
-Normally, for axial resolution limited by optics, the Z-axis step must be smaller than twice (per Nyquist) the optical axial resolution. Optical axial resolution, or depth of field, is usually taken to be lambda/(NA^2); for the 40X 0.8NA objective at 500 nm, it is ~781 nm. Therefore, the Z-step should be <0.39 nm.+The standard formula for the optical lateral resolution is the Rayleigh criterion, a distance given by the formula: 0.61*lambda/NA (where lambda is the wavelength of light). For a 40X 0.8NA objective with 500 nm light, the lateral resolution is ~381 nm. That objective with a camera sensor that has a 6.5 um pixel pitch, is spatially sampling at (6.5 um/40x) ~162.5 nm pixel size, so we meet the Nyquist criteria (because 381 nm/162.5 nm = 2.34), but we wouldn't if we were using 400 nm light. 
 +Normally, for axial resolution limited by optics, the Z-axis step must be smaller than twice (per Nyquist) the optical axial resolution. Optical axial resolution, or depth of field, is usually taken to be 2*lambda*RI/(NA^2); for the 40x 0.8 NA water objective at 500 nm, it is ~2.1 um. Therefore, the Z-step should be < 1 um. 
 For diSPIM, we have two views that can be merged computationally. The axial perspective from each objective is a lateral perspective (with higher resolution) from the other, so we can undersample in Z to a certain extent, which is advantageous from a speed perspective. However, giving up too much axial resolution the registration of the two views will suffer; in an extreme case your Z-step could be large enough to completely skip over a point source. For this reason, we recommend the Z-step be at least as small as the objective's depth of field. (With Fiji MVR and bead datasets, it's easy to register datasets with 0.5 um Z-step spacing but not with 1 um Z-step spacing.) For diSPIM, we have two views that can be merged computationally. The axial perspective from each objective is a lateral perspective (with higher resolution) from the other, so we can undersample in Z to a certain extent, which is advantageous from a speed perspective. However, giving up too much axial resolution the registration of the two views will suffer; in an extreme case your Z-step could be large enough to completely skip over a point source. For this reason, we recommend the Z-step be at least as small as the objective's depth of field. (With Fiji MVR and bead datasets, it's easy to register datasets with 0.5 um Z-step spacing but not with 1 um Z-step spacing.)
 </WRAP> </WRAP>
Line 241: Line 292:
 ==== Default Timing ====  ==== Default Timing ==== 
  
-Specify ​the **Sample ​exposure [ms]** in Slice Settings, ​and either define ​the slice period or let the plugin minimize the slice period automatically. The timing depends on the reset and readout time of the cameras; plugin code specific ​to each supported camera computes timings for the user-specified ​ROI using information provided by the manufacturer (usually either via their detailed camera documentation or read-only ​Micro-Manager ​properties). ​  Any extra time in the slice is placed before the camera trigger to allow maximum time for piezo settling. The values computed by the default timing mode are shown in the slice timing settings and can be subsequently modified manually.+Specify ​the **Sample ​exposure [ms]** in Slice Settings, ​and either define ​the slice period or let the plugin minimize the slice period automatically. The timing depends on the reset and readout time of the cameras as well as the trigger mode set on the [[docs:mm_dispim_plugin_user_guide#cameras_tab|Cameras tab]] (e.g. "Overlap/synchronous" trigger mode performs readout and reset at the same time whereas they are sequential in "Edge" mode).  Plugin code specific ​to each supported camera computes timings for the user-specified ​ROI using information provided by the manufacturer (usually either via their detailed camera documentation or read-only ​Micro-Manager ​properties). ​  Any extra time in the slice is placed before the camera trigger to allow maximum time for piezo settling. The values computed by the default timing mode are shown in the slice timing settings and can be subsequently modified manually.
  
 <WRAP center round tip 60%> <WRAP center round tip 60%>
Line 268: Line 319:
 In the future we would like to include the ability to manipulate the acquired data, including registration of the two views and joint deconvolution, directly in the diSPIM plugin. At present, the Data analysis tab, (<imgref plugin_DataAnalysis>), exports the acquired data to the format required by the MIPAV GenerateFusion plugin. Fiji’s Multiview Registration plugin can directly import diSPIM data. Exporting operates on the top-most image window. In the future we would like to include the ability to manipulate the acquired data, including registration of the two views and joint deconvolution, directly in the diSPIM plugin. At present, the Data analysis tab, (<imgref plugin_DataAnalysis>), exports the acquired data to the format required by the MIPAV GenerateFusion plugin. Fiji’s Multiview Registration plugin can directly import diSPIM data. Exporting operates on the top-most image window.
  
-<imgcaption plugin_DataAnalysis| The Data Analysis panel facilitates exporting acquisition data.>{{:docs:um-datatab.png?600| diSPIM plugin Data Analysis tab}}</imgcaption>+<imgcaption plugin_DataAnalysis| The Data Analysis panel facilitates exporting acquisition data.>{{:docs:um-dataanalyis-tab.png?600| diSPIM plugin Data Analysis tab}}</imgcaption>
  
-Based on the angle specified on the settings tab "Path A stage/objective angle", the pixel size defined in Micro-Manager’s “Pixel Size Calibration”, and slice spacing then the plugin runs the deskew.  If empirically it is off, check the "Invert direction" checkbox and try again.  Deskew fudge factor is an additional scale factor on the deskew and should generally be 1.+Based on the angle specified on the settings tab "Path A stage/objective angle", the pixel size defined in Micro-Manager’s “Pixel Size Calibration”, and slice spacing then the plugin runs the deskew.  If empirically it is off, check the "Invert direction" checkbox and try again.  Deskew fudge factor is an additional scale factor on the deskew and should generally be 1.  Rotate direction should be enabled if the data moves up/down in the raw data while scrolling through instead of left/right.
  
  
Line 280: Line 331:
  
 Once set up, it is likely best to use the new Multi Stage device via the Stage Control plugin rather than assigning it as a stage in the Micro-Manager plugin. Once set up, it is likely best to use the new Multi Stage device via the Stage Control plugin rather than assigning it as a stage in the Micro-Manager plugin.
 +
 +===== Acquisition Playlist =====
 +
 +The acquisition playlist allows you to run multiple acquisitions in sequence.
 +
 +You can drag and drop to reorder the acquisitions in the playlist. When you select an acquisition or position list, the previous item is automatically saved. You can also use the save button in the top right corner to save changes manually.
 +
 +To change what position list an acquisition is using, select the acquisition in the table, and click on the name of the position list in the "Position Lists" section. If an acquisition does not use a position list, select "None".
 +
 +When the "Run Acquisition Playlist" button is clicked, the plugin will automatically set acquisition failures to quiet and send any errors it encounters to the "Acquisition Status" text area. The plugin will automatically select "Save while acquiring" on the acquisition panel and close acquisition display windows after each acquisition.
 +
 +You can raise the diSPIM head between acquisitions by enabling the option in the settings tab, this will use the "Load Sample" position on the navigation tab as the position to raise the diSPIM head to.
 +
 +A note on channels: The plugin only saves channels with unique preset names, if two channels have the same preset only one of them will be saved. Also, only the used channels are saved, meaning the "Use?" checkbox must be checked.
 +
 +<imgcaption plugin_playlist| The acquisition playlist allows you to run multiple acquisitions in sequence.>{{:docs:manual:acq_playlist.png?direct| diSPIM Plugin Acquisition Playlist}}</imgcaption>
 +
 +==== Acquisition Table ====
 +
 +**Add:** Add a new acquisition to the table, the name must be unique.
 +
 +**Remove:** Removes an acquisition from the table.
 +
 +==== Acquisition Table Columns ====
 +
 +**#:** The order of the acquisitions.
 +
 +**Acquisition Name:** The unique name of the acquisition.
 +
 +**Save Name Prefix:** The prefix to be added to saved image data.
 +
 +**Save Directory Root:** The directory to save the captured images into.
 +
 +**Position List Name:** The name of the position list that this acquisition will use.
 +
 +==== Position Lists ====
 +
 +**Add:** Adds a new position list to the table, the name must be unique.
 +
 +**Remove:** Removes a position list from the table and remove it from any acquisition in the playlist using it.
 +
 +**Rename:** Renames a position list in the table and updates the name in the acquisition table.
 +
 +**Edit Position List:** Opens the Micro-Manager "Stage Position List" editor window.
 +
 +**XYZ grid:** Opens the XYZ grid frame which is also accessible from the acquisition panel.
 +
 +==== Acquisition Status ====
 +
 +**Current Acquisition:** The name of the running acquisition, such as "acq1".
 +
 +**Acquisition Status:** When the playlist is run this will show where we are in the playlist, an example being 2/3 if we on "acq2" in the playlist.
 +
 +**Run Acquisition Playlist:** Run each acquisition in the playlist sequentially. The current acquisition settings and selected position list are saved to the underlying acquisition table data before running.
 +
 +==== Save and Load ====
 +
 +**Save:** The top right button labeled "Save" will save any changes to the acquisition settings or Micro-Manager position list to the underlying table data.
 +
 +**Playlist Save Directory:** The directory to save metadata to after the acquisition playlist has run all acquisitions. This includes a json file of metadata that can be loaded into the plugin and the contents of the acquisition status log.
 +
 +**Save Playlist:** Save the acquisition playlist to a json file containing the acquisition settings, position lists, and the metadata that links the two. The current acquisition settings and selected position list are saved to the underlying acquisition table data before saving.
 +
 +**Load Playlist:** Load a json file into the acquisition playlist, populating the acquisition table and position lists.
 +
 +===== Plugin Settings =====
 +
 +The plugin settings are stored in the windows registry adjacent to other Micro-Manager settings at Computer\HKEY_CURRENT_USER\SOFTWARE\JavaSoft\Prefs\org\micromanager\asidispim.

Trace: