TileManager and CycleManager
Both components drive multi-position acquisitions, from different directions.
hSI.hTileManager works in space - a set of tiles laid out over the sample - while
hSI.hCycleManager works in configurations - a list of iterations, each with its own CFG
file, delay and stage position.
hSI.hTileManager
scanimage.components.TileManager. Tiles are
scanimage.components.tiles.tile objects; each carries its corner points, its resolution,
a sample point and, once acquired, its hRoiData. Tiles live in
sample coordinates, so they follow the stage.
Property |
Description |
|---|---|
|
Read-only array of the tiles that will be scanned. |
|
Order in which the scan tiles are visited. |
|
Function that produces that order. Defaults to
|
|
Frames acquired at each tile. |
|
Traverse tiles at different z with the FastZ actuator rather than the stage. |
|
Seconds to wait after a stage move before acquiring. Default 0.1. |
|
The ROI group generated for each tile. |
|
Live counter of scanned tiles. |
|
Status flags. |
Method |
Description |
|---|---|
|
Add tiles to the scan set. |
|
Remove tiles. |
|
Build tiles from a parameter struct. |
|
Prepare for a tiled acquisition. |
|
Move to and acquire the next tile. Returns true when the set is finished. |
|
Stop a tiled acquisition. |
|
The visiting order produced by |
|
Nearest tile to the current stage position. |
|
Overlap between two tiles, as a percentage. |
|
The same lateral tile at every configured z. |
|
Build the ROI groups for the current tiles. |
|
Persist the tile set. |
|
Tile metadata for the acquisition. |
hSI.hTileManager.scanFramesPerTile = 10;
hSI.hTileManager.scanStageSettleTime = 0.2;
hSI.hTileManager.initTileScanning();
See also
Tile Manager, Tile Objects, Tile Generators, Tile Sorting Functions, Tile Scanning and Stage Scanning.
hSI.hCycleManager
scanimage.components.CycleManager. A cycle is an ordered list of iterations; each
iteration is a scanimage.components.cycles.CycleData object with
cfgName- the CFG file to load for that iteration,motorPosition- the stage position to move to,iterDelay- seconds to wait,active- whether the iteration runs.
The list is held in a scanimage.components.cycles.CycleDataGroup.
Property |
Description |
|---|---|
|
The |
|
Number of times the cycle repeats. |
|
Advance the cycle per acquisition within a LOOP, rather than per acquisition mode. |
|
True when |
|
Function run at the start of a cycle. |
|
Functions run before, during and after the move to the next position. Overriding
|
Method |
Description |
|---|---|
|
Start the cycle. |
|
Stop it. |
|
Append an iteration with the current settings. |
|
Append iterations for a list of positions. |
|
Remove iterations. |
|
Reset or refresh the cycle definition. |
|
Reset progress counters. |
|
Save the cycle to file. |
|
The default move implementation, useful as a starting point for a custom |
hSI.hCycleManager.appendNewIteration();
hSI.hCycleManager.cycleDataGroup.getIterByIdx(1).iterDelay = 5;
hSI.hCycleManager.totalCycles = 3;
hSI.startCycle();
The cycleDataGroupDone user function event fires when the last
iteration of a cycle data group completes.