Closed zdorman closed 2 years ago
@zdorman Thank you for creating this issue. Could you also create another issue at https://github.com/CBIIT/ppdc-config/issues to keep track of the required PedOT front-end configuration file changes? The configuration file changes will make PedOT front-end compatible with the proposed v11 JSONL file field names.
cc @jonkiky
Thanks, @zdorman, I'll update the three modules for the v11 release.
Closing with PR149, PR155 and PR156 merged.
What data file(s) does this issue pertain to?
SNV by Gene:
gene-level-snv-consensus-annotated-mut-freq.jsonl
SNV by Variant:variant-level-snv-consensus-annotated-mut-freq.jsonl
CNV by Gene:gene-level-cnv-consensus-annotated-mut-freq.jsonl
Fusion by Gene:putative-oncogene-fused-gene-freq.jsonl
Fusion:putative-oncogene-fusion-freq.jsonl
What release are you using?
v10
Put your question or report your issue here.
To improve consistency of the MTP ETL process, please consider the following changes to field names in the v11 Somatic Alteration (aka Somatic Mutation) JSONL files. A total of 15 fields (3 analogous fields in each of 5 files) would be affected. When v11 is released with the changes, FNL will update the relevant ids and configuration files.
The 3 fields in each file currently follow the general format of:
Total_mutations_Over_Patients_in_dataset
Total_primary_tumors_mutated_Over_Primary_tumors_in_dataset
Total_relapse_tumors_mutated_Over_Relapse_tumors_in_dataset
patients
withsubjects
in all 5 JSONL fields containingpatients
altered
withmutated
in 2 CNV by Gene JSONL fields for consistencyFull table of changes:
(I realize that some of the CNV by Gene inconsistencies addressed here ultimately stem from my request in #197. Thanks for your patience!)