... | ... | @@ -26,8 +26,10 @@ For high-throughput microscopy data, the table should have separate columns for |
|
|
| 3| 108 | 119 | 1 | 10 | experiment\_2021-08-03/replicate\_01/cells-P01-A08.tiff | 93 | 549 | 0.70456 | Plate01 | A08 |
|
|
|
|
|
|
### **Images**
|
|
|
|
|
|
Each image file must contain an image of at most 3 dimensions with the third dimension representing either depth (z coordinate) or time. Images are expected to be organised under one common root directory. For example, if the images are organized like this:
|
|
|
##### Format
|
|
|
The IDE can read all image formats supported by BioFormats but has so far mostly been tested with TIFF. However, its image viewer can currently display images of at most 3 dimensions with the third dimension representing either depth (z coordinate) or time.
|
|
|
##### File system organisation
|
|
|
When the IDE runs on a user’s computer (or a server), the images can be on any file system the user has access to from that computer. Images are expected to be organised under one common root directory. This directory is a top-level directory under which all images can be found. For example, if the images are organized like this:
|
|
|
|
|
|
▽ screen_images
|
|
|
▽ plate1_replicate1
|
... | ... | @@ -39,7 +41,5 @@ Each image file must contain an image of at most 3 dimensions with the third dim |
|
|
|
|
|
then the image root directory is screen_images. The organization of images under the root directory can follow any arbitrary structure as long as the data table associates each image file with the correct path (see Data points - Content above).
|
|
|
|
|
|
The IDE can in principle read all image formats supported by BioFormats but has so far mostly been tested with TIFF.
|
|
|
|
|
|
The image root directory must be accessible from the computer running the app.
|
|
|
Alternatively, the images can be put in an S3-compatible object store for remote access in which case the bucket represent the root directory.
|
|
|
|