Skip to content

Commit

Permalink
Rephrase sentence about Z size of FOV/well ROIs
Browse files Browse the repository at this point in the history
  • Loading branch information
tcompa committed Nov 2, 2023
1 parent 43a622e commit 98514aa
Showing 1 changed file with 8 additions and 4 deletions.
12 changes: 8 additions & 4 deletions docs/tables.md
Original file line number Diff line number Diff line change
Expand Up @@ -258,10 +258,10 @@ tasks) always include two specific ROI tables:
* The table named `well_ROI_table`, which covers the NGFF image corresponding to the whole well[^1];
* The table named `FOV_ROI_table`, which lists all original fields of view (FOVs).

Each one of these two tables includes ROIs that are only defined in the XY
plane, and span the whole image size along the Z axis. Note that this differs,
e.g., from ROIs which are the bounding boxes of three-dimensional segmented
objects, and which may cover only a part of the image Z size.
Each one of these two tables includes ROIs that span the whole image size along
the Z axis. Note that this differs, e.g., from ROIs which are the bounding
boxes of three-dimensional segmented objects, and which may cover only a part
of the image Z size.

#### OME-Zarr import

Expand All @@ -277,6 +277,10 @@ ROI tables to the NGFF images:
case the image is a tiled well[^1]), or it may simply be useful for applying
downstream processing to smaller arrays and avoid large memory requirements.

As for the case of `well_ROI_table` and `FOV_ROI_table` described
[above](#ome-zarr-creation), also these two tables include ROIs spanning the
whole image extension along the Z axis.

#### OME-Zarr processing

ROI tables are also used and updated during image processing, e.g as in:
Expand Down

0 comments on commit 98514aa

Please sign in to comment.