DPL-878 Driver file for PBMC plate --> FluidX rack transfer

[KatyTaylor]

User story As a user of the scRNA Core pipeline, I would like Limber to generate a robot driver file for the "LRC PBMC Bank --> FluidX tubes" transfer.

Who are the primary contacts for this story Katy, Abby, Lesley

Who is the nominated tester for UAT Lesley

Acceptance criteria To be considered successful the solution must allow:

• [ ] Hamilton robot driver file can be downloaded, to tell the robot which transfers to make, between the "LRC PBMC Bank" plates and the FluidX tube racks.

Driver file example, showing layout:

N.B. I believe important columns are: Source Plate ID, Source Plate Well, Purpose, Destination Tube Position - if any of the others cause you difficulty, check with Abby or Lesley whether they're needed.

Dependencies This story is blocked by the following dependencies:

• https://github.com/sanger/limber/issues/1314

[KatyTaylor]

Relevant code to use for reference:

• limber > config > exports > exports.yml
• limber > app > views > exports > hamilton_lca_pbmc_bank_to_lca_bank_stock.csv.erb

User journey, from meeting with Abby & Lesley 17/08/23:

1. When users upload tube rack scans, they tell the LIMS which is for sequencing, and which is for contingency - it has to be determined at this stage because the user needs to know how many tubes to put in each (twice the number of tubes in contingency) (covered in DPL-811)
2. Robot driver file includes 1 or 2 source plate barcodes. For the destination racks, there’s a column that says whether the rack is for sequencing or contingency (this story)
3. Robot knows which beds to put the destination racks on because of the “sequencing / contingency” column
4. Robot decides which beds to put the source plates on, and informs the user with a prompt
5. User knows which beds to put the racks on because they can visually distinguish between them (by number of tubes, or colour coding)
6. User scans source plate barcodes and bed barcodes into LIMS - it just checks whether they are of the correct purpose (LRC PBMC Bank) - there’s risk here but less than is currently accepted in 10X aggregation step (10 source plates with same method) (DPL-829)
7. User scans tube rack barcodes and bed barcodes into LIMS - it checks whether the expected purposes (slight complication here as purposes are on the tubes, not the racks) are in the expected beds. (DPL-829)

[KatyTaylor]

Screenshots showing the an example of prompts that the robot gives the user, telling them which plates to place on which beds:

[KatyTaylor]

Updated this story to remove references to multiple source plates, as there will now only ever be one source plate.

[ac38]

Will confirm regarding the driver file columns required once the banking protocol is modified but I suspect the shared layout will be okay.