-
Notifications
You must be signed in to change notification settings - Fork 43
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
* in snp is not allowed in MASH pipeline rds_to_vcf
#551
Comments
rds_to_vcf
rds_to_vcf
Well, other than a more technical solution on this, a general question is @hsun3163 when we "harmonize " deletion data, is there a way to harmonize it as eg
as opposed to:
? |
One immediate challenge for this is that, the |
As discussed with @rfeng2023 I think we are going to use the standard |
should we replace it in the |
They were not introduced by me, instead, they were inherited from the raw vcf.gz file, as indicated below:
Changing the * to n for only mash output may make the future comparisons between mash output and the output of other parts of our analysis pipeline difficult. |
There are some "*" (which means a deletion) in snp file will cause the error
Error in .Call2("new_XStringSet_from_CHARACTER", class(x0), elementType(x0), : key 42 (char '*') not in lookup table
That may be caused by
Biostrings::DNAStringSet(nea)
, which only allow the input chr as "ACTG".The text was updated successfully, but these errors were encountered: