|
|
|||
|
|
||
|
|||
Question: Answer (by Christoph Krüll, Ph.D, Beckman Coulter): Setup Create any of the SAMI methods shown in Fig.1; one assay plate is send to the same reader several times. It does not make any difference if the plate stays in the reader (1a, 1b) or is moved away for a short incubation or any other further processing (1c). We will use a 'Property' to discriminate the assay plates processed in one SAMI method. Properties such as 'Name' and 'Barcode' describe the plate and can be logged with the reader data. Schedule the method and run it once. This is necessary to be able to configure the data logger.
Data Logger Within the data logger, we now want to configure a separate report for every plate. We will actually define one report per 'family'. A family in SAMI is defined as all transports (plates, tip boxes etc.) needed to run the SAMI method one time. In our example, we use one assay plate per family. Multiple assay plates per family require a more complex log file sorting (see Application Note 'SAMI Log File Sorting'). Open the 'Report configuration' window as shown in Fig.2.
Proceed with the report configuration as shown in Fig. 3. The Family Property is included in some specific SILAS messages and thus shows up here. We simply use it as a discriminator and want to include it in our log file.
Set the Family Property to 'Must be equal to: 1' as shown in Fig.4. With this setting, only data from plates in family 1 will be logged in this particular report. If the same plate goes through several reads, all reader data for this one plate will be included in the log file. Next, we want to save this report under a distinctive name, e.g. 'Fluostar01.log' as shown in Fig.5.
For plates of families 2, 3, 4 etc., we need to create several more reports now. In the 'report configuration' window (Fig.3, 6) select the 'Fluostar' report in the 'Reports' field on the left hand side. Then click 'Export Report' to save this report as a new template, for instance as 'Fluostar_FamilyCount.LRP'. Import this report now by clicking on the 'Import Report' button and selecting the 'Fluostar_FamilyCount.LRP'. Two lines 'Fluostar' will now show in the 'Reports' field. Select the bottom one, choose the 'Filter' tab and go through the steps described in Fig.4 and Fig.5 again. Set the 'Item Properties' to 'Must be equal to: 2' (Fig.4) and change the filename to 'Fluostar02.log' (Fig.5). For more than two families, import the template repeatedly and go through the last two steps for every log file. Finally, confirm the configuration with 'OK'. It is important to close every window with 'OK' now. All configurations will be stored within the method file during scheduling. Now run the method once and you will find the log files 'Fluostar01', 'Fluostar02' etc. in your default log file directory. Note: There is an upper limit of 50-70 individual report files that can be stored within the configuration. The limit depends on the reader used. For a higher number of reports, the definition needs to be done just before scheduling the method. Keep the current method open to ensure proper function of the additional reports. Note for experienced SAMI users: The 'Family' property is only one counter that can be used to generate separate log files. Other examples are 'Home Location Index' or even new properties specifically generated for sorting (see application note 'SAMI log file sorting). * All trademarks are the property of their respective owners. Where applicable, the PCR process is covered by patents owned by Roche Molecular Systems, Inc., and F. Hoffmann-LaRoche, Ltd. For comments or questions about T3 Update, please contact the T3 Editor.
|
