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
We are in the process of both adding short term improvements to RNA data loading (e.g. #4815) to get in particular tomte data loading as we did MIP RNA. At the same time reworking the way this is handled in CG Solna integration (Clinical-Genomics/cg#3669). It would seem a Good Time to rework how cases and analysis is handled in Scout loading.
I propose we instead allow additional WTS and other OMICS samples to enter the samples list. These can then be formally connected to other samples via sharing a subject_id (an already existing LIMS ID key on samples) or by knowledge from the customer analyst. In very few instances does Scout actually need to know who is who, other than to help the analyst not misread sample names when looking at a view with multiple alignments.
The existing RNA and DNA build keys affecting the whole case (including variants multisample VCF files) can still be used to define build for the respective analysis types.
This discussion was converted from issue #4816 on September 04, 2024 07:27.
Heading
Bold
Italic
Quote
Code
Link
Numbered list
Unordered list
Task list
Attach files
Mention
Reference
Menu
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
We are in the process of both adding short term improvements to RNA data loading (e.g. #4815) to get in particular tomte data loading as we did MIP RNA. At the same time reworking the way this is handled in CG Solna integration (Clinical-Genomics/cg#3669). It would seem a Good Time to rework how cases and analysis is handled in Scout loading.
The primary loading is via
scout load case config.yaml
. Said yaml load configs (https://clinical-genomics.github.io/scout/admin-guide/load-config/) describe the case and samples:RNA data is currently added "on top" of other data for a sample, although that sample may or may not be an actual RNA sample.
E.g.
I propose we instead allow additional WTS and other OMICS samples to enter the samples list. These can then be formally connected to other samples via sharing a
subject_id
(an already existing LIMS ID key onsamples
) or by knowledge from the customer analyst. In very few instances does Scout actually need to know who is who, other than to help the analyst not misread sample names when looking at a view with multiple alignments.The existing RNA and DNA build keys affecting the whole case (including variants multisample VCF files) can still be used to define build for the respective analysis types.
Beta Was this translation helpful? Give feedback.
All reactions