|
|
# Microscopy Pipeline Constructor (MyPiC)
|
|
|
|
|
|
MyPiC is a Visual Basic for Application (VBA) macro for Zeiss confocal microscopes running with the ZEN software (version black >= ZEN2010). The macro has been developed in the group of Jan Ellenberg, EMBL, Heidelberg and replaces the AutofocusScreenMacro.
|
|
|
MyPiC is a Visual Basic for Application (VBA) macro for Zeiss confocal microscopes running with the ZEN software (version black >= ZEN2010). The macro has been developed in the group of Jan Ellenberg, EMBL, Heidelberg, and replaces the AutofocusScreenMacro.
|
|
|
|
|
|
The macro allows
|
|
|
|
|
|
* Autofocus based on reflection and fluorescence multi-location time series.
|
|
|
* Fluorescence based tracking using the center of mass of the fluorescence signal.
|
|
|
* Multi-location time-lapse experiments.
|
|
|
* Flexible combination of several independent Z-stack and channel settings.
|
|
|
* Flexible combination of imaging with fluorescence correlation spectroscopy (FCS) experiments.
|
|
|
* Usage of several different FCS settings.
|
|
|
* [Adaptive Feedback microscopy support of two triggable imaging and FCS workflows](./AdaptiveFeedback)
|
|
|
* Autofocus based on reflection and fluorescence multi-location time series
|
|
|
* Fluorescence based tracking using the center of mass of the fluorescence signal
|
|
|
* Multi-location time-lapse experiments
|
|
|
* Flexible combination of several independent Z-stack and channel settings
|
|
|
* Flexible combination of imaging with fluorescence correlation spectroscopy (FCS) experiments
|
|
|
* Usage of several different FCS settings
|
|
|
* [Adaptive Feedback microscopy support of two triggerable imaging and FCS workflows](./AdaptiveFeedback)
|
|
|
|
|
|
**Adaptive feedback microscopy** combines microscopy acquisition with online image analysis to perform complex experiments without user supervision.
|
|
|
|
|
|
|
|
|
|
|
|
> **Disclaimer:**
|
|
|
> MyPiC has been tested on Zeiss LSM 780 microscopes with ZEN 2010, 2011, and 2012, and LSM880 microscopes with ZEN2.1 and ZEN2.3. We don’t guarantee that it will work on other configurations and we don’t take any responsibility for damage occuring during or after use of MyPiC.
|
|
|
> MyPiC has been tested on Zeiss LSM 780 microscopes with ZEN 2010, 2011, and 2012, and LSM880 microscopes with ZEN2.1 and ZEN2.3. We don’t guarantee that it will work on other configurations and we don’t take any responsibility for damage occuring during or after the use of MyPiC.
|
|
|
|
|
|
## Definitions
|
|
|
Throughout this manual we will use following definitions
|
|
|
Throughout this manual we will use the following definitions:
|
|
|
|
|
|
* **Imaging job**<a name = "imagingjob"></a>: Stores specific settings for imaging. The settings include laser power, Z-stack, pixel-dwell time etc. This are all the settings you can define in the ZEN software.
|
|
|
* **FCS job**<a name = "fcsjob"></a>: Stores specific settings to be used for FCS measurements.
|
|
|
* **Task**<a name = "task"></a>: An imaging or FCS job associated or not with additional processing steps, e.g. tracking in XY.
|
|
|
* **Pipeline**<a name = "pipeline"></a>: A concatenation of tasks that will be executed one of the other. In MyPiC we have a [Default pipeline](./Home/#default) that is executed at every position and 2 pipelines ([Trigger1 and Trigger2](./Home/#trigger)) that can be triggered from external programs (i.e. adaptive feedback microscopy).
|
|
|
* **Imaging job**<a name = "imagingjob"></a>: Stores specific settings for imaging. The settings include laser power, Z-stack, pixel dwell time, etc. These are all the settings that can be defined in the ZEN software
|
|
|
* **FCS job**<a name = "fcsjob"></a>: Stores specific settings used for FCS measurements
|
|
|
* **Task**<a name = "task"></a>: An imaging or FCS job which can be associated with additional processing steps, e.g. tracking in XY
|
|
|
* **Pipeline**<a name = "pipeline"></a>: A concatenation of tasks that will be executed one after the other. In MyPiC we have a [Default pipeline](./Home/#default) that is executed at every position and two pipelines ([Trigger1 and Trigger2](./Home/#trigger)) that can be triggered from external programs (i.e. adaptive feedback microscopy)
|
|
|
|
|
|
|
|
|
## Installation and start
|
|
|
|
|
|
* Copy the file *MyPiC.lvb* (for ZEN2010 use the file *MyPiC\_ZEN2010.lvb*) and the directory *resources* to a directory that can be accessed from the computer running ZEN.
|
|
|
* In ZEN Open the *Macro* tab (*Alt-F8*), click on *Edit Macro*.
|
|
|
* Copy the file *MyPiC.lvb* (for ZEN2010 use the file *MyPiC\_ZEN2010.lvb*) and the directory *resources* to a directory that can be accessed from the computer running ZEN
|
|
|
* In ZEN Open the *Macro* tab (*Alt-F8*), and click on *Edit Macro*
|
|
|
|
|
|
Load the macro into ZEN| Explanations of the buttons
|
|
|
--------------|----------------------------
|
|
|
<img src="./images/loadMacro.PNG" width = "400px"> | 1. Load the macro. Browse to the file *MyPiC.lvb* <br /> or *MyPiC\_ZEN2010.lvb* for older ZEN versions. <br /> 2. Run the macro. <br /> 3. To insert the macro in your list of macros click on the tab.
|
|
|
<img src="./images/assignMacro.PNG" width = "400px"> | provide a *Menu Entry*, a text, and select *MyPiC.lvb* as project.
|
|
|
<img src="./images/loadMacro.PNG" width = "400px"> | 1. Load the macro. Browse to the file *MyPiC.lvb* <br /> or *MyPiC\_ZEN2010.lvb* for older ZEN versions <br /> 2. Run the macro <br /> 3. To insert the macro in your list of macros click on the tab
|
|
|
<img src="./images/assignMacro.PNG" width = "400px"> | Provide a *Menu Entry*, a text, and select *MyPiC.lvb* as project
|
|
|
|
|
|
### Trouble shooting the installation
|
|
|
For any issues please contact one of the developers in the Ellenberg group at EMBL, Heidelberg and provide the version of the software, the full version of your ZEN software (Help->About), and all the log and err files. If you have a ZEN version higher than 2010 and the macro complains that it does not find ```Zeiss.Micro.AIM.ApplicationInterface.dll```, you may need to register it manually.
|
|
|
### Troubleshooting the installation
|
|
|
For any issues please contact one of the developers in the Ellenberg group at EMBL, Heidelberg, and provide the version of the software, the full version of your ZEN software (Help->About), and all the *log* and *err* files. If you have a ZEN version higher than 2010 and the macro complains that it does not find ```Zeiss.Micro.AIM.ApplicationInterface.dll```, you may need to register it manually.
|
|
|
|
|
|
You can try this fix
|
|
|
|
... | ... | @@ -49,17 +49,21 @@ You can try this fix |
|
|
|
|
|
• Register the ```Zeiss.Micro.AIM.ApplicationInterface.dll```
|
|
|
|
|
|
``` C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe /tlb /codebase Zeiss.Micro.AIM.ApplicationInterface.dll ```
|
|
|
```
|
|
|
C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe /tlb /codebase Zeiss.Micro.AIM.ApplicationInterface.dll
|
|
|
```
|
|
|
|
|
|
• When you uninstall ZEN, make sure to un-register
|
|
|
• When you uninstall ZEN make sure to un-register using
|
|
|
|
|
|
```C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe/u /tlb /codebase Zeiss.Micro.AIM.ApplicationInterface.dll```
|
|
|
```
|
|
|
C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe/u /tlb /codebase Zeiss.Micro.AIM.ApplicationInterface.dll
|
|
|
```
|
|
|
|
|
|
|
|
|
|
|
|
# <a name="back"></a> Setting up an experiment with MyPiC
|
|
|
|
|
|
After MyPiC has started the user proceeds through several steps before starting an experiment. When an experiment is repeated all settings can be reloaded from example images and configuration files (see [Start acquisition, save and reload settings](#startstop)).
|
|
|
After MyPiC has started, the user proceeds through several steps before starting an experiment. When an experiment is repeated all settings can be reloaded from example images and configuration files (see [Start acquisition, save and reload settings](#startstop)).
|
|
|
|
|
|
* [Create jobs using JobSetter](#jobsetter)
|
|
|
* [Create imaging jobs with the JobSetter](#jobsetterimaging)
|
... | ... | @@ -72,7 +76,7 @@ After MyPiC has started the user proceeds through several steps before starting |
|
|
* [File naming conventions](#naming)
|
|
|
* [Start acquisition, save and reload settings](#startstop)
|
|
|
|
|
|
An example workflow using glass relection autofocus or fluorescence based autofocus is given here
|
|
|
An example workflow using glass reflection autofocus or fluorescence based autofocus is given here
|
|
|
|
|
|
* [Simple workflows with MyPiC](#simpleexample)
|
|
|
* Glass based reflection and imaging
|
... | ... | @@ -91,7 +95,7 @@ The **JobSetter** is started by clicking on the corresponding button (1) *JobSet |
|
|
|
|
|
<div align = "center"><img src="./images/PipCon_upperpart.PNG"> </div>
|
|
|
|
|
|
In the JobSetter window the user can create [Imaging](#imagingjob) and [FCS](#fcsjob) jobs to be used in one or several [pipelines](#pipeline). The user specifies acquisition settings within ZEN and then upload the settings into the VBA macro as a job. Imaging jobs can also be created by loading a set of microscopy images (czi or lsm format) previously acquired on the same microscope.
|
|
|
In the JobSetter window the user can create [Imaging](#imagingjob) and [FCS](#fcsjob) jobs to be used in one or several [pipelines](#pipeline). The user specifies acquisition settings within ZEN and then uploads the settings into the VBA macro as a job. Imaging jobs can also be created by loading a set of microscopy images (czi or lsm format) previously acquired on the same microscope.
|
|
|
|
|
|
|
|
|
>**Caution** Do not load settings from images acquired on a different microscope. This may not work and impair the functionality of the system.
|
... | ... | @@ -101,15 +105,15 @@ In the JobSetter window the user can create [Imaging](#imagingjob) and [FCS](#fc |
|
|
|
|
|
JobSetter > Imaging Jobs | Explanations of the buttons
|
|
|
:-------| :-------------
|
|
|
<img src="./images/jobSetter.PNG" width = "400px">| 1. Create a new job with the current imaging settings <br /> 2. Load imaging jobs from saved images <br/> 3. Change name of current job (highlighted job) <br/> 4. Acquire all or one jobs and save images to disk <br/> 5. Remove a job from the list <br/> 6. Update current job with settings from ZEN <br/> 7. Load settings of current job into ZEN <br/> 8. Stop acquisition <br/> 9. Acquire current job <br/> 10. List of available jobs <br/> 11. Short description of current highlighted job <br/> 12. Available tracks for current job
|
|
|
<img src="./images/jobSetter.PNG" width = "400px">| 1. Create a new job with the current imaging settings <br /> 2. Load imaging jobs from saved images <br/> 3. Change name of current job (highlighted job) <br/> 4. Acquire one or all jobs and save images to disk <br/> 5. Remove a job from the list <br/> 6. Update current job with settings from ZEN <br/> 7. Load settings of current job into ZEN <br/> 8. Stop acquisition <br/> 9. Acquire current job <br/> 10. List of available jobs <br/> 11. Short description of current highlighted job <br/> 12. Available tracks for current job
|
|
|
|
|
|
#### Remarks for the imaging settings
|
|
|
|
|
|
* **Z-stack**: Use the option *Center* instead of *First\Last*, this has proven to be more reliable in the macro. This option is accessed when pressing the *Show all* option in the Z-stack menu-bar. Recenter the stack before loading into MyPiC.
|
|
|
* **Time-lapse**: The macro has its own time-lapse mode. For each time point an image is acquired and saved. However, the user can still load a job that contains Time-series. This can be useful for specific workflows.
|
|
|
* **Multi-position**: The macro allows the user to define a multi-position experiment. Multi-position defined within ZEN is allowed, however in this case the position in the macro should be set to single-position.
|
|
|
* **Definite Focus**: If the microscope has Zeiss *Definite focus* this can be be used within the macro. However note that the position of the focus stabilizer will be initiated at the current position stored in the macro.
|
|
|
* **Combine several imaging settings**: To minimize the hardware time-overhead it is best to optimize the different imaging settings so that the least hardware parts (e.g. MBS, pinhole) are modified between imaging jobs.
|
|
|
* **Z-stack**: Use the option *Center* instead of *First\Last*. This has proven to be more reliable in the macro. This option is accessed when pressing the *Show all* option in the Z-stack menu bar. Recenter the stack before loading into MyPiC
|
|
|
* **Time-lapse**: The macro has its own time-lapse mode. For each time point an image is acquired and saved. However, the user can still load a job that contains time series. This can be useful for specific workflows
|
|
|
* **Multi-position**: The macro allows the user to define a multi-position experiment. Multi-position defined within ZEN is allowed. However, in this case the position in the macro should be set to single position
|
|
|
* **Definite Focus**: If the microscope has Zeiss *Definite focus* this can be used within the macro. However note that the position of the focus stabilizer will be initiated at the current position stored in the macro
|
|
|
* **Combine several imaging settings**: To minimize the hardware time overhead it is best to optimize the different imaging settings so that the least hardware parts (e.g. MBS, pinhole) are modified between imaging jobs
|
|
|
|
|
|
### <a name=jobsetterfcs></a> Create FCS jobs with the JobSetter
|
|
|
|
... | ... | @@ -117,14 +121,14 @@ For FCS jobs the loading is similar as for imaging jobs. However, you can't load |
|
|
|
|
|
JobSetter > FCS Jobs | Explanations of the buttons
|
|
|
:-------| :------
|
|
|
<img src="./images/jobSetter_FCS.PNG" width = "400px"> | 1. Switch tab to load jobs for FCS <br /> 2. Add an FCS job. ZEN prompts the user to save the light-path configuration <br/>3. Change name of FCS job <br/> 4. Remove current FCS job <br/> 5. Update current job with settings from ZEN. ZEN promts user to save the light-path configuration <br/> 6. Load settings of current job into ZEN <br/> 7. Stop acquisition <br/> 8. Acquire current FCS measurement <br/> 9. List of available FCS jobs <br/> 10. Short description of current job
|
|
|
<img src="./images/jobSetter_FCS.PNG" width = "400px"> | 1. Switch tab to load jobs for FCS <br /> 2. Add an FCS job. ZEN prompts the user to save the light path configuration <br/>3. Change name of FCS job. <br/> 4. Remove current FCS job <br/> 5. Update current job with settings from ZEN. ZEN promts the user to save the light path configuration <br/> 6. Load settings of current job into ZEN <br/> 7. Stop acquisition. <br/> 8. Acquire current FCS measurement <br/> 9. List of available FCS jobs <br/> 10. Short description of current job
|
|
|
|
|
|
## [<img src="./images/up.PNG">](#back)<a name=default></a> Add tasks to the Default Pipeline
|
|
|
## [<img src="./images/up.PNG">](#back)<a name=default></a> Add tasks to the Default Pipeline
|
|
|
In a pipeline the user specifies the sequential order of imaging and FCS tasks from jobs previously loaded into the macro using the JobSetter. For a FCS task, FCS positions need to be specified via the adaptive feedback method otherwise the FCS measurement will not be acquired. The **Default pipeline** is the imaging workflow executed at every position and repetition.
|
|
|
|
|
|
Add task to a Default pipeline | Explanations of the buttons
|
|
|
:-------| :-------------
|
|
|
<img src="./images/PipCon_2DefaultPipeline_select.PNG" width = "400px"> | 1. Open select job window (3) <br/> 2. Remove current job in pipeline <br/> 3. Double click on a job to upload it in a pipeline. The GoTo jobs force the switch to a different pipeline
|
|
|
<img src="./images/PipCon_2DefaultPipeline_select.PNG" width = "400px"> | 1. Open window (3) with job list to select from <br/> 2. Remove current job in pipeline <br/> 3. Double click on a job to upload it in a pipeline. The GoTo jobs force the switch to a different pipeline
|
|
|
|
|
|
## [<img src="./images/up.PNG">](#back)<a name=taskopt></a>Set execution, saving, and processing options of a task
|
|
|
|
... | ... | @@ -138,17 +142,17 @@ For imaging tasks the user can specify further processing steps. For instance, t |
|
|
|
|
|
**Explanations of the buttons**
|
|
|
|
|
|
1. Set when task will be acquired. This is every *N* repetitions, or at start or end of repetitions
|
|
|
2. **Save**: Set if task should be saved or not
|
|
|
3. **Z-Offset** is added/subtracted from the current reference Z-position. This does not change reference Z-position for subsequent tasks
|
|
|
4. Execute all tasks in a pipeline once (use to test a pipeline)
|
|
|
1. Set when task will be acquired. This is every *N* repetitions or at the start or the end of repetitions.
|
|
|
2. **Save**: Set if task should be saved.
|
|
|
3. **Z-Offset**: Offset added/subtracted from the current reference Z position. This does not change the reference Z-position for subsequent tasks.
|
|
|
4. Execute all tasks in a pipeline once (used to test a pipeline).
|
|
|
5. Process Image/Tracking methods
|
|
|
* **None**: Do not perform any analysis
|
|
|
* **Center of mass (thr)**: Center of mass of upper 10% intensity. Optimal to compute position of glass reflection
|
|
|
* **None**: Do not perform any analysis.
|
|
|
* **Center of mass (thr)**: Center of mass of upper 10% intensity. Optimal to compute position of glass reflection .
|
|
|
* **Peak**: XYZ coordinate of maximal intensity
|
|
|
* **Center of mass**: Center of mass for the intensity. Optimal to track sparse bright objects
|
|
|
* **Online img. analysis**: Adaptive feedback option. Wait for feedback from an external image analysis program
|
|
|
6. **Channel**: channel to be used for precessing (does not apply for **Online img. analysis**)
|
|
|
6. **Channel**: Channel to be used for processing (does not apply for **Online img. analysis**)
|
|
|
7. **Track Z**: Update reference Z position with computed value
|
|
|
8. **Track XY**: Update XY position with computed value
|
|
|
|
... | ... | @@ -156,18 +160,18 @@ For imaging tasks the user can specify further processing steps. For instance, t |
|
|
|
|
|
## [<img src="./images/up.PNG">](#back)<a name=repetitions></a> Define repetitions
|
|
|
|
|
|
The user needs to define the time interval and number of repetitions executed at every position. Note that compared to ZEN ```Time Series``` mode the hardware time-overhead is higher (~0.5-2 sec depending on the settings) limiting the minimal time-interval. The advantage of MyPiC is to perform different type of images and optionally to combine the workflow with image analysis at every time-point and position. Each repetition is saved in a seperate file with the suffix *TXXXX*.
|
|
|
The user needs to define the time interval and number of repetitions executed at every position. Note that compared to ZEN ```Time Series``` mode the hardware time overhead is higher (~0.5-2 sec depending on the settings), limiting the minimal time-interval. The advantage of MyPiC is to perform different types of imaging and optionally to combine the workflow with image analysis at every time-point and position. Each repetition is saved in a seperate file with the suffix *TXXXX*.
|
|
|
|
|
|
Pipeline repetitions | Explanations of the buttons
|
|
|
:-------| -------------
|
|
|
<img src="./images/pipcon_repetitions.PNG" width = "400px"><img src="./images/interval_delay.PNG" width = "400px"> | 1. Delay/interval between images <br/> 2. Specify if the delay is in seconds or minutes <br/> 3. If checked time interval is between start of an image and the start of the next image (see image inset) <br/> 4. Number of repetitions
|
|
|
<img src="./images/pipcon_repetitions.PNG" width = "400px"><img src="./images/interval_delay.PNG" width = "400px"> | 1. Delay/interval between images <br/> 2. Specify if the delay is in seconds or minutes <br/> 3. If checked time, interval is between start of an image and the start of the next image (see image inset) <br/> 4. Number of repetitions
|
|
|
|
|
|
## [<img src="./images/up.PNG">](#back)<a name=positions></a> Define stage positions for the Default Pipeline
|
|
|
|
|
|
MyPiC allows the user to acquire images using different stage positions. Positions are specified by moving the stage and pressing the **Mark** (8) button in MyPiC. Positions and subpositions can also be loaded from a file.
|
|
|
|
|
|
* Wells/Positions: Specifiy a number of positions where imaging is performed. This could be for example wells in a multi-well sample.
|
|
|
* Subpositions: Subpositions are imaging positions defined with respect to wells/positions. Each Well/position can have one or several subpositions.
|
|
|
* Wells/Positions: Specify a number of positions where imaging is performed. This could be for example wells in a multi-well sample.
|
|
|
* Subpositions: Subpositions are imaging positions defined with respect to wells/positions. Each well/position can have one or several subpositions.
|
|
|
|
|
|
Default positions | Example on how (sub)positions are imaged and named
|
|
|
:---| :---
|
... | ... | @@ -175,10 +179,10 @@ Default positions | Example on how (sub)positions are imaged and named |
|
|
|
|
|
**Explanations of the buttons**
|
|
|
|
|
|
1. **Single**: performs imaging at current stage position
|
|
|
2. **Multiple**: Imaging at multiple positions specified by the user using **Mark** (8).
|
|
|
1. **Single**: performs imaging at current stage position
|
|
|
2. **Multiple**: Imaging at multiple positions specified by the user using **Mark** (8)
|
|
|
3. **Grid**: Use a regularly spaced grid + subgrid. The first marked position sets the first point of the grid
|
|
|
4. **Multiple + Subgrid**: For each position specified by the user a regular spaced subgrid is used (see 13-14)
|
|
|
4. **Multiple + Subgrid**: For each position specified by the user a regularly spaced subgrid is used (see 13-14)
|
|
|
5. **Load positions**: Load file with ending **.pos*
|
|
|
6. Save positions to a file **.pos*
|
|
|
7. List of positions
|
... | ... | @@ -189,11 +193,11 @@ Default positions | Example on how (sub)positions are imaged and named |
|
|
12. Number of rows and columns for grid and distance between grid points
|
|
|
13. Number of rows and columns for subgrid and distance between grid points
|
|
|
14. Position of subgrid with respect to main grid position (red circle)
|
|
|
* Left: Grid position is first subgrid position.
|
|
|
* Right: Grid position represents the center of the subgrid.
|
|
|
15. Order of imaging
|
|
|
* Left: Image all subpositions of a well and then move to next well.
|
|
|
* Right: Image one subposition of a well and then move to next well.
|
|
|
* Left: Grid position is the first subgrid position
|
|
|
* Right: Grid position represents the center of the subgrid
|
|
|
15. Order of imaging
|
|
|
* Left: Image all subpositions of a well and then move to the next well
|
|
|
* Right: Image one subposition of a well and then move to the next well
|
|
|
16. File name of **.pos* file to be loaded
|
|
|
|
|
|
|
... | ... | @@ -210,7 +214,7 @@ Saving directory | Explanations of the buttons |
|
|
> **Airy detector** For images acquired with the Airy detector the user must use the czi format.
|
|
|
|
|
|
### <a name=naming></a>File naming convention
|
|
|
Each time point and each position is saved in a separate file. The file name contains the ID for well, position, and time point. For the default pipeline this reads
|
|
|
Each time point and each position is saved in a separate file. The file name contains the ID for well, position, and time point. For the default pipeline this reads
|
|
|
|
|
|
``` DE_t_WXXXX_PYYYY_TZZZZ.* or basefilename_DE_t_WXXXX_PYYYY_TZZZZ.*```
|
|
|
|
... | ... | @@ -221,11 +225,11 @@ where |
|
|
* *YYYY*: 4 digit well identifier
|
|
|
* *ZZZZ*: 4 digit time point identifier
|
|
|
|
|
|
Each well is saved in a separate directory
|
|
|
Each well is saved in a separate directory named
|
|
|
|
|
|
``` DE_WXXXX_PYYYY ```
|
|
|
|
|
|
If number of subpositions is > 1 then there is a subdirectory per subposition
|
|
|
If the number of subpositions is > 1, there is a subdirectory per subposition.
|
|
|
|
|
|
```
|
|
|
DE_WXXXX
|
... | ... | @@ -235,14 +239,14 @@ DE_WXXXX |
|
|
## [<img src="./images/up.PNG">](#back) <a name=startstop></a> Start acquisition, save and reload settings
|
|
|
After all the previous steps have been performed, acquisition can be started from the main menu of MyPiC. To reload an experiment without performing every single step the user requires
|
|
|
|
|
|
* example-files of each imaging and/or FCS job to be loaded into MyPiC with the [JobSetter](#jobsetter) and the
|
|
|
* file containing the task specifications for each pipeline, *PipelineConstructor.ini*.
|
|
|
* example files of each imaging and/or FCS job to be loaded into MyPiC with the [JobSetter](#jobsetter) and the
|
|
|
* file containing the task specifications for each pipeline: *PipelineConstructor.ini*
|
|
|
|
|
|
A file *PipelineConstructor.ini* is automatically generated when the start-button has been pressed.
|
|
|
A file *PipelineConstructor.ini* is automatically generated when the start button has been pressed.
|
|
|
|
|
|
Start/stop/saving | Explanations of the buttons
|
|
|
:---|:---
|
|
|
<img src="./images/pipcon_startstop.PNG" width = "400px"> | 1. Start acquisition <br/> 2. Start acquisition and send commands to LabView water pump controller (optional) <br/> 3. Stop acquisition <br/> 4. Stop acquistion at the end of current repetition <br/> 5. Pause acquisition <br/> 6. Load pipelines settings from *PipelineConstructor.ini* file <br/>7. Save pipeline settings to a specific location <br/> 8. Show registry keys definitions for adaptive feedback/online image analysis
|
|
|
<img src="./images/pipcon_startstop.PNG" width = "400px"> | 1. Start acquisition <br/> 2. Start acquisition and send commands to LabView water pump controller (optional) <br/> 3. Stop acquisition <br/> 4. Stop acquistion at the end of the current repetition <br/> 5. Pause acquisition <br/> 6. Load pipeline settings from *PipelineConstructor.ini* file <br/>7. Save pipeline settings to a specific location <br/> 8. Show registry keys definitions for adaptive feedback/online image analysis
|
|
|
|
|
|
|
|
|
## [<img src="./images/up.PNG">](#back) <a name = simpleexample></a> Simple workflows with MyPiC
|
... | ... | @@ -250,25 +254,25 @@ Start/stop/saving | Explanations of the buttons |
|
|
|
|
|
### Glass based reflection autofocus and imaging
|
|
|
|
|
|
In this workflow at each repetition the microscope acquires a XZ scan and estimate the Z-position of the glass reflection line. Imaging is then performed at a certain Z-offset from this estimated position.
|
|
|
In this workflow at each repetition the microscope acquires a XZ scan and estimates the Z position of the glass reflection line. Imaging is then performed at a certain Z offset from this estimated position.
|
|
|
|
|
|
Define an autofocus job (named e.g. AF) and an imaging job (named e.g. LR). In MyPiC set in the Default pipeline as first task AF with processing **Center of Mass (thr)** and **Track Z**. The second task is LR. Specify a Z-offset value to achieve the required distance from the cover glass.
|
|
|
Define an autofocus job (named e.g. AF) and an imaging job (named e.g. LR). In MyPiC set in the Default pipeline as first task AF with processing **Center of Mass (thr)** and **Track Z**. The second task is LR. Specify a Z offset value to achieve the required distance from the cover glass.
|
|
|
|
|
|
|
|
|
For the imaging settings try to use the same light-path for both jobs. For example use 433 and 561 laser to image GFP and RFP and 633 to measure the glass surface reflection. For the autofocus choose a XZ line scan with several stacks. In absence of a piezo a larger DZ and smaller Z-range can be used in order to avoid a very slow acquisition.
|
|
|
For the imaging settings try to use the same light-path for both jobs. For example use 488nm and 561nm laser to image GFP and RFP and 633nm laser to measure the glass surface reflection. For the autofocus choose a XZ line scan with several stacks. In absence of a piezo a larger slice interval and smaller Z range can be used in order to avoid a slow acquisition.
|
|
|
|
|
|
> For the XZ reflection of glass scan do not use `Fast Z line`. This mode is not precise enough.
|
|
|
|
|
|
Example settings are given here
|
|
|
Example settings are given here:
|
|
|
|
|
|
**LR imaging settings** | **AF glass reflection settings**
|
|
|
:--- | :---
|
|
|
<img src="./images/acquisition_imagingSettings.PNG" width = "300px"> | <img src="./images/autofocus_imagingSettings.PNG" width = "300px">
|
|
|
**AF Scan mode** | **AF Z stack**
|
|
|
**AF scan mode** | **AF Z-stack**
|
|
|
<img src="./images/autofocus_scanMode_line.PNG" width = "300px"> | <img src="./images/autofocus_zStack.PNG" width = "300px">
|
|
|
|
|
|
|
|
|
### Fluorescence intensity center of mass based tracking
|
|
|
This workflow can be used to perform a tracking of bright objects in low resolution and imaging at high resolution of the object of interest. The pipeline works best for sparse objects. If several bright objects are in the same field of view than the tracking of a single object may fail.
|
|
|
This workflow can track bright objects at low resolution, followed by imaging the object of interest at high resolution. The pipeline works best for sparse objects. If several bright objects are in the same field of view, the tracking of a single object may fail.
|
|
|
|
|
|
Define a low-resolution job, named LR, with a large field of view (low zoom) and fast acquisition. Define a high-resolution job. Try to use similar light-path settings for the two jobs. Add to the default pipeline LR as first task with processing **Center of Mass** and **Track Z**, **Track XY**. Specify the channel to process. Add the HR job as second task. |
|
|
Define a low resolution job, named LR, with a large field of view (low zoom) and fast acquisition. Define a high resolution job, named HR. Try to use similar light-path settings for the two jobs. Add to the default pipeline LR as first task with processing **Center of Mass** and **Track Z**, **Track XY**. Specify the channel to process. Add the HR job as second task. |