... | @@ -45,36 +45,36 @@ Throughout this manual we will use following definitions |
... | @@ -45,36 +45,36 @@ Throughout this manual we will use following definitions |
|
|
|
|
|
# <a name="back"></a> Setting up an experiment with MyPiC
|
|
# <a name="back"></a> Setting up an experiment with MyPiC
|
|
|
|
|
|
After MyPiC has started the user needs to proceed through several steps before starting an experiment.
|
|
After MyPiC has started the user proceeds through several steps before starting an experiment:
|
|
|
|
|
|
1. [Load/create jobs using JobSetter](#jobsetter)
|
|
1. [Create jobs using JobSetter](#jobsetter)
|
|
* [Load/create imaging jobs](#jobsetterimaging)
|
|
* [Create imaging jobs with the JobSetter](#jobsetterimaging)
|
|
* [Load/create FCS jobs (optional)](#jobsetterfcs)
|
|
* [Create FCS jobs with the JobSetter](#jobsetterfcs)
|
|
2. [Add jobs to the Default pipeline](#default)
|
|
2. [Add tasks to the Default Pipeline](#default)
|
|
3. [Execution, saving, and processing options for each task](#taskopt)
|
|
3. [Set execution, saving, and processing options of a task](#taskopt)
|
|
4. [Define the repetitions](#repetitions)
|
|
4. [Define repetitions](#repetitions)
|
|
5. [Define stage positions for default pipeline](#positions)
|
|
5. [Define stage positions for the Default Pipeline](#positions)
|
|
6. [Define saving directory](#saving)
|
|
6. [Define the saving options](#saving)
|
|
* [Naming conventions](#naming)
|
|
* [Naming conventions](#naming)
|
|
7. [Start and stop acquisition, save and reload settings](#startstop)
|
|
7. [Start acquisition, save and reload settings](#startstop)
|
|
8. [Adaptive feedback microscopy/Online image analysis](#adaptivefeedback)
|
|
8. [Adaptive feedback microscopy/Online image analysis](#adaptivefeedback)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
## [<img src="./images/up.PNG">](#back)<a name=jobsetter></a> Load jobs in the JobSetter
|
|
## [<img src="./images/up.PNG">](#back)<a name=jobsetter></a> Create jobs in the JobSetter
|
|
|
|
|
|
The **JobSetter** is started by clicking on the corresponding button (1) *JobSetter*
|
|
The **JobSetter** is started by clicking on the corresponding button (1) *JobSetter*
|
|
|
|
|
|
|
|
|
|
<div align = "center"><img src="./images/PipCon_upperpart.PNG"> </div>
|
|
<div align = "center"><img src="./images/PipCon_upperpart.PNG"> </div>
|
|
|
|
|
|
In the JobSetter window the user can create several [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 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.
|
|
|
|
|
|
|
|
|
|
>**Caution** Do not load settings from images acquired on a different microscope. This may not work and impair the functionality of the system.
|
|
>**Caution** Do not load settings from images acquired on a different microscope. This may not work and impair the functionality of the system.
|
|
|
|
|
|
|
|
|
|
### <a name=jobsetterimaging></a> Load/create imaging jobs
|
|
### <a name=jobsetterimaging></a> Create imaging jobs with the JobSetter
|
|
|
|
|
|
JobSetter > Imaging Jobs | Explanations of the buttons
|
|
JobSetter > Imaging Jobs | Explanations of the buttons
|
|
:-------| :-------------
|
|
:-------| :-------------
|
... | @@ -88,7 +88,7 @@ JobSetter > Imaging Jobs | Explanations of the buttons |
... | @@ -88,7 +88,7 @@ JobSetter > Imaging Jobs | Explanations of the buttons |
|
* **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.
|
|
* **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.
|
|
* **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> Load/create FCS jobs
|
|
### <a name=jobsetterfcs></a> Create FCS jobs with the JobSetter
|
|
|
|
|
|
For FCS jobs the loading is similar as for imaging jobs. However, you can't load the settings directly from a file into the JobSetter. If using a file, please load the file into ZEN and press ```Re-use```. Several FCS settings can be stored. For this the user must use different names of the light-path for each FCS job.
|
|
For FCS jobs the loading is similar as for imaging jobs. However, you can't load the settings directly from a file into the JobSetter. If using a file, please load the file into ZEN and press ```Re-use```. Several FCS settings can be stored. For this the user must use different names of the light-path for each FCS job.
|
|
|
|
|
... | @@ -96,14 +96,14 @@ JobSetter > FCS Jobs | Explanations of the buttons |
... | @@ -96,14 +96,14 @@ 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 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 an 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.
|
|
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 an 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
|
|
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 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/up.PNG">](#back)<a name=taskopt></a>Execution, saving, and processing options for a task
|
|
## [<img src="./images/up.PNG">](#back)<a name=taskopt></a>Set execution, saving, and processing options of a task
|
|
|
|
|
|
|
|
|
|
For each imaging and FCS [task](#task) several options can be specified. These determine when to execute and save a task. Furthermore, the user can set a ```Z-offset``` with respect to the reference Z-location (see also [Define stage positions for default pipeline](#positions)).
|
|
For each imaging and FCS [task](#task) several options can be specified. These determine when to execute and save a task. Furthermore, the user can set a ```Z-offset``` with respect to the reference Z-location (see also [Define stage positions for default pipeline](#positions)).
|
... | @@ -115,7 +115,7 @@ For imaging tasks the user can specify further processing steps. For instance, t |
... | @@ -115,7 +115,7 @@ For imaging tasks the user can specify further processing steps. For instance, t |
|
|
|
|
|
** Explanations of the buttons**
|
|
** Explanations of the buttons**
|
|
|
|
|
|
1. Specifies when task will be acquired. This is every *N* repetitions, or at start or end of repetitions
|
|
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
|
|
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
|
|
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)
|
|
4. Execute all tasks in a pipeline once (use to test a pipeline)
|
... | @@ -131,7 +131,7 @@ For imaging tasks the user can specify further processing steps. For instance, t |
... | @@ -131,7 +131,7 @@ For imaging tasks the user can specify further processing steps. For instance, t |
|
|
|
|
|
|
|
|
|
|
|
|
|
## [<img src="./images/up.PNG">](#back)<a name=repetitions></a> Define the repetitions
|
|
## [<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 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 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*.
|
|
|
|
|
... | @@ -139,7 +139,7 @@ Pipeline repetitions | Explanations of the buttons |
... | @@ -139,7 +139,7 @@ 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 default pipeline
|
|
## [<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.
|
|
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.
|
|
|
|
|
... | @@ -175,7 +175,7 @@ Default positions | Example on how (sub)positions are imaged and named |
... | @@ -175,7 +175,7 @@ Default positions | Example on how (sub)positions are imaged and named |
|
|
|
|
|
|
|
|
|
|
|
|
|
## [<img src="./images/up.PNG">](#back) <a name=saving></a>Define saving directory
|
|
## [<img src="./images/up.PNG">](#back) <a name=saving></a>Define the saving options
|
|
|
|
|
|
Images and FCS measurements are saved in a main directory specified by the user. A sub-directory per position/subposition is automatically generated.
|
|
Images and FCS measurements are saved in a main directory specified by the user. A sub-directory per position/subposition is automatically generated.
|
|
|
|
|
... | @@ -208,20 +208,22 @@ DE_WXXXX |
... | @@ -208,20 +208,22 @@ DE_WXXXX |
|
DE_WXXXX_PYYYY
|
|
DE_WXXXX_PYYYY
|
|
```
|
|
```
|
|
|
|
|
|
## [<img src="./images/up.PNG">](#back) <a name=startstop></a> Start and stop acquisition, save and load settings
|
|
## [<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 steps the user requires
|
|
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 or FCS job](#jobsetter) and the
|
|
* 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*. This file is automatically generated when the start-button is pressed.
|
|
* file containing the task specifications for each pipeline, *PipelineConstructor.ini*.
|
|
|
|
|
|
Start stop | Explanations of the buttons
|
|
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 online image analysis registry keys
|
|
<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 adpative feedback/online image analysis
|
|
|
|
|
|
|
|
|
|
# [<img src="./images/up.PNG">](#back) <a name="adaptivefeedback"></a> Adaptive feedback microscopy/Online image analysis
|
|
# [<img src="./images/up.PNG">](#back) <a name="adaptivefeedback"></a> Adaptive feedback microscopy/online image analysis
|
|
|
|
|
|
With the adaptive feedback microscopy capability the user can combine online image analysis and image acquisition and perform:
|
|
With the adaptive feedback microscopy capability of MyPiC the user can combine online image analysis and image acquisition to perform:
|
|
* Detection of rare events and start a different imaging protocol
|
|
* Detection of rare events and start a different imaging protocol
|
|
* Time-lapse FCS measurements
|
|
* Time-lapse FCS measurements
|
|
* Cell tracking
|
|
* Cell tracking
|
... | @@ -240,7 +242,7 @@ MyPiC communicates with external programs by reading and writing in the Windows |
... | @@ -240,7 +242,7 @@ MyPiC communicates with external programs by reading and writing in the Windows |
|
HKEY_CURRENT_USER\Software\VB and VBA Program Settings\OnlineImageAnalysis\macro
|
|
HKEY_CURRENT_USER\Software\VB and VBA Program Settings\OnlineImageAnalysis\macro
|
|
```
|
|
```
|
|
|
|
|
|
This occurs for each imaging job when **Online img. analysis** in the Method of [Processing and Tracking](#taskopt) is set. After the acquisition of the corresponding job the key [**CodeMic**](#codemic) will be set to `wait`, [**CodeOia**](#codeoia) to `newImage` and [**filePath**](#filepath) to the name of image to analyze. MyPiC will continuously monitor **CodeMic** until the value changes from `wait` to one of the other possible values. If **CodeMic** is `focus`, `trigger1`, `trigger2` coordinates from keys [**X, Y, Z**](#xyz) and [**FCSX, FCSY, FCSZ**](#fcsxyz) are read. Via the registry the user can also dynamically set bleaching or acquisition [ROIs](#rois) for an automated FRAP experiment. A list of online image analysis keys can be obtained by clicking on the **Show OIA Keys** button of the main Macro window.
|
|
This occurs for each imaging job when **Online img. analysis** in the Method of [Processing and Tracking](#taskopt) is set. After the acquisition of the corresponding job the key [**CodeMic**](#codemic) will be set to `wait`, [**CodeOia**](#codeoia) to `newImage` and [**filePath**](#filepath) to the name of image to analyze. MyPiC will continuously monitor **CodeMic** until the value changes from `wait` to one of the other possible values. If **CodeMic** is `focus`, `trigger1`, `trigger2` coordinates from keys [**X, Y, Z**](#xyz) and [**FCSX, FCSY, FCSZ**](#fcsxyz) are read. Via the registry the user can also dynamically set bleaching or acquisition [ROIs](#rois) for an automated FRAP experiment. The full list of online image analysis keys can be obtained by clicking on the **Show OIA Keys** button of the main Macro window. Here we provide a list of the most important commands.
|
|
|
|
|
|
<div align='center'>
|
|
<div align='center'>
|
|
<img src="./images/windowsRegistryCommands.jpg" width = "600px">
|
|
<img src="./images/windowsRegistryCommands.jpg" width = "600px">
|
... | @@ -256,24 +258,24 @@ Contains the commands for the microscope |
... | @@ -256,24 +258,24 @@ Contains the commands for the microscope |
|
`wait` | do not progress in imaging
|
|
`wait` | do not progress in imaging
|
|
`error` | the online image analsys pipeline has encountered an error
|
|
`error` | the online image analsys pipeline has encountered an error
|
|
`nothing` | Nothing has been found
|
|
`nothing` | Nothing has been found
|
|
`trigger1` | Start **Trigger1** imaging using values given in XYZ
|
|
`trigger1` | Start **Trigger1** pipeline using values given in **X**, **Y**, **Z** registry entries
|
|
`trigger2` | Start **Trigger2** imaging using values given in XYZ
|
|
`trigger2` | Start **Trigger2** imaging using values given in **X**, **Y**, **Z** registry entries
|
|
`focus` | Update XYZ coordinate of current imaging position. This can be used to perform object based tracking
|
|
`focus` | Update XYZ coordinate of current imaging position. This can be used to perform object based tracking
|
|
`setFcsPos` | Read position(s) for FCS measurement in case a FCS job has been specified from fcsX, fcsY, fcsZ
|
|
`setFcsPos` | Read position(s) for FCS measurement from **fcsX**, **fcsY**, **fcsZ**. <br/> Start an FCS experiment if next task in pipeline is a FCS job
|
|
`setRoi` | Read ROIs and update ROIs for subsequent task(s) in pipeline
|
|
`setRoi` | Read ROIs and update ROIs for subsequent task(s) in pipeline
|
|
|
|
|
|
<a name="codeoia"></a>
|
|
<a name="codeoia"></a>
|
|
#### Key **CodeOia**
|
|
#### Key **CodeOia**
|
|
Contains commands for the image analysis program.
|
|
Contains the commands for the image analysis program.
|
|
|
|
|
|
Value | Meaning
|
|
Value | Meaning
|
|
------ | ------
|
|
------ | ------
|
|
`nothing` | Nothing to do
|
|
`nothing` | Nothing to do
|
|
`newImage` | A new image with path filePath needs to be analysed
|
|
`newImage` | A new image with path **filePath** needs to be analysed
|
|
|
|
|
|
<a name="filepath"></a>
|
|
<a name="filepath"></a>
|
|
#### Key **filePath**
|
|
#### Key **filePath**
|
|
Contains full path of image that needs to be analysed
|
|
Contains the full path of image that needs to be analysed
|
|
|
|
|
|
Value | Meaning
|
|
Value | Meaning
|
|
------ | ------
|
|
------ | ------
|
... | @@ -282,7 +284,7 @@ Contains full path of image that needs to be analysed |
... | @@ -282,7 +284,7 @@ Contains full path of image that needs to be analysed |
|
|
|
|
|
|
|
|
|
<a name="xyz"></a>
|
|
<a name="xyz"></a>
|
|
#### Keys **XYZ**
|
|
#### Keys **X**, **Y**, **Z**
|
|
Specifies stage positions. Coordinates with respect to upper left corner of the image (in pixels) and first slice (0,0,0). Several points are separated by `;`
|
|
Specifies stage positions. Coordinates with respect to upper left corner of the image (in pixels) and first slice (0,0,0). Several points are separated by `;`
|
|
|
|
|
|
Value | Meaning
|
|
Value | Meaning
|
... | @@ -301,7 +303,7 @@ Specifies FCS scanner positions. Coordinates with respect to upper left corner o |
... | @@ -301,7 +303,7 @@ Specifies FCS scanner positions. Coordinates with respect to upper left corner o |
|
----------- | ------
|
|
----------- | ------
|
|
`X1;X2;X3;...` | X positions with respect to left corner in pixels
|
|
`X1;X2;X3;...` | X positions with respect to left corner in pixels
|
|
`Y1;Y2;Y3;...` | Y positions with respect to upper corner in pixels
|
|
`Y1;Y2;Y3;...` | Y positions with respect to upper corner in pixels
|
|
`Z1;Z2;Z3;...` | Z positions with respect to bottom slice in pixels. If this key is left empty current focus position is used.
|
|
`Z1;Z2;Z3;...` | Z positions with respect to bottom slice in pixels. If this key is left empty current focus position is used
|
|
|
|
|
|
|
|
|
|
<a name="rois"></a>
|
|
<a name="rois"></a>
|
... | @@ -317,19 +319,26 @@ A ROI is defined by 4 different keys. |
... | @@ -317,19 +319,26 @@ A ROI is defined by 4 different keys. |
|
|
|
|
|
For a circle specify 2 points: the center of the circle and one point on the circle.
|
|
For a circle specify 2 points: the center of the circle and one point on the circle.
|
|
For a rectangle specify 2 points: the upper left and lower right corners.
|
|
For a rectangle specify 2 points: the upper left and lower right corners.
|
|
For a polyline to specify at least 3 points.
|
|
For a polyline specify at least 3 points.
|
|
For an ellipse specify 3 points: the center of the ellipse and a point on axis1 and axis2, respectively.
|
|
For an ellipse specify 3 points: the center of the ellipse and a point on axis1 and axis2, respectively.
|
|
|
|
|
|
## <a name= trigger></a> Trigger1 and Trigger2 pipelines
|
|
## <a name= trigger></a> Trigger1 and Trigger2 pipelines
|
|
|
|
|
|
The pipelines **Trigger1/2** are only executed when the command ```trigger1``` or ```trigger2``` is received through the windows registry [**CodeMic**](#codemic). A typical workflow is a multi-position low-resolution imaging using the **Default** pipeline. When objects of interest are detected using online image analysis then the **Trigger1/2** pipeline is started with position(s) specified using the registry keys [XYZ](#xyz). Several imaging/stage positions can be passed to the macro simultaneously, these will be imaged one after the other.
|
|
The pipelines **Trigger1** or **Trigger2** are executed when the command ```trigger1``` or ```trigger2```, respectively, is received through the windows registry [**CodeMic**](#codemic). A typical workflow is a multi-position low-resolution imaging using the **Default** pipeline. When objects of interest are detected using online image analysis then the **Trigger1/2** pipeline is started with position(s) specified using the registry keys [**X, Y, Z**](#xyz). If no stage coordinates are specified imaging is performed at the current stage and focus position of the **Default** pipeline.
|
|
|
|
|
|
|
|
|
|
|
|
Multiple imaging/stage positions can be imaged sequentially without returning to the **Default** pipeline.
|
|
|
|
|
|
|
|
1. Several positions are specified at once in the registry [**X, Y, Z**](#xyz) from the analysis of a single image from the **Default** pipeline.
|
|
|
|
2. The start of the **Trigger1/2** pipeline is delayed. The pipeline starts when a certain number of stage positions are specified within a time interval. In this interval the **Default** pipeline continues.
|
|
|
|
|
|
|
|
|
|
Multiple imaging positions can also be specified sequentially. In this case the **Trigger1/2** pipelines start when stage positions are specified within a time interval or when a maximal number of positions has been reached. If no XYZ coordinates are specified then imaging is performed at the current stage and focus position of the **Default** pipeline. When all repetitions of all positions are finished the imaging continues with the **Default** pipeline. The setup of the pipelines is similar as for the default pipeline. Within a **Trigger1/2** pipeline additional online image analysis steps can be specified.
|
|
When all repetitions of all positions are finished the imaging continues with the **Default** pipeline. The setup of the pipelines is similar as for the default pipeline. Within a **Trigger1/2** pipeline additional online image analysis steps can be specified.
|
|
|
|
|
|
|
|
|
|
Trigger1/2 | Explanations of the buttons
|
|
Trigger1/2 pipelines | Explanations of the buttons
|
|
-----------------|----------------------------
|
|
:------------|:---------------------
|
|
<img src="./images/PipCon_trigger1.PNG" width = "400px"> | 1. Specify order of tasks as for Default pipeline <br/> 2. Specify whether to further process some of the imaging jobs <br/> 3. Specify repetitions <br/> 4. Start pipeline after one position has been specified and **max. waiting (sec)** interval has elapsed<br/> 5. Start pipeline when at least **max # Pts** stage positions have been specified. <br/> 6. If **Keep parent position** is unchecked then the stage position of the **Default** pipeline from which the trigger has been released is deleted. This option is useful to avoid triggering repeated false positives from the same position.
|
|
<img src="./images/PipCon_trigger1.PNG" width = "400px"> | 1. Set thd order of tasks and Z-offset <br/> 2. Specify whether further process task <br/> 3. Set repetitions <br/> 4. Starts pipeline after **max. waiting (sec)** interval has elapsed. Interval is <br/> 5. Start pipeline when at least **max # Pts** stage positions have been specified. <br/> 6. If **Keep parent position** is unchecked then the stage position <br/>of the **Default** pipeline from which the trigger has been released is deleted. <br/> This option is useful to avoid triggering repeated false positives from the same position.
|
|
|
|
|
|
# Example imaging workflows with MyPiC
|
|
# Example imaging workflows with MyPiC
|
|
Workflows without adaptive feedback do not require any further program.
|
|
Workflows without adaptive feedback do not require any further program.
|
... | | ... | |