Hi Sabry,

The build is 37.1 which doesn't contain any patches. This is indicated
on this page: http://www.ncbi.nlm.nih.gov/genome/guide/human/release_notes.html.
The link that you provided
(http://www.ncbi.nlm.nih.gov/projects/genome/assembly/grc/human/data/?build=37)
specifies the assemblies by patches and not by build versions.

This means that:

Build 37.1 contains the GRCh37 reference assembly

Build 37.2 contains the GRCh37.p2 reference assembly

Build 37.3 contains the GRCh37.p5 reference assembly


The GRC Patch Release Track on hg19 may be of interest to you. Here is
a link to that track:

http://genome.ucsc.edu/cgi-bin/hgTrackUi?db=hg19&c=chr21&g=altSeqComposite


I hope that this clarifies the confusion. If you have further
questions, please contact the mailing list: [email protected].

Vanessa Kirkup Swing
UCSC Genome Bioinformatics





---------- Forwarded message ----------
From: Sabry Razick <[email protected]>
Date: Tue, Mar 6, 2012 at 8:34 AM
Subject: [Genome] hg19 GRCh37 or GRCh37.1
To: [email protected]


Hello,
 Which version of the GRCh is identical to hg19  (GRCh37 or GRCh37.1) ? is
the identity 100% (is it the same thing with different names)?

Clarification:
You documentation and the 2011 publication, clearly states that it is
GRCh37, but in some FAQs I see that GRCh37.1 is mentioned instead and the
statistics link is to Build 37.1 (on
http://genome.ucsc.edu/cgi-bin/hgGateway). May be it is used intergangbly
as it does not really matter whether GRCh37 or GRCh37.1 as they are very
similar. But I see that there a difference of 2 million bases between these
two versions,
(according to
http://www.ncbi.nlm.nih.gov/projects/genome/assembly/grc/human/data/index.shtml
).

Regards and thank you in advance,

Sabry Razick.
_______________________________________________
Genome maillist  -  [email protected]
https://lists.soe.ucsc.edu/mailman/listinfo/genome

_______________________________________________
Genome maillist  -  [email protected]
https://lists.soe.ucsc.edu/mailman/listinfo/genome

Reply via email to