Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Y24-194 - LCM WGS/EM-Seq - Pipeline configuration and integration test #4199

Closed
5 of 7 tasks
andrewsparkes opened this issue Jul 11, 2024 · 3 comments · Fixed by #4536 or sanger/limber#2101
Closed
5 of 7 tasks
Assignees
Labels
EMSeq emSEQ EPIC An EPIC task with sub-tasks

Comments

@andrewsparkes
Copy link
Member

andrewsparkes commented Jul 11, 2024

User story
As Scott and Sara we would like tracking developed for the new LCM WGS/EM-Seq pipeline. A process map and associated documentation contain the details required.

Who are the primary contacts for this story
Scott G (R&D)
Sara W (Lab ops)

Who is the nominated tester for UAT
TBC

Acceptance criteria
Sub-stories have been created that should cover this story. The following acceptance criteria are for checking everything is joined up and tested:

  • Integration Suite test for whole pipeline, including the same samples going down both the EM-Seq and WGS branches.
  • Confirm Submission names, request type and library type names with stakeholders

Dependencies
This story is divided into two stories for EMSeq and WGS branches and a common initial part up to the Adp Lig plate. Transitive dependencies have been added here as well to find them easier.

References
This story has a non-blocking relationship with:

Additional context
See the following documents for detailed information (e.g. steps and plate purposes):
LucidChart Process Diagram
Overview document
CLCM Multiomics document

Mostly this story is standard SS and Limber configuration.
These are the tricky bits I can see (also see docs above):

  1. Submissions - Initial submission is on the Lysate plate at the start, for DNA prep (RNA branch may be added later). Then part way along this brnaches into WGS and EM paths. Both branches will always happen, in parallel. You cannot use one submission all the way through because of this later branch. But as both will always happen for all samples then you don't want to have to wait on the SSR to manually create submissions at the branch point. Possibly create an automatic submission to branch off the EM path? Have to try out some options and see what works best.
  2. There are several places where they have annotated bed verifications that want to check multiple plates in advance. We can't do bed verifications that involve transfers that go A->B->C, but we should be able to do verifying ones that check plates are in specific positions. But only if LIMS already knows about the barcodes of those plates, so they'd have to be set up in advance. Includes crossing the branching point.
  3. They would like to print out labels in advance for these steps that include the branching. I'm not sure we can do that.

The research story for the branching point is Y24-196 - LCM WGS/EM-Seq - Research - Test pipeline configuration

@psd-issuer psd-issuer bot changed the title LCM WGS/EM-Seq - Pipeline configuration and integration test Y24-194 - LCM WGS/EM-Seq - Pipeline configuration and integration test Jul 11, 2024
@andrewsparkes andrewsparkes added Size: L Large - large effort & risk EMSeq emSEQ labels Jul 11, 2024
@KatyTaylor KatyTaylor added EPIC An EPIC task with sub-tasks Size: S Small - low effort & risk and removed Size: L Large - large effort & risk labels Aug 22, 2024
@stevieing stevieing removed the Size: S Small - low effort & risk label Oct 4, 2024
@yoldas yoldas added the On Hold On hold label Nov 21, 2024
@yoldas yoldas removed the On Hold On hold label Nov 29, 2024
@yoldas
Copy link
Member

yoldas commented Dec 2, 2024

Library Types (Email)

WGS:

"For the WGS libraries that have recently been submitted for sequencing after manual EMseq library preparation they have been using:
o Library Type: LCMB
o Fragment size required (from): 450
o Fragment size required (to): 450"

However please let me confirm this with the SSRs, because using 450 for both the to & from library sizes is not what I was expecting to see.

EMSeq:

"For the EMseq libraries, there is a pre-existing library type ‘emSEQ’ which can be used to maintain consistency with the manual EMseq work done up to now."

@yoldas
Copy link
Member

yoldas commented Dec 9, 2024

I have set superseded_by on the old submission: Limber-Htp - LCM Triomics EMSeq in UAT; the replacement is Limber-Htp - LCM Triomics .

Note that the request type for the Limber-Htp - LCM Triomics submission is still 'LCM Triomics EMSeq' . This is because the pipeline starts with EMSeq and branches off for WGS later and (RNASeq in the future).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment