Describe the bug
I ran into some errors while running my data processing pipeline. Apparently, VV can generate mappings to transcripts without actually generating DNA and protein descriptions. The flag value is processing_error, but my library, apparently, didn't pick up on that because no actual messages are included in errors.
To Reproduce
Using the open endpoint so I can link to the output: https://rest.variantvalidator.org/LOVD/lovd/GRCh37/NC_000011.9%3Ag.111742146del/refseq/all/tx/False?content-type=application%2Fjson
Produces (shortened output):
{
"NC_000011.9:g.111742146del": {
"NC_000011.9:g.111742146del": {
"g_hgvs": "NC_000011.9:g.111742146del",
"genomic_variant_error": null,
"genomic_variant_warnings": null,
"hgvs_t_and_p": {
"NM_001077690.1": {
"p_hgvs_slc": null,
"p_hgvs_tlc": null,
"t_hgvs": null,
"transcript_variant_error": null,
"transcript_version_warning": null
},
"NM_001352409.1": {
"p_hgvs_slc": null,
"p_hgvs_tlc": null,
"t_hgvs": null,
"transcript_variant_error": null,
"transcript_version_warning": null
},
"NM_001352410.1": {
"p_hgvs_slc": null,
"p_hgvs_tlc": null,
"t_hgvs": null,
"transcript_variant_error": null,
"transcript_version_warning": null
},
"NM_001352413.1": {
"p_hgvs_slc": null,
"p_hgvs_tlc": null,
"t_hgvs": null,
"transcript_variant_error": null,
"transcript_version_warning": null
},
"NM_001352417.1": {
"p_hgvs_slc": null,
"p_hgvs_tlc": null,
"t_hgvs": null,
"transcript_variant_error": null,
"transcript_version_warning": null
},
"NM_001352418.1": {
"p_hgvs_slc": null,
"p_hgvs_tlc": null,
"t_hgvs": null,
"transcript_variant_error": null,
"transcript_version_warning": null
},
"NM_024740.2": {
"p_hgvs_slc": null,
"p_hgvs_tlc": null,
"t_hgvs": null,
"transcript_variant_error": null,
"transcript_version_warning": null
}
}
},
"errors": [],
"flag": "processing_error"
}
}
Any clue what may be going on? I'm having more variants on other chromosomes where this happens, but I assume it's the same problem. Since all error fields are empty, I really have no clue what might be happening. There are no warnings about alignment gaps, either.
Expected behavior
When an error occurs, having a message will flag my library that there is a problem (although I could update it to do something with the flag, even in the absence of any messages). If the mapping is the issue, removing the mappings would probably be better.
Describe the bug
I ran into some errors while running my data processing pipeline. Apparently, VV can generate mappings to transcripts without actually generating DNA and protein descriptions. The
flagvalue isprocessing_error, but my library, apparently, didn't pick up on that because no actual messages are included inerrors.To Reproduce
Using the open endpoint so I can link to the output: https://rest.variantvalidator.org/LOVD/lovd/GRCh37/NC_000011.9%3Ag.111742146del/refseq/all/tx/False?content-type=application%2Fjson
Produces (shortened output):
{ "NC_000011.9:g.111742146del": { "NC_000011.9:g.111742146del": { "g_hgvs": "NC_000011.9:g.111742146del", "genomic_variant_error": null, "genomic_variant_warnings": null, "hgvs_t_and_p": { "NM_001077690.1": { "p_hgvs_slc": null, "p_hgvs_tlc": null, "t_hgvs": null, "transcript_variant_error": null, "transcript_version_warning": null }, "NM_001352409.1": { "p_hgvs_slc": null, "p_hgvs_tlc": null, "t_hgvs": null, "transcript_variant_error": null, "transcript_version_warning": null }, "NM_001352410.1": { "p_hgvs_slc": null, "p_hgvs_tlc": null, "t_hgvs": null, "transcript_variant_error": null, "transcript_version_warning": null }, "NM_001352413.1": { "p_hgvs_slc": null, "p_hgvs_tlc": null, "t_hgvs": null, "transcript_variant_error": null, "transcript_version_warning": null }, "NM_001352417.1": { "p_hgvs_slc": null, "p_hgvs_tlc": null, "t_hgvs": null, "transcript_variant_error": null, "transcript_version_warning": null }, "NM_001352418.1": { "p_hgvs_slc": null, "p_hgvs_tlc": null, "t_hgvs": null, "transcript_variant_error": null, "transcript_version_warning": null }, "NM_024740.2": { "p_hgvs_slc": null, "p_hgvs_tlc": null, "t_hgvs": null, "transcript_variant_error": null, "transcript_version_warning": null } } }, "errors": [], "flag": "processing_error" } }Any clue what may be going on? I'm having more variants on other chromosomes where this happens, but I assume it's the same problem. Since all error fields are empty, I really have no clue what might be happening. There are no warnings about alignment gaps, either.
Expected behavior
When an error occurs, having a message will flag my library that there is a problem (although I could update it to do something with the flag, even in the absence of any messages). If the mapping is the issue, removing the mappings would probably be better.