Closed ACastanza closed 8 months ago
I think https://github.com/related-sciences/ensembl-genes/issues/22 is the underlying issue here. Release 110 had an unsolvable issue:
It is not possible to link an alternate region with the corresponding primary assembly region in the release 110 database. This information will be present in the
dna_align_feature
table in the release 111 database.
But now that 111 is released, I'll look to update the SQL queries and logic for the new database schema. Thanks for the reminder!
Any idea when you might be able to get this fix in? We make use of this history file and I'd like to use the current version instead of carrying forward the old one again.
Noting 111 release information:
Any idea when you might be able to get this fix in?
Let me do a little work now to assess the feasibility.
Unblocked by https://github.com/related-sciences/ensembl-genes/commit/eb7c779369d215e08761e4b509eb8c32655aefc5 and rerunning exports in this action.
Okay 111 is working with the latest human output in 8c4decd75705b0764e30e8fdd29a2aea5cf0db3f.
The two source code commits that change methodology are:
We've switched to a more aggressive method for detection allele groups. There will no longer be any representative genes with duplicate symbols.
@ACastanza will let you close the issue if the new data looks good for you and your application.
Looks good to me, thanks for getting this fix in, much appreciated!