In burgerga/toxplate: Create a Plate Layout File to Map Locations to Wells

knitr::opts_chunk$set(
  collapse = TRUE,
  comment = "#>",
  fig.path = ".README/README-",
  fig.width = 3,
  fig.height = 1.5
)
library('toxplate')
library('tibble')
library('magrittr')

toxplate

Creates a plate layout for your experiment based on the top-left and the bottom-right well and a possible zigzag pattern. These layout files can be used to match the location (aka 'imageNr') in the image filename to the correct well in the plate. The resulting plate layout data can be exported and used in CellProfiler instead of putting all images in separate well folders.

Usage

The toxplate package provides two functions: getLayoutPicture and getLayoutMappingDF. getLayoutPicture generates a picture of your layout, which you can use to store with your experiment and to inspect your layout before generating a layout mapping with getLayoutMappingDF. Both functions take the same arguments: the top-left and bottom-right well, the zigzag direction, and the starting number. For more details about the arguments use ?getLayoutPicture

getLayoutPicture

Example usage for a typical 24-well plate with 1 location per well, and zigzag over columns:

getLayoutPicture("A01", "D06", "columns")

The same plate, but with zigzag over rows:

getLayoutPicture("A01", "D06", "rows")

and without zigzag (rows):

getLayoutPicture("A01", "D06", "notZigzagRowWise")

To use multiple positions per well just add the maximum position to the bottom-right well:

getLayoutPicture("A01", "D06_02", "columns")

One more example of a partially filled bigger plate

getLayoutPicture("C05", "K12_02", "rows")

getLayoutMappingDF

When the layout is what you expect you can generate a mapping with getLayoutMappingDF (I used as_tibble to prevent long output):

getLayoutMappingDF("A01", "D06_02", "columns") %>% as_tibble

Installation

The toxplate package is not on CRAN (yet). To install it you need the devtools package:

devtools::install_github('burgerga/toxplate')

burgerga/toxplate documentation built on May 13, 2019, 8:47 a.m.