Description
- Automated robots (e.g., liquid handlers, screening instruments) generate sequence files that Katalyst should use to map wells, samples, and KAT IDs.
- Katalyst fails to recognize or process these sequence files:
- No experiments are created or updated.
- No analytical data is attached.
- Inspection shows that the sequence file format or naming convention has changed or does not match Katalyst expectations.
Solution
- Obtain a sample of the current robot sequence file and compare it to Katalyst’s expected format:
- Column names (sample ID, well, plate, file name, etc.).
- Position of KAT IDs or other identifiers.
- File extension and encoding.
- Update one of the following (depending on ownership and flexibility):
- Robot configuration:
- Adjust exported sequence file structure to match the Katalyst template.
- Include KAT IDs and plate/well information in the expected columns.
- Katalyst sequence‑file parser:
- Update mapping rules or patterns so Katalyst can correctly interpret the robot’s current output format.
- Robot configuration:
- After configuration:
- Test with a small sequence, verifying that Katalyst:
- Creates or updates the correct experiment.
- Correctly maps wells and attaches any analytical data that follows.
- Test with a small sequence, verifying that Katalyst:
- Document the agreed‑upon naming and sequence file format so both robot administrators and Katalyst admins know what is required.
Comments
0 comments
Article is closed for comments.