-
Notifications
You must be signed in to change notification settings - Fork 92
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
What to do about shifting ensembl build? #1521
Comments
It's probably worth trying the build update to 110, like as not nothing will have changed for most species. You'll see with the diff it generates, whether there's anything to worry about. The main reason for including the check was to make sure stuff doesn't change without people realising. |
What do you mean "trying the build update"? Do you mean just run |
That won't hit the annotations, though... |
I don't know if it helps, but Ensembl has archives. 103 is found here: http://feb2021.archive.ensembl.org/index.html Would it be possible to redo the Gorilla PR for 103? |
Yeah, that's how it was intended. Occasionally update to the new build, and letting git tell you whether anything important has changed. Running |
@andrewkern will give updating to 104 a shot |
ugh running this returns an HTTP error because Ensembl has changed the designation of
I will submit a patch along with the update |
OMG |
...oh boy a whole mess of these have moved... |
okay i've submitted a PR at #1536 |
Looks like many of the builds changed. In most cases it's just chromosome names and synonyms. In these cases, we'll need to make sure that the chrom names we use in the that the chrom-averaged recombination rate and mutation rate lists work with the new names. Looks like they will, but I'm not 100% sure. A more serious problem occurs when the chromosome lengths actually change, as happened e.g. in CanFam. New chromosome lengths can conflict with existing recombination maps, so we definitely don't want to automatically update them. |
Over in #1517, @ChristianHuber has got a PR for Gorilla (yay!). However, it's failing because the autogenerated file
stdpopsim/catalog/ensembl_info.py
has been changed:and in
tests/test_ensembl.py
, we haveSo, looks like ensembl has moved along, and we need to either
I suspect the reason for this is so that we can cite exactly where the info is coming from, but I am not on top of all the ramifications.
The text was updated successfully, but these errors were encountered: