Y26-088 - Library Prep from Ultima UG200 (support new tags and add UG200 automated submission)

[sabrine33]

User story

Ultima UG200 for PCR-free libraries uses the same library preparation steps as UG100. We need to introduce new purpose names for UG200 so that the library team can distinguish between plates and tubes for the UG200 and UG100 sequencers, and also ensuring the correct tags are used.

Who are the primary contacts for this story
AbudRahman T

Who is the nominated tester for UAT
AbudRahman T

Consider if these features can be feature-flagged to decouple testing and deployment.

To be considered successful, the solution must allow:

• Provide new plate purposes for UG200 using a UPF2 prefix to distinguish them from UG100 (e.g. UPF2 Cherrypicked) (naming to be confirmed with @KatyTaylor )
• Ensure the UPF2 Lib Plate supports P3 and P4 tags only (confirm the correct tag names from tag story)
• Add an Ultima UG200 pipeline configuration file using the new purpose names, mirroring the behaviour of the existing Ultima pipeline
• The request options for the automated submission: wafer_size =10Tb , ot_recipe= Free
• Update robots.rb to include robot layout verification for the new purposes, mirroring the behaviour of the existing Ultima pipeline.
• Add an Ultima UG200 integration test suite

Integration suite test: https://gitlab.internal.sanger.ac.uk/psd/integration-suite/-/merge_requests/308

** Deployment notes **

Set automated field for submission template "Limber-Htp - Ultima PCR Free - Ultima UG200 sequencing Automated" to true in the database after deployment. This is to hide the automated submission from the UI.

[KatyTaylor]

Are you proposing that UPF Balanced Norm labware always have 2 buttons - to submit for UG100 or to submit for UG200?

Or would it be clever and know which one was used the first time round?

[sabrine33]

Are you proposing that UPF Balanced Norm labware always have 2 buttons - to submit for UG100 or to submit for UG200?

Or would it be clever and know which one was used the first time round?

It should retrieve the sequencing type from the ancestor and propose the same; otherwise, it could become confusing for the end user

[yoldas]

I have added a draft Ultimate UG200 config for pipeline, purposes, and robots. I assumed UPF names will be UPF2 for this pipeline. They should be changed in case a different naming is necessary.

[yoldas]

Notes:

Ultima stories to include in integration testing:

• Y26-086 - As TL (Tris) I would like to have an "Ultima UG200 Sequencing" pipeline page so that I can schedule and monitor batches on this new sequencer #5622
• Y26-085 - As a SSR (Liz C) I would like to be able to create a submission to perform Ultima UG200 sequencing #5621
• Y26-088 - Library Prep from Ultima UG200 (support new tags and add UG200 automated submission) #5624
• Y26-106 - UG200 sample sheet generator #5647
• Y26-084 - Support New tags for Ultima UG200 sequencing submission #5620

Testing with integration suite:
Merge into ultima_ug200_staging branches for SS, Limber, and Integration if necessary.

Sequencescape branches -> ultima_ug200_staging

• Y26-084-ultima-support-new-tags-for-ultima-ug200-sequencing-submission
• y26-106-ug200-sample-sheet-generator
• Y26-085-submission_template-for-ultima-ug200-sequencing

Limber branches:

• y26-088-library-prep-from-ultima-ug200-support-new-tags-and-add-ug200-automated-submission

Integration branches:

• y26-088-library-prep-from-ultima-ug200-support-new-tags-and-add-ug200-automated-submission