Thanks for your reply, I get it now.
• 0 views
•
link
written
by
michaelrichardlei •
Why genome reference (genome assembly) name is so annoying?
Everytime I need to remind me that hg38 is GRCh38, hg19 is GRCh37, so hg38 is the new version of hg19.
Why the UCSC didn't name it hg20?
• 1,647 views
•
link
updated
by
Pierre Lindenbaum
•
written
by
michaelrichardlei •
•
written
by
michaelrichardlei •
1 answer
http://genome.ucsc.edu/goldenPath/newsarch.html
Starting with this release, the UCSC Genome Browser version numbers for human assemblies will match those of the GRC to minimize version confusion. Hence, the GRCh38 assembly is referred to as hg38 in Genome Browser datasets and documentation.
• 0 views
•
link
written
by
Pierre Lindenbaum
please validate this answer using the green tick on the left.
• 0 views
•
link
written
by
Pierre Lindenbaum
Log in to answer this question.
More posts like this
-
Liftover GRCh37 to hg38 1kg/GATK.
written by ManuelDB
-
CAAD score for SNPs vcf file
written by Eliza •
-
What aren't hg19-hg38 liftOver chains symmetrical?
written by d-cameron
-
UCSC liftover
written by jhy •
-
Why does the iGenomes have decoy for only GRCh38.
written by Apprentice
-
Reference Consortium (HRC) in GRch38/hg38
written by enho •
-
What should you do if you don't know the wig file is based on GRCH37 or GRCH38?
written by Shicheng Guo
-
How to find rs number of SNP when UCSC data base position known in reverse strand sequence
written by Nawaj Shaikh •
-
Map ensembl gene id form hg38 in hg19
written by Tanvir Ahamed
-
new regions in GRCh38
written by skanterakis
The nice thing about standards is that there are so many of them to choose from. —Andrew S. Tanenbaum