id stringlengths 21 21 | kind stringclasses 3
values | options listlengths 2 6 | target listlengths 2 6 | state stringlengths 166 260 | question stringclasses 7
values | domain stringclasses 1
value | family stringclasses 1
value | source stringclasses 1
value |
|---|---|---|---|---|---|---|---|---|
v3_9c509ddc69cddc06_n | noul | [
"false",
"true"
] | [
0.13,
0.87
] | A qc gate passed the cross-sample concordance; additionally failed the sex-check concordance. Context: under the CAP checklist, during normal operations. Reported by the operator. | Is this scenario one where: manual review is required? | bioinformatics_ops | genomics | yuri_v3 |
v3_533649ee97f31b11_n | noul | [
"false",
"true"
] | [
0.64,
0.36
] | A batch of 96 samples shows uniform coverage across the target; additionally passed the cross-sample concordance. Context: before the Friday release, shortly after a software update. Reported by the operator. | Is this scenario one where: manual review is required? | bioinformatics_ops | genomics | yuri_v3 |
v3_913e9b561fd91d2e_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0.23,
0.4,
0.05,
0.17,
0.06,
0.09
] | The variant-calling run completed with 0 failed checks; additionally shows uniform coverage across the target. Context: under the CAP checklist, under an active deadline. Reported by the supervisor. | Rate run quality for this scenario on a 0-5 scale. | bioinformatics_ops | genomics | yuri_v3 |
v3_5d4464d189243d70_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0.03,
0.22,
0.31,
0.42,
0.02
] | The annotation pipeline completed with 0 failed checks; additionally failed the sex-check concordance. Context: in the clinical reporting pipeline, during the holiday freeze. Reported by the automated check. | Rate data integrity risk for this scenario on a 0-5 scale. | bioinformatics_ops | genomics | yuri_v3 |
v3_4cf14ba343f7b287_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0.01,
0.31,
0.5,
0.18,
0
] | A qc gate shows a sudden coverage drop in one batch; additionally passed the cross-sample concordance. Context: under the CAP checklist, mid-incident. Reported by the monitoring system. | Rate data integrity risk for this scenario on a 0-5 scale. | bioinformatics_ops | genomics | yuri_v3 |
v3_bc9f6a871c54f37f_c | choice | [
"pre_analytical",
"library",
"sequencing",
"analysis"
] | [
0.27,
0.09,
0.45,
0.19
] | The annotation pipeline passed the cross-sample concordance; additionally shows a sudden coverage drop in one batch. Context: under the CAP checklist, with a new vendor onboarded. Reported by the monitoring system. | Failure class for this scenario. | bioinformatics_ops | genomics | yuri_v3 |
v3_7b57313d4eeab974_c | choice | [
"pre_analytical",
"library",
"sequencing",
"analysis"
] | [
0.21,
0.06,
0.5,
0.23
] | A batch of 96 samples shows uniform coverage across the target; additionally completed with 0 failed checks. Context: under the CAP checklist, while legacy systems are still active. Reported by the supervisor. | Failure class for this scenario. | bioinformatics_ops | genomics | yuri_v3 |
v3_ff7a1503cb2f0a7c_n | noul | [
"false",
"true"
] | [
0.54,
0.46
] | A batch of 96 samples has a duplicated sample ID in the manifest; additionally shows uniform coverage across the target. Context: for the research cohort, with a new vendor onboarded. Reported by the on-call engineer. | Is this scenario one where: a sample swap is suspected? | bioinformatics_ops | genomics | yuri_v3 |
v3_6b4b3c1098c9603d_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0.04,
0.62,
0.28,
0.06,
0
] | A batch of 96 samples completed with 0 failed checks; additionally produced a VCF with 3.2M variants against an expected 4.5M. Context: under the CAP checklist, during the morning shift. Reported by the automated check. | Rate run quality for this scenario on a 0-5 scale. | bioinformatics_ops | genomics | yuri_v3 |
v3_c82fd82731308c4e_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0.01,
0.27,
0.58,
0.14,
0
] | A batch of 96 samples produced a VCF with 3.2M variants against an expected 4.5M; additionally passed the cross-sample concordance. Context: under the CAP checklist, during the system migration. Reported by the supervisor. | Rate data integrity risk for this scenario on a 0-5 scale. | bioinformatics_ops | genomics | yuri_v3 |
v3_00e69bf25bc1ee06_n | noul | [
"false",
"true"
] | [
0.97,
0.03
] | A qc gate shows 14 samples below the 20x depth threshold; additionally failed the sex-check concordance. Context: under the CAP checklist, with staffing at reduced levels. Reported by the automated check. | Is this scenario one where: the run meets release criteria? | bioinformatics_ops | genomics | yuri_v3 |
v3_b9f28598c3a811f3_n | noul | [
"false",
"true"
] | [
0.06,
0.94
] | The variant-calling run shows swapped indices in two lanes; additionally failed the sex-check concordance. Context: under the CAP checklist, while on-call rotation changed. Reported by the operator. | Is this scenario one where: manual review is required? | bioinformatics_ops | genomics | yuri_v3 |
v3_371e6c63e44e5b86_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0,
0,
0.3,
0.69,
0.01
] | A qc gate shows 14 samples below the 20x depth threshold; additionally produced a VCF with 3.2M variants against an expected 4.5M. Context: in the clinical reporting pipeline, while on-call rotation changed. Reported by the on-call engineer. | Rate run quality for this scenario on a 0-5 scale. | bioinformatics_ops | genomics | yuri_v3 |
v3_1b13ae4be6102bb7_c | choice | [
"release",
"release_partial",
"hold_all",
"reprocess"
] | [
0.31,
0.2,
0.35,
0.14
] | A batch of 96 samples passed the cross-sample concordance; additionally has a contamination estimate of 8%. Context: for the research cohort, immediately after go-live. Reported by the automated check. | Batch disposition for this scenario. | bioinformatics_ops | genomics | yuri_v3 |
v3_677dbd70afa387e3_c | choice | [
"pre_analytical",
"library",
"sequencing",
"analysis"
] | [
0.06,
0.02,
0.4,
0.52
] | The variant-calling run shows uniform coverage across the target; additionally shows swapped indices in two lanes. Context: in the clinical reporting pipeline, immediately after go-live. Reported by the monitoring system. | Failure class for this scenario. | bioinformatics_ops | genomics | yuri_v3 |
v3_4cdc2616e6469714_n | noul | [
"false",
"true"
] | [
0.09,
0.91
] | The annotation pipeline failed the sex-check concordance; additionally shows 14 samples below the 20x depth threshold. Context: under the CAP checklist, during a scheduled maintenance window. Reported by the automated check. | Is this scenario one where: manual review is required? | bioinformatics_ops | genomics | yuri_v3 |
v3_a8c806037bb6f95e_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0,
0,
0.07,
0.88,
0.05
] | The variant-calling run produced a VCF with 3.2M variants against an expected 4.5M; additionally failed the sex-check concordance. Context: under the CAP checklist, during the holiday freeze. Reported by the automated check. | Rate data integrity risk for this scenario on a 0-5 scale. | bioinformatics_ops | genomics | yuri_v3 |
v3_d4ef2525db111527_c | choice | [
"pre_analytical",
"library",
"sequencing",
"analysis"
] | [
0.73,
0.07,
0.03,
0.17
] | The variant-calling run completed with 0 failed checks; additionally has a contamination estimate of 8%. Context: for the research cohort, with a new vendor onboarded. Reported by the on-call engineer. | Failure class for this scenario. | bioinformatics_ops | genomics | yuri_v3 |
v3_a53a06bf0aa2ab3c_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0,
0.01,
0.36,
0.61,
0.02
] | A batch of 96 samples has a contamination estimate of 8%; additionally shows swapped indices in two lanes. Context: before the Friday release, under an active deadline. Reported by the automated check. | Rate run quality for this scenario on a 0-5 scale. | bioinformatics_ops | genomics | yuri_v3 |
v3_5173634fe1e6c528_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0.15,
0.55,
0.29,
0.01,
0
] | A qc gate shows uniform coverage across the target; additionally has a duplicated sample ID in the manifest. Context: for the research cohort, during a scheduled maintenance window. Reported by the automated check. | Rate run quality for this scenario on a 0-5 scale. | bioinformatics_ops | genomics | yuri_v3 |
v3_5423c75ee770e4a1_c | choice | [
"pre_analytical",
"library",
"sequencing",
"analysis"
] | [
0.41,
0.11,
0.24,
0.24
] | A qc gate passed the cross-sample concordance; additionally shows swapped indices in two lanes. Context: for the research cohort, as part of a compliance sweep. Reported by the monitoring system. | Failure class for this scenario. | bioinformatics_ops | genomics | yuri_v3 |
v3_2be5d094838afec6_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0,
0.01,
0.26,
0.7,
0.03
] | A batch of 96 samples shows 14 samples below the 20x depth threshold; additionally failed the sex-check concordance. Context: for the research cohort, under an active deadline. Reported by the operator. | Rate run quality for this scenario on a 0-5 scale. | bioinformatics_ops | genomics | yuri_v3 |
v3_9d94f3023f9fa3b6_n | noul | [
"false",
"true"
] | [
0.21,
0.79
] | A batch of 96 samples passed the cross-sample concordance; additionally shows swapped indices in two lanes. Context: in the clinical reporting pipeline, during normal operations. Reported by the monitoring system. | Is this scenario one where: manual review is required? | bioinformatics_ops | genomics | yuri_v3 |
v3_3574d23e70eac5ea_c | choice | [
"pre_analytical",
"library",
"sequencing",
"analysis"
] | [
0.18,
0.05,
0.59,
0.18
] | The variant-calling run shows a sudden coverage drop in one batch; additionally has a contamination estimate of 8%. Context: for the research cohort, during the quarterly review. Reported by the supervisor. | Failure class for this scenario. | bioinformatics_ops | genomics | yuri_v3 |
v3_80545784a428ab4c_c | choice | [
"release",
"release_partial",
"hold_all",
"reprocess"
] | [
0,
0,
0.88,
0.12
] | A batch of 96 samples shows swapped indices in two lanes; additionally failed the sex-check concordance. Context: in the clinical reporting pipeline, immediately after go-live. Reported by the on-call engineer. | Batch disposition for this scenario. | bioinformatics_ops | genomics | yuri_v3 |
v3_e7f63c37ae99fc2f_c | choice | [
"release",
"release_partial",
"hold_all",
"reprocess"
] | [
0,
0.01,
0.89,
0.1
] | A qc gate shows 14 samples below the 20x depth threshold; additionally has a duplicated sample ID in the manifest. Context: before the Friday release, under an active deadline. Reported by the on-call engineer. | Batch disposition for this scenario. | bioinformatics_ops | genomics | yuri_v3 |
v3_69504e4f5ddf25f9_n | noul | [
"false",
"true"
] | [
0.93,
0.07
] | The annotation pipeline shows uniform coverage across the target; additionally failed the sex-check concordance. Context: before the Friday release, with a new vendor onboarded. Reported by the review queue. | Is this scenario one where: the run meets release criteria? | bioinformatics_ops | genomics | yuri_v3 |
v3_2b530a3436b0de4b_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0,
0,
0.42,
0.57,
0.01
] | The annotation pipeline produced a VCF with 3.2M variants against an expected 4.5M; additionally shows 14 samples below the 20x depth threshold. Context: for the research cohort, immediately after go-live. Reported by the on-call engineer. | Rate run quality for this scenario on a 0-5 scale. | bioinformatics_ops | genomics | yuri_v3 |
v3_e451589e16cfb56b_n | noul | [
"false",
"true"
] | [
0.74,
0.26
] | A batch of 96 samples shows uniform coverage across the target; additionally completed with 0 failed checks. Context: under the CAP checklist, during peak load. Reported by the review queue. | Is this scenario one where: manual review is required? | bioinformatics_ops | genomics | yuri_v3 |
v3_d95705f1907d578f_c | choice | [
"release",
"release_partial",
"hold_all",
"reprocess"
] | [
0.01,
0.25,
0.69,
0.05
] | A qc gate passed the cross-sample concordance; additionally shows a sudden coverage drop in one batch. Context: under the CAP checklist, while on-call rotation changed. Reported by the operator. | Batch disposition for this scenario. | bioinformatics_ops | genomics | yuri_v3 |
v3_25715d4b4b52d291_n | noul | [
"false",
"true"
] | [
0.87,
0.13
] | A batch of 96 samples passed the cross-sample concordance; additionally shows 14 samples below the 20x depth threshold. Context: under the CAP checklist, with staffing at reduced levels. Reported by the monitoring system. | Is this scenario one where: a sample swap is suspected? | bioinformatics_ops | genomics | yuri_v3 |
v3_10acaba282f2ec1f_n | noul | [
"false",
"true"
] | [
0.14,
0.86
] | A batch of 96 samples has a contamination estimate of 8%; additionally shows a sudden coverage drop in one batch. Context: before the Friday release, during the morning shift. Reported by the review queue. | Is this scenario one where: manual review is required? | bioinformatics_ops | genomics | yuri_v3 |
v3_5ff38bdbc0fa8743_c | choice | [
"release",
"release_partial",
"hold_all",
"reprocess"
] | [
0,
0,
0.73,
0.27
] | A batch of 96 samples produced a VCF with 3.2M variants against an expected 4.5M; additionally has a contamination estimate of 8%. Context: under the CAP checklist, while legacy systems are still active. Reported by the monitoring system. | Batch disposition for this scenario. | bioinformatics_ops | genomics | yuri_v3 |
v3_87f70ce8e4857cce_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0,
0,
0.23,
0.75,
0.02
] | A batch of 96 samples produced a VCF with 3.2M variants against an expected 4.5M; additionally has a duplicated sample ID in the manifest. Context: for the research cohort, immediately after go-live. Reported by the on-call engineer. | Rate run quality for this scenario on a 0-5 scale. | bioinformatics_ops | genomics | yuri_v3 |
v3_87f4224839b0268e_c | choice | [
"release",
"release_partial",
"hold_all",
"reprocess"
] | [
0.93,
0,
0.07,
0
] | A batch of 96 samples completed with 0 failed checks; additionally shows uniform coverage across the target. Context: in the clinical reporting pipeline, with staffing at reduced levels. Reported by the automated check. | Batch disposition for this scenario. | bioinformatics_ops | genomics | yuri_v3 |
v3_108199bff48451d3_c | choice | [
"release",
"release_partial",
"hold_all",
"reprocess"
] | [
0.02,
0.05,
0.46,
0.47
] | A batch of 96 samples shows swapped indices in two lanes; additionally shows uniform coverage across the target. Context: in the clinical reporting pipeline, under an active deadline. Reported by the operator. | Batch disposition for this scenario. | bioinformatics_ops | genomics | yuri_v3 |
v3_258bd7c33a9eef51_c | choice | [
"release",
"release_partial",
"hold_all",
"reprocess"
] | [
0.01,
0.12,
0.71,
0.16
] | The variant-calling run completed with 0 failed checks; additionally has a duplicated sample ID in the manifest. Context: in the clinical reporting pipeline, during peak load. Reported by the operator. | Batch disposition for this scenario. | bioinformatics_ops | genomics | yuri_v3 |
v3_06af6f04921b0c17_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0.26,
0.37,
0.06,
0.14,
0.07,
0.1
] | A qc gate shows uniform coverage across the target; additionally completed with 0 failed checks. Context: under the CAP checklist, under an active deadline. Reported by the review queue. | Rate run quality for this scenario on a 0-5 scale. | bioinformatics_ops | genomics | yuri_v3 |
v3_951b985392c29c88_c | choice | [
"pre_analytical",
"library",
"sequencing",
"analysis"
] | [
0.45,
0,
0,
0.55
] | The variant-calling run has a duplicated sample ID in the manifest; additionally completed with 0 failed checks. Context: under the CAP checklist, while on-call rotation changed. Reported by the review queue. | Failure class for this scenario. | bioinformatics_ops | genomics | yuri_v3 |
v3_daedbdb52c8cb342_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0.01,
0.09,
0.27,
0.56,
0.07
] | A batch of 96 samples shows swapped indices in two lanes; additionally completed with 0 failed checks. Context: for the research cohort, shortly after a software update. Reported by the on-call engineer. | Rate data integrity risk for this scenario on a 0-5 scale. | bioinformatics_ops | genomics | yuri_v3 |
v3_eb7567cde96972ad_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0,
0,
0.06,
0.85,
0.09
] | The annotation pipeline shows a sudden coverage drop in one batch; additionally failed the sex-check concordance. Context: in the clinical reporting pipeline, while legacy systems are still active. Reported by the on-call engineer. | Rate data integrity risk for this scenario on a 0-5 scale. | bioinformatics_ops | genomics | yuri_v3 |
v3_25718fe9ab0a564a_n | noul | [
"false",
"true"
] | [
0.67,
0.33
] | A qc gate has a contamination estimate of 8%; additionally produced a VCF with 3.2M variants against an expected 4.5M. Context: in the clinical reporting pipeline, during the holiday freeze. Reported by the operator. | Is this scenario one where: a sample swap is suspected? | bioinformatics_ops | genomics | yuri_v3 |
v3_4669b818a1653fd2_c | choice | [
"pre_analytical",
"library",
"sequencing",
"analysis"
] | [
0.26,
0.11,
0.06,
0.57
] | A batch of 96 samples produced a VCF with 3.2M variants against an expected 4.5M; additionally has a contamination estimate of 8%. Context: in the clinical reporting pipeline, as part of a compliance sweep. Reported by the supervisor. | Failure class for this scenario. | bioinformatics_ops | genomics | yuri_v3 |
v3_b4d6f67b22dd9f71_c | choice | [
"release",
"release_partial",
"hold_all",
"reprocess"
] | [
0.03,
0.02,
0.88,
0.07
] | A batch of 96 samples completed with 0 failed checks; additionally failed the sex-check concordance. Context: for the research cohort, during an external partner integration. Reported by the on-call engineer. | Batch disposition for this scenario. | bioinformatics_ops | genomics | yuri_v3 |
v3_39503f383b45ab44_n | noul | [
"false",
"true"
] | [
0.1,
0.9
] | The annotation pipeline has a duplicated sample ID in the manifest; additionally shows swapped indices in two lanes. Context: in the clinical reporting pipeline, at the end of the fiscal period. Reported by the operator. | Is this scenario one where: a sample swap is suspected? | bioinformatics_ops | genomics | yuri_v3 |
v3_6a333a85652838a2_n | noul | [
"false",
"true"
] | [
0.23,
0.77
] | The variant-calling run has a contamination estimate of 8%; additionally failed the sex-check concordance. Context: in the clinical reporting pipeline, while legacy systems are still active. Reported by the supervisor. | Is this scenario one where: a sample swap is suspected? | bioinformatics_ops | genomics | yuri_v3 |
v3_462388da257c1fd3_c | choice | [
"release",
"release_partial",
"hold_all",
"reprocess"
] | [
0,
0,
0.49,
0.51
] | The variant-calling run has a duplicated sample ID in the manifest; additionally produced a VCF with 3.2M variants against an expected 4.5M. Context: before the Friday release, with staffing at reduced levels. Reported by the operator. | Batch disposition for this scenario. | bioinformatics_ops | genomics | yuri_v3 |
v3_054be1647c8bfa51_c | choice | [
"release",
"release_partial",
"hold_all",
"reprocess"
] | [
0.35,
0.02,
0.47,
0.16
] | A qc gate has a contamination estimate of 8%; additionally completed with 0 failed checks. Context: under the CAP checklist, at the end of the fiscal period. Reported by the monitoring system. | Batch disposition for this scenario. | bioinformatics_ops | genomics | yuri_v3 |
v3_a2bd21abdc6099d7_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0.69,
0.17,
0.08,
0.04,
0.01,
0.01
] | The variant-calling run completed with 0 failed checks; additionally shows uniform coverage across the target. Context: under the CAP checklist, during normal operations. Reported by the review queue. | Rate data integrity risk for this scenario on a 0-5 scale. | bioinformatics_ops | genomics | yuri_v3 |
v3_09105d07b8b32be0_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0,
0.03,
0.37,
0.56,
0.04
] | A batch of 96 samples has a contamination estimate of 8%; additionally failed the sex-check concordance. Context: before the Friday release, as part of a compliance sweep. Reported by the automated check. | Rate run quality for this scenario on a 0-5 scale. | bioinformatics_ops | genomics | yuri_v3 |
v3_85da3cd6024190f8_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0,
0,
0.03,
0.92,
0.05
] | A batch of 96 samples produced a VCF with 3.2M variants against an expected 4.5M; additionally failed the sex-check concordance. Context: in the clinical reporting pipeline, with a new vendor onboarded. Reported by the review queue. | Rate data integrity risk for this scenario on a 0-5 scale. | bioinformatics_ops | genomics | yuri_v3 |
v3_eeb626b38b65c929_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0,
0.01,
0.64,
0.35,
0
] | A qc gate has a contamination estimate of 8%; additionally shows 14 samples below the 20x depth threshold. Context: before the Friday release, while on-call rotation changed. Reported by the on-call engineer. | Rate data integrity risk for this scenario on a 0-5 scale. | bioinformatics_ops | genomics | yuri_v3 |
v3_070b4e3a014396e4_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0,
0,
0.14,
0.82,
0.04
] | The variant-calling run failed the sex-check concordance; additionally has a duplicated sample ID in the manifest. Context: under the CAP checklist, while legacy systems are still active. Reported by the supervisor. | Rate data integrity risk for this scenario on a 0-5 scale. | bioinformatics_ops | genomics | yuri_v3 |
v3_a31f3c8e20197586_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0,
0,
0.3,
0.69,
0.01
] | A batch of 96 samples shows a sudden coverage drop in one batch; additionally has a duplicated sample ID in the manifest. Context: in the clinical reporting pipeline, during the morning shift. Reported by the supervisor. | Rate run quality for this scenario on a 0-5 scale. | bioinformatics_ops | genomics | yuri_v3 |
v3_c9652ec0b59ca731_n | noul | [
"false",
"true"
] | [
0.13,
0.87
] | The variant-calling run has a duplicated sample ID in the manifest; additionally shows swapped indices in two lanes. Context: for the research cohort, following a recent audit. Reported by the automated check. | Is this scenario one where: a sample swap is suspected? | bioinformatics_ops | genomics | yuri_v3 |
v3_f6f0fd7157c5ac0d_n | noul | [
"false",
"true"
] | [
0.26,
0.74
] | The variant-calling run shows a sudden coverage drop in one batch; additionally passed the cross-sample concordance. Context: under the CAP checklist, during normal operations. Reported by the on-call engineer. | Is this scenario one where: manual review is required? | bioinformatics_ops | genomics | yuri_v3 |
v3_73271e58505990e8_c | choice | [
"release",
"release_partial",
"hold_all",
"reprocess"
] | [
0.02,
0.04,
0.34,
0.6
] | A batch of 96 samples shows swapped indices in two lanes; additionally completed with 0 failed checks. Context: for the research cohort, during the system migration. Reported by the on-call engineer. | Batch disposition for this scenario. | bioinformatics_ops | genomics | yuri_v3 |
v3_a57f06e599b79d11_n | noul | [
"false",
"true"
] | [
0.07,
0.93
] | The annotation pipeline shows swapped indices in two lanes; additionally failed the sex-check concordance. Context: for the research cohort, during the system migration. Reported by the supervisor. | Is this scenario one where: a sample swap is suspected? | bioinformatics_ops | genomics | yuri_v3 |
v3_d9d0c007a23a1340_n | noul | [
"false",
"true"
] | [
0.85,
0.15
] | A batch of 96 samples has a contamination estimate of 8%; additionally has a duplicated sample ID in the manifest. Context: in the clinical reporting pipeline, with a new vendor onboarded. Reported by the monitoring system. | Is this scenario one where: the run meets release criteria? | bioinformatics_ops | genomics | yuri_v3 |
v3_a1fe2a03f1447b7c_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0,
0.04,
0.85,
0.11,
0
] | A batch of 96 samples shows 14 samples below the 20x depth threshold; additionally has a contamination estimate of 8%. Context: for the research cohort, during the morning shift. Reported by the automated check. | Rate data integrity risk for this scenario on a 0-5 scale. | bioinformatics_ops | genomics | yuri_v3 |
v3_1fdd05bb7b8bfbee_c | choice | [
"pre_analytical",
"library",
"sequencing",
"analysis"
] | [
0.92,
0.04,
0.01,
0.03
] | A batch of 96 samples has a duplicated sample ID in the manifest; additionally has a contamination estimate of 8%. Context: under the CAP checklist, during the quarterly review. Reported by the on-call engineer. | Failure class for this scenario. | bioinformatics_ops | genomics | yuri_v3 |
v3_bf490beaeb2018fd_c | choice | [
"release",
"release_partial",
"hold_all",
"reprocess"
] | [
0,
0.01,
0.6,
0.39
] | The annotation pipeline shows swapped indices in two lanes; additionally shows uniform coverage across the target. Context: in the clinical reporting pipeline, during the holiday freeze. Reported by the on-call engineer. | Batch disposition for this scenario. | bioinformatics_ops | genomics | yuri_v3 |
v3_c9362e0d8160c67e_n | noul | [
"false",
"true"
] | [
0.31,
0.69
] | A batch of 96 samples shows uniform coverage across the target; additionally failed the sex-check concordance. Context: for the research cohort, while on-call rotation changed. Reported by the operator. | Is this scenario one where: a sample swap is suspected? | bioinformatics_ops | genomics | yuri_v3 |
v3_5b082394e1903250_c | choice | [
"pre_analytical",
"library",
"sequencing",
"analysis"
] | [
0.02,
0,
0,
0.98
] | The variant-calling run failed the sex-check concordance; additionally completed with 0 failed checks. Context: before the Friday release, during the holiday freeze. Reported by the operator. | Failure class for this scenario. | bioinformatics_ops | genomics | yuri_v3 |
v3_0a14c2a521c26e87_c | choice | [
"release",
"release_partial",
"hold_all",
"reprocess"
] | [
0.84,
0,
0.16,
0
] | A batch of 96 samples passed the cross-sample concordance; additionally completed with 0 failed checks. Context: under the CAP checklist, during the holiday freeze. Reported by the automated check. | Batch disposition for this scenario. | bioinformatics_ops | genomics | yuri_v3 |
v3_2e842457cacbffa6_n | noul | [
"false",
"true"
] | [
0.19,
0.81
] | The variant-calling run completed with 0 failed checks; additionally failed the sex-check concordance. Context: before the Friday release, while on-call rotation changed. Reported by the on-call engineer. | Is this scenario one where: manual review is required? | bioinformatics_ops | genomics | yuri_v3 |
v3_ced1ae158b714116_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0.44,
0.29,
0.13,
0.11,
0.02,
0.01
] | A batch of 96 samples shows uniform coverage across the target; additionally passed the cross-sample concordance. Context: before the Friday release, at the end of the fiscal period. Reported by the automated check. | Rate data integrity risk for this scenario on a 0-5 scale. | bioinformatics_ops | genomics | yuri_v3 |
v3_20d516402fcf3c55_c | choice | [
"release",
"release_partial",
"hold_all",
"reprocess"
] | [
0.01,
0.01,
0.81,
0.17
] | A qc gate failed the sex-check concordance; additionally completed with 0 failed checks. Context: in the clinical reporting pipeline, following a recent audit. Reported by the monitoring system. | Batch disposition for this scenario. | bioinformatics_ops | genomics | yuri_v3 |
v3_a2b2ffcaa9990181_n | noul | [
"false",
"true"
] | [
0.08,
0.92
] | The annotation pipeline has a duplicated sample ID in the manifest; additionally produced a VCF with 3.2M variants against an expected 4.5M. Context: in the clinical reporting pipeline, during the morning shift. Reported by the on-call engineer. | Is this scenario one where: manual review is required? | bioinformatics_ops | genomics | yuri_v3 |
v3_ae35be6affbfd774_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0,
0,
0.28,
0.7,
0.02
] | The annotation pipeline shows a sudden coverage drop in one batch; additionally shows swapped indices in two lanes. Context: for the research cohort, mid-incident. Reported by the on-call engineer. | Rate run quality for this scenario on a 0-5 scale. | bioinformatics_ops | genomics | yuri_v3 |
v3_9f71e5b816f0cd4f_c | choice | [
"release",
"release_partial",
"hold_all",
"reprocess"
] | [
0.01,
0.01,
0.77,
0.21
] | A batch of 96 samples failed the sex-check concordance; additionally shows uniform coverage across the target. Context: in the clinical reporting pipeline, while legacy systems are still active. Reported by the supervisor. | Batch disposition for this scenario. | bioinformatics_ops | genomics | yuri_v3 |
v3_c3223324435d63bd_c | choice | [
"release",
"release_partial",
"hold_all",
"reprocess"
] | [
0.02,
0.04,
0.47,
0.47
] | The variant-calling run completed with 0 failed checks; additionally shows swapped indices in two lanes. Context: before the Friday release, during an external partner integration. Reported by the review queue. | Batch disposition for this scenario. | bioinformatics_ops | genomics | yuri_v3 |
v3_52a5bf3dd9b69947_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0,
0.31,
0.4,
0.28,
0.01
] | The annotation pipeline failed the sex-check concordance; additionally passed the cross-sample concordance. Context: in the clinical reporting pipeline, during an external partner integration. Reported by the monitoring system. | Rate data integrity risk for this scenario on a 0-5 scale. | bioinformatics_ops | genomics | yuri_v3 |
v3_cc26287b58f7b8f1_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0.01,
0.28,
0.59,
0.12,
0
] | The variant-calling run shows a sudden coverage drop in one batch; additionally completed with 0 failed checks. Context: before the Friday release, under reduced staffing. Reported by the monitoring system. | Rate data integrity risk for this scenario on a 0-5 scale. | bioinformatics_ops | genomics | yuri_v3 |
v3_4220d7dd02679ff5_n | noul | [
"false",
"true"
] | [
0.96,
0.04
] | A batch of 96 samples shows a sudden coverage drop in one batch; additionally failed the sex-check concordance. Context: for the research cohort, immediately after go-live. Reported by the review queue. | Is this scenario one where: the run meets release criteria? | bioinformatics_ops | genomics | yuri_v3 |
v3_d3d1de5ff91b6ec3_n | noul | [
"false",
"true"
] | [
0.38,
0.62
] | The annotation pipeline passed the cross-sample concordance; additionally shows 14 samples below the 20x depth threshold. Context: for the research cohort, during normal operations. Reported by the review queue. | Is this scenario one where: manual review is required? | bioinformatics_ops | genomics | yuri_v3 |
v3_ffcc475f8b1de1fa_c | choice | [
"pre_analytical",
"library",
"sequencing",
"analysis"
] | [
0.05,
0.01,
0.02,
0.92
] | The variant-calling run shows uniform coverage across the target; additionally completed with 0 failed checks. Context: before the Friday release, while legacy systems are still active. Reported by the on-call engineer. | Failure class for this scenario. | bioinformatics_ops | genomics | yuri_v3 |
v3_03a499d031bf1b3c_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0,
0,
0.32,
0.67,
0.01
] | The annotation pipeline has a contamination estimate of 8%; additionally has a duplicated sample ID in the manifest. Context: in the clinical reporting pipeline, shortly after a software update. Reported by the supervisor. | Rate data integrity risk for this scenario on a 0-5 scale. | bioinformatics_ops | genomics | yuri_v3 |
v3_f130308e29d28c48_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0,
0,
0.25,
0.74,
0.01
] | A batch of 96 samples shows a sudden coverage drop in one batch; additionally has a duplicated sample ID in the manifest. Context: before the Friday release, mid-incident. Reported by the monitoring system. | Rate data integrity risk for this scenario on a 0-5 scale. | bioinformatics_ops | genomics | yuri_v3 |
v3_7f292c299b48eb7f_c | choice | [
"pre_analytical",
"library",
"sequencing",
"analysis"
] | [
0.03,
0.02,
0.04,
0.91
] | A batch of 96 samples produced a VCF with 3.2M variants against an expected 4.5M; additionally shows uniform coverage across the target. Context: for the research cohort, while legacy systems are still active. Reported by the on-call engineer. | Failure class for this scenario. | bioinformatics_ops | genomics | yuri_v3 |
v3_add7ec620cae3264_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0,
0.01,
0.44,
0.54,
0.01
] | The annotation pipeline has a duplicated sample ID in the manifest; additionally has a contamination estimate of 8%. Context: in the clinical reporting pipeline, at the end of the fiscal period. Reported by the on-call engineer. | Rate data integrity risk for this scenario on a 0-5 scale. | bioinformatics_ops | genomics | yuri_v3 |
v3_2af5477850beea7e_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0,
0,
0.04,
0.72,
0.24
] | The variant-calling run failed the sex-check concordance; additionally shows swapped indices in two lanes. Context: in the clinical reporting pipeline, during an external partner integration. Reported by the automated check. | Rate data integrity risk for this scenario on a 0-5 scale. | bioinformatics_ops | genomics | yuri_v3 |
v3_538e2bae1f9da227_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0.01,
0.3,
0.56,
0.13,
0
] | A qc gate passed the cross-sample concordance; additionally shows a sudden coverage drop in one batch. Context: under the CAP checklist, following a recent audit. Reported by the on-call engineer. | Rate data integrity risk for this scenario on a 0-5 scale. | bioinformatics_ops | genomics | yuri_v3 |
v3_928f78a662269a62_n | noul | [
"false",
"true"
] | [
0.1,
0.9
] | The annotation pipeline shows a sudden coverage drop in one batch; additionally failed the sex-check concordance. Context: in the clinical reporting pipeline, during a scheduled maintenance window. Reported by the operator. | Is this scenario one where: manual review is required? | bioinformatics_ops | genomics | yuri_v3 |
v3_1723bfebcb7749ee_n | noul | [
"false",
"true"
] | [
0.64,
0.36
] | The annotation pipeline has a contamination estimate of 8%; additionally has a duplicated sample ID in the manifest. Context: under the CAP checklist, following a recent audit. Reported by the automated check. | Is this scenario one where: a sample swap is suspected? | bioinformatics_ops | genomics | yuri_v3 |
v3_5923a1a4958558e2_n | noul | [
"false",
"true"
] | [
0.08,
0.92
] | A batch of 96 samples has a duplicated sample ID in the manifest; additionally shows a sudden coverage drop in one batch. Context: under the CAP checklist, with staffing at reduced levels. Reported by the on-call engineer. | Is this scenario one where: manual review is required? | bioinformatics_ops | genomics | yuri_v3 |
v3_c8668c7b2cea686a_n | noul | [
"false",
"true"
] | [
0.95,
0.05
] | The variant-calling run has a duplicated sample ID in the manifest; additionally shows a sudden coverage drop in one batch. Context: before the Friday release, during the quarterly review. Reported by the review queue. | Is this scenario one where: the run meets release criteria? | bioinformatics_ops | genomics | yuri_v3 |
v3_74fb7c0abd409556_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0,
0,
0.1313,
0.8182,
0.0505
] | The variant-calling run shows 14 samples below the 20x depth threshold; additionally failed the sex-check concordance. Context: under the CAP checklist, during an external partner integration. Reported by the supervisor. | Rate run quality for this scenario on a 0-5 scale. | bioinformatics_ops | genomics | yuri_v3 |
v3_4fd243ee87c85bf1_c | choice | [
"release",
"release_partial",
"hold_all",
"reprocess"
] | [
0.04,
0.26,
0.58,
0.12
] | A qc gate has a duplicated sample ID in the manifest; additionally passed the cross-sample concordance. Context: in the clinical reporting pipeline, during the morning shift. Reported by the monitoring system. | Batch disposition for this scenario. | bioinformatics_ops | genomics | yuri_v3 |
v3_0d1ba3aa3b0f743a_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0,
0,
0.03,
0.71,
0.26
] | The variant-calling run shows swapped indices in two lanes; additionally failed the sex-check concordance. Context: in the clinical reporting pipeline, during the system migration. Reported by the operator. | Rate data integrity risk for this scenario on a 0-5 scale. | bioinformatics_ops | genomics | yuri_v3 |
v3_a2e012eee47786c0_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0.05,
0.53,
0.37,
0.05,
0
] | The annotation pipeline shows swapped indices in two lanes; additionally completed with 0 failed checks. Context: under the CAP checklist, while on-call rotation changed. Reported by the supervisor. | Rate run quality for this scenario on a 0-5 scale. | bioinformatics_ops | genomics | yuri_v3 |
v3_45d78c4c814e450a_c | choice | [
"pre_analytical",
"library",
"sequencing",
"analysis"
] | [
0.65,
0.22,
0.01,
0.12
] | A batch of 96 samples has a contamination estimate of 8%; additionally has a duplicated sample ID in the manifest. Context: before the Friday release, during the morning shift. Reported by the review queue. | Failure class for this scenario. | bioinformatics_ops | genomics | yuri_v3 |
v3_c81f21918cc6d956_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0.01,
0.55,
0.3,
0.13,
0.01
] | A qc gate shows 14 samples below the 20x depth threshold; additionally shows uniform coverage across the target. Context: for the research cohort, under an active deadline. Reported by the automated check. | Rate run quality for this scenario on a 0-5 scale. | bioinformatics_ops | genomics | yuri_v3 |
v3_e149fac1e2e6ce35_c | choice | [
"pre_analytical",
"library",
"sequencing",
"analysis"
] | [
0.26,
0.01,
0.12,
0.61
] | The variant-calling run shows a sudden coverage drop in one batch; additionally has a duplicated sample ID in the manifest. Context: in the clinical reporting pipeline, mid-incident. Reported by the review queue. | Failure class for this scenario. | bioinformatics_ops | genomics | yuri_v3 |
v3_21d107c8b834a3d7_c | choice | [
"release",
"release_partial",
"hold_all",
"reprocess"
] | [
0,
0,
0.66,
0.34
] | The variant-calling run shows swapped indices in two lanes; additionally has a duplicated sample ID in the manifest. Context: under the CAP checklist, during the system migration. Reported by the automated check. | Batch disposition for this scenario. | bioinformatics_ops | genomics | yuri_v3 |
v3_350e96306b91e8bb_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0.38,
0.44,
0.03,
0.08,
0.01,
0.06
] | A qc gate passed the cross-sample concordance; additionally completed with 0 failed checks. Context: in the clinical reporting pipeline, under an active deadline. Reported by the monitoring system. | Rate run quality for this scenario on a 0-5 scale. | bioinformatics_ops | genomics | yuri_v3 |
v3_88e96e2538f796e7_c | choice | [
"pre_analytical",
"library",
"sequencing",
"analysis"
] | [
0.36,
0.01,
0.1,
0.53
] | The annotation pipeline shows 14 samples below the 20x depth threshold; additionally has a duplicated sample ID in the manifest. Context: under the CAP checklist, under reduced staffing. Reported by the on-call engineer. | Failure class for this scenario. | bioinformatics_ops | genomics | yuri_v3 |
v3_8dee8f00e58563b5_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0,
0,
0.09,
0.84,
0.07
] | The annotation pipeline failed the sex-check concordance; additionally shows a sudden coverage drop in one batch. Context: before the Friday release, with a new vendor onboarded. Reported by the automated check. | Rate run quality for this scenario on a 0-5 scale. | bioinformatics_ops | genomics | yuri_v3 |
v3_e6590eb1be65ce33_c | choice | [
"pre_analytical",
"library",
"sequencing",
"analysis"
] | [
0.35,
0.25,
0.15,
0.25
] | A qc gate has a contamination estimate of 8%; additionally completed with 0 failed checks. Context: before the Friday release, while legacy systems are still active. Reported by the review queue. | Failure class for this scenario. | bioinformatics_ops | genomics | yuri_v3 |
v3_e8a8bdb00f887c4e_c | choice | [
"release",
"release_partial",
"hold_all",
"reprocess"
] | [
0,
0.04,
0.19,
0.77
] | The variant-calling run shows swapped indices in two lanes; additionally shows 14 samples below the 20x depth threshold. Context: for the research cohort, during normal operations. Reported by the monitoring system. | Batch disposition for this scenario. | bioinformatics_ops | genomics | yuri_v3 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.