Skip to main content

ChEMBL PostgreSQL



With the aim of providing more options to access the ChEMBL database, a PostgreSQL version of the most recent ChEMBL release is now available on the ChEMBL FTP site, (thanks to the Ora2Pg project for making the conversion process relatively painless). 

The main goal of this project is make it easier for users to integrate the chemical data in the ChEMBL database with freely available chemical cartridges, such as the excellent RDKit and Bingo. Now that we have the PostgreSQL version of the database available, we are in the process of benchmarking the aforementioned chemical cartridges - we will report back soon the results of the benchmarking exercises we are undertaking. We are also looking to build and release a virtual machine, which will come preloaded with ChEMBL, PostgreSQL, RDKit and/or Bingo. When we have more details on this we will let you know.

Right now everyone has the opportunity to download and install the PostgreSQL version of the ChEMBL database and optionally install a chemical cartridge. We hope this will help as many projects as possible and any comments or feedback will be very much appreciated. Enjoy it :)

(You can download the ChEMBL_14 PostgreSQL here, the tarball also comes with some basic install instructions, but does assume you have a PostgreSQL instance up and running).

Comments

greg landrum said…
Nice!

Let me know if there's anything I can do to help with the benchmarking.
Unknown said…
oh yes, you'll hear from us soon
:)
greg landrum said…
Any chance you would be willing/able to share logs of substructures that people have executed against ChEMBL?

That kind of real-world (and public) data would be very helpful for optimizing SSS fingerprints.
jpo said…
Greg - we've been asked this a lot of times, and quite simply it's against our terms of use of the resources here at the EBI. The queries are confidential, and we have written the application, so anything that may be considered confidential is cleared from any caches as soon as is practicable, consistent with reasonable performance, or is only stored client side.

In summary, we don't store the queries.

There have been a few apocryphal cases where in the field of drug discovery, people have gone and mined or shared the queries of their web resources, and it is quite a sad tale......
Kyle Kinney said…
Awesome, this is almost exactly what I needed - I was not looking forward to trying to convert this into postgresql myself. There's only one little issue - I'm running postgresql 9.0, and this is for postgresql 9.1. Any idea what kinds of compatibility issues am I likely to run into? The only noticeable failure I saw on loading was the failure of the CREATE EXTENSION plpgsql, and I may or may not be able to substitute CREATE LANGUAGE there. Not sure how much plpgsql has changed between versions, other than being an extension now.
Push comes to shove, I can migrate, but if it's a matter of changing a couple lines at the top, I'd rather avoid it.

Popular posts from this blog

ChEMBL_27 SARS-CoV-2 release

The COVID-19 pandemic has resulted in an unprecedented effort across the global scientific community. Drug discovery groups are contributing in several ways, including the screening of compounds to identify those with potential anti-SARS-CoV-2 activity. When the compounds being assayed are marketed drugs or compounds in clinical development then this may identify potential repurposing opportunities (though there are many other factors to consider including safety and PK/PD considerations; see for example https://www.medrxiv.org/content/10.1101/2020.04.16.20068379v1.full.pdf+html). The results from such compound screening can also help inform and drive our understanding of the complex interplay between virus and host at different stages of infection.
Several large-scale drug screening studies have now been described and made available as pre-prints or as peer-reviewed publications. The ChEMBL team has been following these developments with significant interest, and as a contribution t…

RDKit, C++ and Jupyter Notebook

Fancy playing with RDKit C++ API without needing to set up a C++ project and compile it? But wait... isn't C++ a compiled programming language? How this can be even possible?

Thanks to Cling (CERN's C++ interpreter) and xeus-cling jupyter kernel is possible to use C++ as an intepreted language inside a jupyter notebook!

We prepared a simple notebook showing few examples of RDKit functionalities and a docker image in case you want to run it.

With the single requirement of docker being installed in your computer you'll be able to easily run the examples following the three steps below:
docker pull eloyfelix/rdkit_jupyter_clingdocker run -d -p 9999:9999 eloyfelix/rdkit_jupyter_clingopen http://localhost:9999/notebooks/rdkit_cling.ipynb in a browser


FPSim2, a simple Python3 molecular similarity tool

FPSim2 is a new tool for fast similarity search on big compound datasets (>100 million) being developed at ChEMBL. We started developing it as we needed a Python3 library able to run either in memory or out-of-core fast similarity searches on such dataset sizes.

It's written in Python/Cython and features:
A fast population count algorithm (builtin-popcnt-unrolled) from https://github.com/WojciechMula/sse-popcount using SIMD instructions.Bounds for sub-linear speed-ups from 10.1021/ci600358fA compressed file format with optimised read speed based in PyTables and BLOSCUse of multiple cores in a single search In memory and on disk search modesSimple and easy to use
Source code is available on github and Conda packages are also available for either mac or linux. To install it type:

conda install rdkit -c rdkitconda install fpsim2 -c efelix
Try it with docker (much better performance than binder):

    docker pull eloyfelix/fpsim2    docker run -p 9999:9999 eloyfelix/fpsim2    open htt…

2019 and ChEMBL – News, jobs and birthdays

Happy New Year from the ChEMBL Group to all our users and collaborators. 
Firstly, do you want a new challenge in 2019?  If so, we have a position for a bioinformatician in the ChEMBL Team to develop pipelines for identifying links between therapeutic targets, drugs and diseases.  You will be based in the ChEMBL team but also work in collaboration with the exciting Open Targets initiative.  More details can be found here(closing date 24thJanuary). 
In case you missed it, we published a paper at the end of last on the latest developments of the ChEMBL database “ChEMBL: towards direct deposition of bioassay data”. You can read it here.  Highlights include bioactivity data from patents, human pharmacokinetic data from prescribing information, deposited data from neglected disease screening and data from the IMI funded K4DD project.  We have also added a lot of new annotations on the therapeutic targets and indications for clinical candidates and marketed drugs to ChEMBL.  Importantly we ha…

ChEMBL 25 and new web interface released

We are pleased to announce the release of ChEMBL 25 and our new web interface. This version of the database, prepared on 10/12/2018 contains:

2,335,417 compound records1,879,206 compounds (of which 1,870,461 have mol files)15,504,603 activities1,125,387 assays12,482 targets72,271 documents

Data can be downloaded from the ChEMBL ftp site: ftp://ftp.ebi.ac.uk/pub/databases/chembl/ChEMBLdb/releases/chembl_25

Please see ChEMBL_25 release notes for full details of all changes in this release: ftp://ftp.ebi.ac.uk/pub/databases/chembl/ChEMBLdb/releases/chembl_25/chembl_25_release_notes.txt


DATA CHANGES SINCE THE LAST RELEASE

# Deposited Data Sets:

Kuster Lab Chemical Proteomics Drug Profiling (src_id = 48, Document ChEMBL_ID = CHEMBL3991601):
Data have been included from the publication: The target landscape of clinical kinase drugs. Klaeger S, Heinzlmeir S and Wilhelm M et al (2017), Science, 358-6367 (https://doi.org/10.1126/science.aan4368)

# In Vivo Assay Classification:

A classification…