---------------------------------------------------------------


gorGor4.trackDb.html : Differences exist between hgwbeta and hgw2 

(RR fields taken from public MySql server, not individual machine)

893,894c893,894
< evaSnp4 | and small insertions and deletions (indels)
< evaSnp4 | from the European Variation Archive
---
> evaSnp4 | and small insertions and deletions (indels) &mdash; collectively Simple
> evaSnp4 | Nucleotide Variants (SNVs) &mdash; from the European Variation Archive

1108,1109c1108,1109
< evaSnp5 | and small insertions and deletions (indels)
< evaSnp5 | from the European Variation Archive
---
> evaSnp5 | and small insertions and deletions (indels) &mdash; collectively Simple
> evaSnp5 | Nucleotide Variants (SNVs) &mdash; from the European Variation Archive

2039,2051d2038
< rmsk | 
< rmsk | <p>
< rmsk | When analyzing the data tables of this track, keep in mind that Repbase is not the same 
< rmsk | as the Repeatmasker sequence database and that the repeat names in the
< rmsk | Repeatmasker output are not the same as the sequence names in the Repeatmasker
< rmsk | database.  Concretely, you can find a name such as "L1PA4" in the Repeatmasker
< rmsk | output and this track, but there is not necessarily a single sequence "L1PA4"
< rmsk | in the Repeatmasker database. This is because Repeatmasker creates annotations
< rmsk | by joining matches to partial pieces of the database together so there is no
< rmsk | 1:1 relationship between its sequence database and the annotations. To learn
< rmsk | more, you can read the Repeatmasker paper, its source code or reach out to the
< rmsk | Repeatmasker authors, your local expert on transposable elements or us.
< rmsk | </p>