-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Genome Nexus: 41 variants that have incorrectly annotated ref/alt. #34
Comments
@thomasyu888 could you elaborate what these columns represent exactly:
I assume that we need at least these three sets of columns to solve this issue (or something similar):
But I only see In addition these miss end position. In my understanding the annotation-tools converts VCF to MAF and thereby computes the End_Position. It would be good to add that as well. Ideally to make the debugging easier, we would have all this:
Could you help provide these? |
Ah, @inodb this is only the current output (CURRENT...) and expected output (EXPECTED...) I didn't pull down the input. One thing to note is that if these are from maf files, they may not have end_positions. I would have to double check. |
Sorry for the delay, Ill slowly add resources here. There is one variant that is a VCF. I won't upload the center input: input.vcf.txt |
More resources - I split these up because some sites have different input files as well. center input: input_1.txt |
More: center input: input_2.txt |
Final: center input: input.txt |
@thomasyu888 I've started looking into this and wanted to follow up on an inconsistency I found. Idk if there are others, just that the first one I started looking at the REF/ALT are not what's reported in the diff file you shared above. These are the POS, REF, ALT in the VCF from the input file in this comment
But the diff file shows
|
I found similar inconsistencies in the other input example files as well. I'm not really sure how to approach this either because of the differing inputs from the diff file shared:
from the input file (input2)
Just eye balling what this might resolve to.. which still doesn't match what the my assumption:
the expected values reported in the diff file shared
|
Sorry about the confusion @ao508 . The diff file doesnt show what's in the input.txt. The diff file is supposed to match what's in processed.txt. what the collaborator is suggesting is that those are incorrect and the corrected ref/alt in the other columns of the diff file. |
I think I've resolved an issue that affected at least some of these variants #39 |
Uploaded as file for ease. ref_alt_diff.txt
The text was updated successfully, but these errors were encountered: