-
Notifications
You must be signed in to change notification settings - Fork 16
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
Error importing converted vcf #35
Comments
Thanks for the alert on this issue. |
You are correct - the error does appear after reading the tassel format data file source("GBS-Chip-Gmatrix.R") not when running calcG(). I've attached a portion of my data file! |
Hi, it looks like there is an issue with your RA file. Are you able to please share your VCF file and the pipeline you used to generate the VCF file? |
Apologies, I mistakenly closed the issue... |
I used the GBS_SNP_CROP pipeline and attached my vcf file. |
Thanks for sending the vcf. We had not realised that the AD field was being used in (at least) 2 different ways. The script was written to expect a pair of read depths (ref,alt) associated with each genotype for this field. (This is how GATK and samtools use this label). We are looking at how much effort might be required to convert this type of vcf. |
Hi, I've tried reproducing your problem (malformed AD field) in v3.0, v.4.0, v4.1 of GBS-SNP-CROP. The AD field looks fine in all versions and properly reports pairs of read depths (ref, alt), not like in your VCF file. What version of GBS-SNP-CROP did you use? I'm recommending script 8 of v4.0 to produce VCF files as the other versions have some other not AD related problems. |
I successfully converted my vcf file to the tassel format with the supplied python helper script (thanks!), but there seems to be an issue when running Gfull <-calcG().
Error in alleles[iind, ] <- matrix(as.numeric(unlist(strsplit(genosin[[iind + :
number of items to replace is not a multiple of replacement length
Would you have any solutions for this?
Thanks!
The text was updated successfully, but these errors were encountered: