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

UniChem 2.0

UniChem new beta interface and web services We are excited to announce that our UniChem beta site will become the default one on the 11th of May. The new system will allow us to better maintain UniChem and to bring new functionality in a more sustainable way. The current interface and web services will still be reachable for a period of time at https://www.ebi.ac.uk/unichem/legacy . In addition to it, the most popular legacy REST endpoints will also remain implemented in the new web services: https://www.ebi.ac.uk/unichem/api/docs#/Legacy Some downtime is expected during the swap.  What's new? UniChem’s current API and web application is implemented with a framework version that’s not maintained and the cost of updating it surpasses the cost of rebuilding it. In order to improve stability, security, and support the implementation and fast delivery of new features, we have decided to revamp our user-facing systems using the latest version of widely used and maintained frameworks, i

A python client for accessing ChEMBL web services

Motivation The CheMBL Web Services provide simple reliable programmatic access to the data stored in ChEMBL database. RESTful API approaches are quite easy to master in most languages but still require writing a few lines of code. Additionally, it can be a challenging task to write a nontrivial application using REST without any examples. These factors were the motivation for us to write a small client library for accessing web services from Python. Why Python? We choose this language because Python has become extremely popular (and still growing in use) in scientific applications; there are several Open Source chemical toolkits available in this language, and so the wealth of ChEMBL resources and functionality of those toolkits can be easily combined. Moreover, Python is a very web-friendly language and we wanted to show how easy complex resource acquisition can be expressed in Python. Reinventing the wheel? There are already some libraries providing access to ChEMBL d

LSH-based similarity search in MongoDB is faster than postgres cartridge.

TL;DR: In his excellent blog post , Matt Swain described the implementation of compound similarity searches in MongoDB . Unfortunately, Matt's approach had suboptimal ( polynomial ) time complexity with respect to decreasing similarity thresholds, which renders unsuitable for production environments. In this article, we improve on the method by enhancing it with Locality Sensitive Hashing algorithm, which significantly reduces query time and outperforms RDKit PostgreSQL cartridge . myChEMBL 21 - NoSQL edition    Given that NoSQL technologies applied to computational chemistry and cheminformatics are gaining traction and popularity, we decided to include a taster in future myChEMBL releases. Two especially appealing technologies are Neo4j and MongoDB . The former is a graph database and the latter is a BSON document storage. We would like to provide IPython notebook -based tutorials explaining how to use this software to deal with common cheminformatics p

ChEMBL 30 released

  We are pleased to announce the release of ChEMBL 30. This version of the database, prepared on 22/02/2022 contains: 2,786,911 compound records 2,157,379 compounds (of which 2,136,187 have mol files) 19,286,751 activities 1,458,215 assays 14,855 targets 84,092 documents Data can be downloaded from the ChEMBL FTP site: https://ftp.ebi.ac.uk/pub/databases/chembl/ChEMBLdb/releases/chembl_30/ Please see ChEMBL_30 release notes for full details of all changes in this release:  https://ftp.ebi.ac.uk/pub/databases/chembl/ChEMBLdb/releases/chembl_30/chembl_30_release_notes.txt New Deposited Datasets EUbOPEN Chemogenomic Library (src_id = 55, ChEMBL Document ID CHEMBL4689842):   The EUbOPEN consortium is an Innovative Medicines Initiative (IMI) funded project to enable and unlock biology in the open. The aims of the project are to assemble an open access chemogenomic library comprising about 5,000 well annotated compounds covering roughly 1,000 different proteins, to synthesize at least

Multi-task neural network on ChEMBL with PyTorch 1.0 and RDKit

  Update: KNIME protocol with the model available thanks to Greg Landrum. Update: New code to train the model and ONNX exported trained models available in github . The use and application of multi-task neural networks is growing rapidly in cheminformatics and drug discovery. Examples can be found in the following publications: - Deep Learning as an Opportunity in VirtualScreening - Massively Multitask Networks for Drug Discovery - Beyond the hype: deep neural networks outperform established methods using a ChEMBL bioactivity benchmark set But what is a multi-task neural network? In short, it's a kind of neural network architecture that can optimise multiple classification/regression problems at the same time while taking advantage of their shared description. This blogpost gives a great overview of their architecture. All networks in references above implement the hard parameter sharing approach. So, having a set of activities relating targets and molecules we can tra