This article describes what Sample Tracking is and the how to use its commands in a FluentControl™ script to generate a Sample Tracking report.
Sample Tracking is a software add-on that can be installed in addition to FluentControl and allows to record sample identities, track samples throughout the pipetting process in a SQL database and generate report files. Using Sample Tracking requires a Fluent GX license when connected to a real instrument.
Sample Tracking Embedded vs. Sample Tracking Stand Alone
At Sample Tracking installation, there will be a choice between two different options.
Sample Tracking Embedded:
The SQL database does not store pipetting data persistent across runs. Meaning a Sample Tracking report can be generated during a run and contains the results of that specific run. At the start of a next run, the SQL database content is cleared, hence pipetting data is not tracked cumulative to the data from previous runs.
Sample Tracking Stand Alone:
The SQL database stores pipetting data persistent across multiple runs. Meaning if a sample is processed in a run, then the sample data is permanently stored in the SQL database and if re-using that sample in a future run, the SQL database can track all actions for that sample cumulative across multiple runs. Please note, this implies that one cannot re-use the same barcode value for a different sample in a future run, but always requires a unique barcode value for a new sample.
After installation of Sample Tracking, you will also need to enable the I/O state checkbox of the Sample Tracking Driver at Configure System - Drivers.
How to use Sample Tracking commands in a FluentControl script
To use Sample Tracking in a script, the sequence of events must be as following:
- Assign labware barcodes to Source and Destination Labware
- Register Source Labware
- Process Samples
- Generate Report for Destination Labware
If Samples are located inside a tube runner, the tube runner itself must also have a barcode and at Register Labware, select the label of the entire tube runner, not individual tubes.
In case your labware doesn’t have real barcodes to scan, it is possible to assign labware barcodes programmatically, for example use the script command Import Sample IDs from file, use the SetAttribute() function or by right-click the labware on the worktable window and write a barcode to the labware manually.
All source labware to register and all destination labware for which a report shall be generated must have a labware barcode. Assign the barcodes before the Register Labware command. Having labware barcodes is mandatory, having well barcodes is optional.
At Register Labware, select either option ‘Register Labware’ or select option ‘Register Labware with Platemap’ in case you have a platemap file with additional sample information available.
After Sample Tracking Register Labware, just program your script normally. Sample Tracking automatically listens to pipetting messages at runtime, processes the information and writes data such as Sample IDs, Volume, Concentration and Pipetting Errors to the SQL database.
It is possible to access some of the data stored in the SQL database with Sample Tracking script commands Get Value and Set Values. For example, you could use Get Value to read out a volume value for a specific sample and store that value in a FluentControl variable.
For Tecan Readers that can perform a Magellan measurement: Sample Tracking can automatically push Sample IDs and Pipetting Status into Magellan software. To enable this functionality, navigate to FluentControl Menu – Settings - Configure System – Magellan Driver Settings – and enable the Sample Tracking checkbox.
Generate Report always creates a PDF Report file with the selected plate report. Optional you can also select ‘Export to CSV’, which creates a *.csv file for the same selected report type. The option ‘Print Report’ sends out a print job, hence it is usually not needed unless you are looking for a physical print out on paper.
At Generate Report, a dropdown list provides a selection of various Sample Tracking report types. If you don’t know yet which report type to use, the Plate Report Extended or the Platemap Report is a good choice to start with.
Assuming the default file paths are configured, Sample Tracking report are stored here:
PDF Report file: C:\ProgramData\Tecan\Sample Tracking\Reports
CSV report file (optional): C:\ProgramData\Tecan\VisionX\Output
The SampleTracking Report will contain data for the selected destination labware such as Position, Sample ID, Volume, Concentration and Error list. At the bottom of the report you can find legend for the error numbers in this specific report.
The *.csv report file of a Platemap report file has the correct format so it can also be used to Register a labware with a Platemap file in a future run if you continue to process the same plate in a future run and have Sample Tracking Embedded.
Further Help
For further help, please refer to our Helpdesk.
Link to Tecan Product Page:
401815-029