In a previous article, we introduced the different types of results data๐ the Delvotestยฎ Accelerator Smart (DAS) generates during and after testing, and how to access them. One of these is an easy-to-read .pdf (Portable Document Format) file report containing the final plate table's results (including Z-values) and high-level, critical metadata (e.g., operator, temperature, etc.). In this article, we explore this report file in depth.
Access and Structure
To access one of these .pdf reports, simply follow the steps outlined in Introducing Results๐. Once you have the file, you should see something like this:
If you'd like to get this example file, here's a download link๐. // add link
Similar to the Incubation tab๐, the report is divided in two main sections: at the top, a Summary Data Section textually outlining critical, overarching information about the test; and, at the bottom, a final, data-enriched Plate Table Section reflecting the Incubation tab's Plate table subsection๐.
Summary Data Section
This section typically contains fourteen report fields. Here's what each means, and, when relevant, where you can find more information about them.
Measurement Name
The unique identifier which follows its respective Test subfolder's name and its naming convention๐.
Device Name
The DAS's which executed the test's name, which you can view and edit๐in the Set up tab.
Operator
The name of the operator selected when preparing the test๐ in the Incubation tab's Operator dropdown field๐.
Your list of operators is also available for you to view and edit๐in the Set up tab.
Date
The date when the test started, defined according to this DAS's customisable localisation settings๐. It is formatted with hyphen ('-') delimiters between its year (four digits), month (two digits), and day (two digits) values.
โด YYYY-MM-DD
e.g., for 5 December 2024, the result should be 2024-12-05.
Product
The test line of your Delvotestยฎ plate, as automatically identified by the DAS when preparing the test๐ in the Incubation tab's Product name field๐.
Start time
The time the test started, defined according to this DAS's customisable localisation settings๐. It's formatted using a 24-hour clock, with colon (':') delimiters between its hour (two digits), minute (two digits), and seconds (two digits) values.
โด HH:MM:SS
e.g., for 11:55:22 (AM), the result should be 11:55:22.
Batch Number
The data identified either during automatic barcode scanning or manual barcode input๐ when preparing the test in the Incubation tab's Batch number field๐.
Plate Number
The data identified either during automatic barcode scanning or manual barcode input๐ when preparing the test in the Incubation tab's Plate number field๐.
Method
The data selected when preparing the test in the Incubation tab's Inhibitor method dropdown field๐.
Incubation time
The total time taken for the plate's incubationโwhich, based on the DAS's Working Principle๐ is incidentally also the plate's Control Time๐. It's formatted with colon (':') delimiters between its hour (two digits), minute (two digits), and seconds (two digits) values.
โด HH:MM:SS
e.g., for a test that took 3 hours, 19 minutes and 4 seconds, the result should be 03:19:04.
Comments
The data entered when preparing the test๐ in the Incubation tab's Comments field๐.
Comments After
// ask @Atha โ where/when are they able to add comments afterwards? //
Warnings
Whenever the DAS detects abnormal performance, like in this example, it will textually describe the issue(s) in this section of the report. There are a series of potential outcomes, which we explore as a troubleshooting centre in Introducing Results Warnings๐.
Temperature [mean / min / max]
Every minute during testing, the DAS captures temperature data, where, in this field of the report, the overall median, minimum and maximum values are summarised.
Plate Table Section
This section reflects the Incubation tab's Plate table subsection๐. Every plate-well contains the following data:
Colour coding
Every plate-well's NEGATIVE and POSITIVE results are, respectively, colour-coded in green and red. In circumstances where no result is established for a plate-well โ e.g., due to an error during testing, or when only a/some plate-strip(s) are tested โ, this will be colour-coded in grey.
Nref and Pref
For plate-wells where either a NEGATIVE or POSITIVE reference control was denoted when preparing the test๐ in the Incubation tab's Negative and Positive checkboxes๐, this information will be reflected here in the report. // need to check if cell-level comments are also displayed ... should've tested, sorry! //
๐กBy the way, did you know that even if you indicate a sample is a reference control, the DAS will still test it without presuming its performance prior? This is part of the DAS's way of ensuring continuous verification for your reference controls as part of its Working Principle๐.
Z-values
Based on the DAS's Working Principle๐, every plate-well cell also reports its final Z-scale value as determined at Control Time๐, within one decimal point. // add link
File Naming Convention
Particularly helpful for automating reporting functions when integrating DAS data flows with your systems e.g., Laboratory Information Management System (LIMS), this report file follows a standard naming convention:
[Device Name]_[Batch Number]_[Plate Number]_[Date]-[Time]_[???]_Results.pdf
[Device Name]
The DAS's which executed the test's name, a parameter you can view and edit๐in the Set up tab.
_
Single underscore ('_') delimiter.
[Batch Number]
The data identified either during automatic barcode scanning or manual barcode input๐ when preparing the test in the Incubation tab's Batch number field๐.
_
Single underscore ('_') delimiter.
[Plate Number]
The data identified either during automatic barcode scanning or manual barcode input๐ when preparing the test in the Incubation tab's Plate number field๐.
_
Single underscore ('_') delimiter.
[Date]
The date when the test started, defined according to this DAS's customisable localisation settings๐. It's formatted without delimiters between its year (four digits), month (two digits), and day (two digits) values.
โด YYYYMMDD
e.g., for 5 December 2024, the result should be 20241205.
-
Single hyphen ('-) delimiter.
[Time]
The time the test started, defined according to this DAS's customisable localisation settings๐. It's formatted using a 24-hour clock, without delimiters between its hour (two digits), minute (two digits), and seconds (two digits) values.
โด HHMMSS
e.g., for 11:55:22 (AM), the result should be 115522.
_
Single underscore ('_') delimiter.
DA3
Simply the text 'DA3', not dependently determined on any external function/logic other than the fact that this is a report file.
_
Single underscore ('_') delimiter.
Results
Simply the text 'Results', not dependently determined on any external function/logic other than the fact that this is a report file.
.pdf
The file's type extension (i.e., Portable Document Format).
So, when considering this example's file (download link๐) // add link // , you should see the following:
DAS_1112_24K08B30_360_20241205-115522_DA3_Results.pdf
This means that this was a tested conducted by a device named DAS_1112 (i.e., [Device Name] = DAS_1112), with a Delvotestยฎ plate from batch 24K08B30 (i.e., [Batch Number] = 24K08B30), of which this was the 360แตสฐ plate from that batch (i.e., [Plate Number] = 360), where the test began on 5 December 2024 (i.e., [Date] = 20241205), at 11:55:22 AM (i.e., [Time] = 115522) // complete this, include .pdf at the end.
Next Steps
If this is the first type of results data๐ you've explored in depth, a great next step is to have a look at a more detailed results data type the DAS also generates for every testโwhich, incidentally, is the critical file needed to build results backwards data integration automation with your LIMS.
โญ๏ธ Next series: Results Data // .csv๐
๐ฌ Got any questions? Need help? Get in touch support@delvotest.com