Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion examples/calibration_2d/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,7 @@ points, and generate a mapping from desired coordinates to calibrated coordinate
|:--------------------------------:|:-----------------------------------:|:-------------------------------------:|
| ![basic bilinear](img/basic.png) | ![biquadratic](img/biquadratic.png) | ![real example](img/real_example.png) |

This calibration algorithm requires as input both the coordinates of the **expected** positions (blue dots), and the coordinates of the **actual** positions (red dots). The actual positions can be acquired by moving the gantry until the end effector is directly on the fiducial mark or sample, and then reading off the positions from software such as [Zaber Launcher](https://software.zaber.com/zaber-launcher/download).
This calibration algorithm requires as input both the coordinates of the **expected** positions (blue dots), and the coordinates of the **actual** positions (red dots). The actual positions can be acquired by moving the gantry until the end effector is directly on the fiducial mark or sample, and then reading off the positions from software such as [Zaber Launcher](https://zaber.com/zaber-launcher#download).

- On the left is the most basic bilinear interpolation, requiring four corner point pairs - expected coordinates $(x_p, y_p)$ and actual coordinates $(x_p', y_p')$. The calibration algorithm uses these point pairs to generate the coefficients for a mapping function that the user can call to transform desired coordinates to calibrated coordinates from any location.

Expand Down
2 changes: 1 addition & 1 deletion examples/microplate_scanning_basic/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -32,7 +32,7 @@ For more information on how to identify the serial port,
see [Find the right serial port name](https://software.zaber.com/motion-library/docs/guides/communication/find_right_port).
- `DEVICE_NUMBER`: the order that the controller or stage is plugged into the device chain.
For example, if it is the first and only device in the chain then use the number 1.
Check the device numbering by opening [Zaber Launcher](https://software.zaber.com/zaber-launcher/download) to view the devices connected to a serial port.
Check the device numbering by opening [Zaber Launcher](https://zaber.com/zaber-launcher#download) to view the devices connected to a serial port.
- `ROW_HOME_OFFSET` and `COLUMN_HOME_OFFSET`: the offset in millimeters
from the home or zero position of both axes to the edge of the well plate.
- `PLATE_TYPE`: number of wells in the standard ANSI microwell plate.
Expand Down
4 changes: 2 additions & 2 deletions examples/microscope_tiling_basler_camera/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -26,7 +26,7 @@ Edit the following constants in the script to fit your setup before running the

- `SERIAL_PORT`: the serial port that your microscope is connected to.
For more information on how to identify the serial port, see [Find the right serial port name](https://software.zaber.com/motion-library/docs/guides/communication/find_right_port).
- `TOP_LEFT`: top left point of sample region (can be copied directly from microscope app in [Zaber Launcher](https://software.zaber.com/zaber-launcher/download))
- `TOP_LEFT`: top left point of sample region (can be copied directly from microscope app in [Zaber Launcher](https://zaber.com/zaber-launcher#download))
- `BOTTOM_RIGHT`: bottom right point of sample region (also can be copied)
- `OVERLAP_H`: desired decimal percentage of horizontal overlap between neighbouring tiles
- `OVERLAP_V`: desired decimal percentage of vertical overlap between neighbouring tiles
Expand All @@ -48,7 +48,7 @@ This example doesn't attempt to perform any sort of automated pixel calibration,

### Focus

This example doesn't attempt to adjust focus while tiling. If your sample's height is uniform, then focus can be set manually from the basic controls or microscope app available in [Zaber Launcher](https://software.zaber.com/zaber-launcher/download).
This example doesn't attempt to adjust focus while tiling. If your sample's height is uniform, then focus can be set manually from the basic controls or microscope app available in [Zaber Launcher](https://zaber.com/zaber-launcher#download).

If your sample's height is non-uniform, then it would be worth looking at the [focus map](../microscope_autofocus/) and [autofocus examples](../microscope_autofocus/) in this repository. Logic for focussing the objective could be added below the call to `AxisGroup.move_absolute` in the `capture_images` function in main:

Expand Down
2 changes: 1 addition & 1 deletion examples/motion_input_shaping/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -164,4 +164,4 @@ Class Methods:

## Troubleshooting Tips

- If you encounter an error when running one of the example scripts, check the Serial Port number (ex. COM5) using [Zaber Launcher](https://software.zaber.com/zaber-launcher/download).
- If you encounter an error when running one of the example scripts, check the Serial Port number (ex. COM5) using [Zaber Launcher](https://zaber.com/zaber-launcher#download).
4 changes: 2 additions & 2 deletions examples/motion_pvt_sequence_generation/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -5,7 +5,7 @@
This repository contains code to complement our article [Motion Planning with Position-Velocity-Time](https://www.zaber.com/articles/motion-planning-with-position-velocity-time). The cubic polynomial PVT algorithm
described in the article is implemented in Python, along with helper functions to automatically
generate missing parameters, plot the generated path and trajectory, and save the results
to a CSV file that is compatible with [Zaber Launcher](https://software.zaber.com/zaber-launcher/download)'s PVT Viewer App.
to a CSV file that is compatible with [Zaber Launcher](https://zaber.com/zaber-launcher#download)'s PVT Viewer App.

## Hardware Requirements

Expand All @@ -15,7 +15,7 @@ However, the underlying math and generated trajectories could be utilized on alm
Notes:

- This code requires Zaber devices with firmware version 7.33 or higher.
- This code can be used to generate PVT sequence CSV files compatible with [Zaber Launcher](https://software.zaber.com/zaber-launcher/download)'s PVT Viewer App.
- This code can be used to generate PVT sequence CSV files compatible with [Zaber Launcher](https://zaber.com/zaber-launcher#download)'s PVT Viewer App.

## Dependencies

Expand Down