-
Notifications
You must be signed in to change notification settings - Fork 10
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
Retrieving older annotations while matching API version #139
Comments
Hi Roberto! I assume you installed the Ensembl perl API using github (i.e. from https://github.com/Ensembl/ensembl)? If so, you need to check out the release 74 of the source code:
Then it should work. The perl script has a first check . Since installation of the Ensembl Perl API and all other required perl libraries is quite tricky (at least in my opinion) it could be that you run into other problems later. Just let me know for which species you need annotations and I'll create them for you. And thanks for the bug in the vignette! |
Actually @rcastelo , in which vignette did you find the |
Hi Johannes, Thanks for the hint, it looks like I have been able to correct that problem, but now I've stumbled into this other error:
which looks like there is some stale data in the mysql database that precludes the pipeline going forward. Do you know how can I clean up and have fresh start? The vignette where I found the typo was the one from the AHEnsDbs annotation package, concretely this one. |
Hi again, ok, so I figured out that I can simply enter in the MySQL database and remove that stale database
In principle the user 'readonly' has password 'readonly' and I can enter into the MySQL server with |
Can you please check if your database contains any data? To me it seems that the data import failed. So, maybe connect to the database and do a quick
but I guess that the table will be empty. According to this error message:
restoring a mysql database from txt files is disabled for
It depends a bit on your system, but for me on linux I had to add this to /etc/my.cnf.d/server.cnf (below the The other thing I don't quite undestand is this line:
so, connection fails because it does not recognize the |
Maybe specifying the port you're running mysql could help: try adding And again, if you don't want to spend that much time fiddling around with the rather tricky mysql/perl/Ensembl API setup you can also just tell me for what species and releases you want to have |
Thanks, the suggestion about the port worked (the port in my case was
This is the configuration file with the added line
and now complains about another table called |
Maybe try to restart the mysql server. That might be needed to ensure the
Note that also the client needs to have
Maybe also have a look at the mysql documentation if the error persists. I hope it does not have to do something with incompatible mysql server versions - note that the Ensembl Perl API requires a quite old Perl and MySQL. On my system (macOS) I'm using mariadb 10.8.3 |
Hi, restarting the mysql server did the job, however, adding
to the mysql configuration file at
so I simply removed this bit and the pipeline went forward till this next error:
It seems that it has started processing some tables ( |
hm, this is strange. Did you remove the old
To me it seems that something happens at the second step and that not all tables are created (something incompatible with your local mysql server in line 21 of the sql file?). You could check which tables were created by connecting to your database
and then list all tables
when there are only few tables (e.g. just the alt_allele* tables) then there might be an error creating all required tables... |
I think I'm almost there!! :) I do remove the old
so the question is why does it choke at these errors:
I recalled somehow your words above where you said "I hope it does not have to do something with incompatible mysql server versions - note that the Ensembl Perl API requires a quite old Perl and MySQL. On my system (macOS) I'm using mariadb 10.8.3". So, I decided to uninstall MySQL completely and installed, via HomeBrew (I'm also on macOS), MariaDB and got actually the same version you mention (10.8.3). Next to
so, I think I'm very close to make it. Please let me know if the Perl error tells you anything. |
- Avoid retrieving stable_id_version for older Ensembl releases (issue #139).
Oh - indeed, that might be something I hadn't anticipated - could be that some of the variables I'm extracting are not available or defined in older Ensembl version. I'll update the perl code to avoid calling that method for older Ensembl releases. Please install the package again from github ( |
Hi, with this new update of the
By the way, do you know of any website where one can see the different number of human Ensembl genes per release version of the Ensembl database? (this would allow one to anticipate what version of Ensembl was used to generate a table of counts based on Ensembl gene identifiers, as long as the number of rows/ensembl genes is specific to an Ensembl version). Thanks again! |
Wow! Congratulations!!! Regarding your question - no, unfortunately I don't know if there exists such a page. Worst case, get EnsDb databases for each Ensembl release from AnnotationHub and get the gene counts from there ;) |
Hi,
I'm tryting to build an EnsDb annotation package for an old version of the human annotations (74) for a purpose of trying to fully reproduce some result, but I'm encountering the following error:
I've installed the Ensembl Perl API and mysql with a 'readonly' user with password 'readonly' and in principle everything is in place, but I don't know to get around this mismatch between the version of Ensembl human annotations that I want to fetch (74) and the fact that the current Ensembl API version is 107. I already tried to set an environment variable
ENS=74
, but didn't make any difference. Any hint will be appreciated.By the way, in the vignette from where I read about using this function
createEnsDbForSpecies()
, the command to fetch the code for that function in the vignette is:while it should be:
The text was updated successfully, but these errors were encountered: