help with CrossMap
Hello all,
I would really appreciate your help as I am new to working with different file builds and having a setback lifting a vcf file from build hg38 to hg19. in essence, using CrossMap the chromosome value gets altered. Like for example, below is the code:
CrossMap.py vcf hg38ToHg19.over.chain.gz inpute_hg38.vcf.gz hg19.fa.gz output.hg19.vcf
The output file has the value
chr1_gl000192_random 526406 chr1:149144526:SG G A .
While the file have the value
chr1 149144526 chr1:149144526:SG G A
The change happens in the CHROM value after using CrossMap. This change stops me from being able to combine all different vcf files for furthiur analysis. Any idea why this is happening or how to stop it?
• 1,943 views
•
link
written
by
raalsuwaidi •
0 answers
No answers yet.
Log in to answer this question.
More posts like this
-
More than 90% of variants were failed to match, using LiftoverVcf of Picard.
written by yoshidakoki •
-
Liftover - Picard and plink issues when performing liftover from CanFam4 to CanFam3
written by ipediez93 •
-
gatk LiftoverVCF finishes with no output VCF nor error.
written by jpablo •
-
VEST3 in wANNOVAR output
written by paolo •
-
Tutorial: Automated dbSNP lookup by rsID position, plus genome build liftover
written by Kevin Blighe
-
GATK BaseRecalibrator known-sites vcf file
written by Jordi •
-
Correct reference for Platinum Genomes?
written by Tails
-
Failed to liftover from hg38 to hg19
written by BAGeno
-
HOW EDIT VCF FILE COLUMNS
written by misbahabas •
-
VCF failed liftover, incorrect alternate allele
written by musaevdamir •
Does this appear for all positions of the chromosome, or just a few? It might be that these particular positions don't have a corresponding position in the target reference and are placed in some "placeholder" contig to be discarded. But I might be wrong, I didn't use CrossMap yet, I'm just planning to do liftover soon and I'm trying to read up on it.
thanks, i will check this out