Examples

Examples

A bit lost with PlateEditor? To get you started, you can follow the proposed examples, using the files available in the bundled application or dowloadable throughout this tutorial.

Simple example

Download the files here: Simple.zip
Archive contents:
- Layout.save: layout file for this example that can be loaded in PlateEditor.
- Results_example1.txt: text file containing the data for this plate. The file can be mapped with a Well ID ("Well"). The "Cell count" column should be imported as a numeric type.

Available with this example:
- Loading a layout file and playing around with the layout and Sample-type areas.
- Attaching a single-plate result file, parsing and mapping, validation and heatmap visualization.
- Using the "Column Analysis" feature to see data aggregation.

How to:
When importing the result file, all parsing options can be left to their default values. Map the "Cell count" column for import, as in the picture below.

Screening example

Download the files here: Screening.zip
Archive contents:
- Layout.save: layout file for this example that can be loaded in PlateEditor.
- Definition.csv: csv file containing the definition for the range "cpds" defined in the layout.
- Results.xlsx: excel file containing the results for all plates. The file can be mapped with a Well ID ("Well") and a Plate ID ("Plate ID"). The "RFU" column should be imported as a numeric type.

Available with this example:
- Loading a layout file and playing around with the layout and Control-type, Range-type areas.
- Attaching a multi-plate definition file, parsing and mapping, plate visualization with Plate view.
- Attaching a multi-plate result file, parsing and mapping, validation and heatmap visualization, plate browsing.
- Min & Max options for multiple plates.
- Pairing result and definition plates using the auto-pairing functions.
- Using the "Controls" tool to see the calculation of controls for multiple plates
- Using the "Hits" tool to select values above a given threshold

How to:
When importing the definition file, all parsing options can be left to their default values. Map the "CPD ID" column to the Definition role.
When importing the result file, all parsing options can be left to their default values. Map the "RFU" column for import.
Pair the result and definition plates using the auto-pairing function (By plate name). There should be 162 matches.
Change the Min & Max option to "Plate" and browse the result plates to identify hits. This can be done automatically with the "Hits" tool, after selecting the desired threshold.
Open the "Controls" tool and run the "Compute All" function to start the plate analysis process (see below).

Screening2 example

Download the files here: Screening2.zip
Archive contents:
- Layout.save: layout file for this example that can be loaded in PlateEditor.
- Definition.txt: text file containing the definition for the range "compounds" defined in the layout.
- Results.txt: text file containing the results for all plates. The file can be mapped with a Well ID ("Well") and a Plate ID ("Plate ID"). The "RFU" column should be imported as a numeric type.

Available with this example:
- Loading a layout file and playing around with the layout and Control-type, Range-type areas.
- Attaching a multi-plate definition file, parsing and mapping, plate visualization with Plate view.
- Attaching a multi-plate result file, parsing and mapping, validation and heatmap visualization, plate browsing.
- Min & Max options for multiple plates.
- Pairing result and definition plates using the auto-pairing functions.
- Using the "Controls" tool to see the calculation of controls for multiple plates
- Using the "Hits" tool to select values above a given threshold

How to:
When importing the definition file, all parsing options can be left to their default values. Map the "Cpd ID" column to the Definition role.
When importing the result file, all parsing options can be left to their default values. Map the "RFU" column for import.
Pair the result and definition plates using the auto-pairing function (By plate name). There should be 10 matches.
Browse the result plates to identify hits. This can be done automatically with the "Hits" tool, after selecting the desired threshold.
Open the "Controls" tool and run the "Compute All" function to start the plate analysis process (see example above).

DRC example

Download the files here: DRC.zip
Archive contents:
- Layout.save: layout file for this example that can be loaded in PlateEditor.
- Results.csv: csv file containing the data for this plate. The file can be mapped with a Well ID ("Well"). The "Data" column should be imported as a numeric type.

Available with this example:
- Loading a layout file and playing around with the layout and Range-type areas.
- Attaching a single-plate result file, parsing and mapping, validation and heatmap visualization.
- Using the "Grouped Analysis" tool to see grouped aggregation for dose-response.

How to:
When importing the result file, all parsing options can be left to their default values. Map the "Data" column for import.
Open the "Grouped Analysis" tool and select the concentration as rows, the Range as columns (see below).

DRC2 example

Download the files here: DRC2.zip
Archive contents:
- Layout.save: layout file for this example that can be loaded in PlateEditor.
- Definition.txt: text file containing the definition for the range "compounds" defined in the layout.
- Results.xlsx: excel file containing the data for this plate. The file can be mapped with a Well ID ("Well"). The "Data" column should be imported as a numeric type.

Available with this example:
- Loading a layout file and playing around with the layout and Range-type areas.
- Attaching a single-plate definition file, parsing and mapping, plate visualization with Plate view.
- Attaching a single-plate result file, parsing and mapping, validation and heatmap visualization.
- Using the "Grouped Analysis" tool to see grouped aggregation for dose-response.

How to:
When importing the definition file, all parsing options can be left to their default values. Map the "Name" column to the Definition role.
When importing the result file, all parsing options can be left to their default values. Map the "Data" column for import.
Open the "Grouped Analysis" tool and select the concentration as rows, the Range as columns (see example above).
Note the automatic resolution of names for each range items

DRC3 example

Download the files here: DRC3.zip
Archive contents:
- Layout.save: layout file for this example that can be loaded in PlateEditor.
- Definition.txt: text file containing the definition for the range "compounds" defined in the layout.
- Results.xlsx: excel file containing the data for all plates. The file can be mapped with a Well ID ("Well") and a Plate ID ("Plate"). The "Data" column should be imported as a numeric type.

Available with this example:
- Loading a layout file and playing around with the layout and Range-type areas.
- Attaching a multi-plate definition file, parsing and mapping, plate visualization with Plate view.
- Attaching a multi-plate result file, parsing and mapping, validation and heatmap visualization.
- Min & Max options for multiple plates.
- Pairing result and definition plates using the auto-pairing functions.
- Using the "Grouped Analysis" tool to see grouped aggregation for dose-response, in a multi-plate setup.

How to:
When importing the definition file, all parsing options can be left to their default values. Map the "Name" column to the Definition role.
When importing the result file, all parsing options can be left to their default values. Map the "Data" column for import.
Pair the result and definition plates using the auto-pairing function (By plate index). There should be 3 matches.
Open the "Grouped Analysis" tool and select the concentration as rows, the Range as columns (see example above).
Browse the result plates. Note the automatic resolution of names for each range items, at the plate level.

Infection example

Download the files here: Infection.zip
Archive contents:
- Layout.save: layout file for this example that can be loaded in PlateEditor.
- Results.xlsx: excel file containing the data for this plate. The file can be mapped with a Well ID ("Well"). The "Data" column should be imported as a numeric type.

Available with this example:
- Loading a layout file and playing around with the layout and Sample-type areas.
- Defining combination layouts using multiple layers.
- Attaching a single-plate result file, parsing and mapping, validation and heatmap visualization.
- Using the "Column Analysis" tool to see data aggregation for combinations.

How to:
When importing the result file, all parsing options can be left to their default values. Map the "Data" column for import.
Open the "Column Analysis" tool to see the data aggregation accross all the computed combinations.

Grouping example

Download the files here: Grouping.zip
Archive contents:
- Layout_Groups.save: layout file for this example that can be loaded in PlateEditor.
- Definition_Groups.txt: text file containing the definition for 2 plates, for the range "Range" defined in the layout. The definition should be mapped to the "Definition" column, only column present in the file.
- Results_Groups.xlsx: excel file containing the data for this plate. The file can be mapped with a Well ID ("Well"). The "Data" column should be imported as a numeric type.

Available with this example:
- Loading a layout file and playing around with the layout and Range-type areas.
- Defining combination layouts using multiple layers.
- Attaching a single-plate result file, parsing and mapping, validation and heatmap visualization.
- Using the "Grouped Analysis" tool to see data aggregation for combinations.

How to:
When importing the result file, all parsing options can be left to their default values. Map the "Data" column for import.
Open the "Grouped Analysis" tool to see the how the data aggregates when setting up different combinations and levels of aggregation.