Skip to content

Y26-112 - Generate Summary of Final Pooling Strategy for scRNA Pipeline #2771

@Stan1520

Description

@Stan1520

Context
The scRNA pipeline currently lacks an automated way to generate a summary of the final pooling strategy. This requires manual collation of sample performance, failures, and pooling information, creating back-and-forth with Ops and increasing the risk of incorrect reporting. A downloadable summary from Limber (preferred) would provide a consistent and automated output.

User story
As a user, I want to generate and download a summary of the final pooling strategy from the LRC PBMC Pools plate page in Limber, So that I can view sample performance, failures, and pooling outcomes without manually collating data.

Who are the primary contacts for this story
Abby C

Who is the nominated tester for UAT
Abby C

Acceptance criteria
To be considered successful the solution must allow:

  • A Download Summary File action is available on the LRC PBMC Pools plate page for the scRNA Core pipeline.
  • The generated file follows the defined template structure, including matching column headers and column order, and includes blank rows for failed samples not present in the pools plate.
  • The file includes parent plate reference (LRC PBMC Defrost or LRC PBMC Aliquot) and populates the Defrost/Aliquot plate Status using thresholds: viability < 50% or total cell count < 500000 cells/ml flagged.

Dependencies

This story is blocked by the following dependencies:

  • #<issue_no.>
  • sanger/#<issue_no.>

References
This story has a non-blocking relationship with:

  • #<issue_no.>
  • sanger/#<issue_no.>

Additional context
There is a story in (Seq130) which requests the creation of the LRC PBMC Aliquot plate so references to this are included in advance (the parent plate of the LRC PBMC Pools plate will either be an LRC PBMC Defrost or LRC PBMC Aliquot plate).
To populate the 'LRC PBMC Defrost/Aliquot plate Status' column, this should reference a viability threshold of 50% and a total cell count threshold of 500000 cells/ml. Anything below this we would want to flag, even if it doesn't result in a well failure.

https://docs.google.com/spreadsheets/d/1c3ZcXwH2GTimkTV2FznRkGeMiY64iywwCSMbSi9GNl8/edit?usp=sharing

Deployment notes

Add any details that should be noted when deploying this feature. For example, is a database migration needed, a specifc rake task or other script that needs to be run, a dependency on another application or service that needs to be released first etc?
These notes are intended to ensure the developers releasing the feature know what needs to be done.

Add any other context or screenshots about the feature request here.

Metadata

Metadata

Assignees

Labels

EnhancementNew feature or requestSize: MMedium - medium effort & risk
No fields configured for Feature.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions