You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Calculate the "allowance band" and save into a new field on request metadata (or somewhere else if makes more sense). Allowance band can be:
"Full allowance" (or "2 pool attempts, 2 counts")
"2 pool attempts, 1 count"
"1 pool attempt, 2 counts"
"1 pool attempt, 1 count"
"Allowance band" calculations:
There is already code in the submission upload that calculates whether there will be enough material for the "full allowance" (one of the bands) - added in story #4460.
See Calculations section of that story for how.
psd-issuerbot
changed the title
Calculate the "allowance band" and save into a new field on request metadata (or somewhere else if makes more sense). Allowance band can be:
Y25-076 - Calculate the "allowance band" and save into a new field on request metadata (or somewhere else if makes more sense). Allowance band can be:
Feb 3, 2025
KatyTaylor
changed the title
Y25-076 - Calculate the "allowance band" and save into a new field on request metadata (or somewhere else if makes more sense). Allowance band can be:
Y25-025 - Maintain customer-requested number of repeats (SS)
Feb 3, 2025
KatyTaylor
changed the title
Y25-025 - Maintain customer-requested number of repeats (SS)
Maintain customer-requested number of repeats (SS)
Feb 3, 2025
psd-issuerbot
changed the title
Maintain customer-requested number of repeats (SS)
Y25-077 - Maintain customer-requested number of repeats (SS)
Feb 3, 2025
@KatyTaylor Would all existing libraries be considered "Full allowance" for the new metadata? Since we are checking for this new metadata in Limber we don't want to break existing/in progress runs so do we need to backfill the existing data with "Full allowance"?
@KatyTaylor Would all existing libraries be considered "Full allowance" for the new metadata? Since we are checking for this new metadata in Limber we don't want to break existing/in progress runs so do we need to backfill the existing data with "Full allowance"?
Hi @BenTopping , thanks for raising this. The only samples that have gone through this pipeline so far are:
A test run that R&D did - using real samples - but this is finished and there's no need to backfill data for this, as this data is only used at the point of pooling (theoretically it could be used for reporting after the fact, but I don't think it will matter for this test run)
A HumGen run - libraries made in Dec, still hasn't been sequenced (I think) - not relevant for this, because it used the GEMs plate entrypoint, so after pooling.
This is necessary for sanger/limber#2164 to be delivered.
Acceptance Criteria
At point of cDNA prep submission (Sequencescape):
"Allowance band" calculations:
There is already code in the submission upload that calculates whether there will be enough material for the "full allowance" (one of the bands) - added in story #4460.
See Calculations section of that story for how.
The calculations for the other bands are similar:
"Full allowance" = ( "Chip loading volume" * 2) + (2 * 10) + 5
"2 pool attempts, 1 count" = ( "Chip loading volume" * 2) + 10 + 5
"1 pool attempt, 2 counts" = "Chip loading volume" + (2 * 10) + 5
"1 pool attempt, 1 count" = "Chip loading volume" + 10 + 5
The text was updated successfully, but these errors were encountered: