Skip to main content

New ChEMBL ligand-based target predictions docker image available


Resultado de imagen de zoltar fortune


One year ago we published a new version of our target prediction models and since then we've been working on its implementation for the upcoming ChEMBL 26 release.

What did we do?

First of all we re-trained the models with the LightGBM library instead of using scikit-learn. By doing this and tuning a bit the parameters our prediction timing improved by 2 orders of magnitude while keeping comparable prediction power. Having quicker models allowed us to easily implement a simple web service providing real time predictions.

Since we are currently migration to a more sustainable Kubernetes infrastructure it made sense to us to directly write the small target prediction web service as a cloud native app. We then decided to give OpenFaaS a try as a platform to deploy machine learning models.

OpenFaaS is a framework for building serverless functions with Docker and Kubernetes. It provides templates for deploying functions as REST endpoints in many different programming languages (Python, Node, Java, Ruby, go...).

Our target predicitons OpenFaaS function source code is now available in our github repository. A Docker image with ready to use ChEMBL 25 trained models is also available here.

Does this mean that you won't be able to use the models without an Kubernetes/OpenFaaS installation? No way! It is also easy to start an instance in your local machine:

docker run -p 8080:8080 chembl/mcp:25
# in a different shell
curl -X POST -H 'Accept: */*' -H 'Content-Type: application/json' -d '{"smiles": "CC(=O)Oc1ccccc1C(=O)O"}' http://127.0.0.1:8080

Bear in mind that the service needs to load the models into memory, so it may take few minutes until it returns predictions. The predictions returned by the service are the ones for the models with CCR ((sensitivity + specificity) / 2) >= 0.85

Comments

Chris said…
Hi, Tried to use Docker

docker run -p 8080:8080 chembl/mcp
Forking - python [index.py]
2020/02/06 10:54:02 Started logging stderr from function.
2020/02/06 10:54:02 Started logging stdout from function.
2020/02/06 10:54:02 OperationalMode: http
2020/02/06 10:54:02 Timeouts: read: 10s, write: 10s hard: 10s.
2020/02/06 10:54:02 Listening on port: 8080
2020/02/06 10:54:02 Writing lock-file to: /tmp/.lock
2020/02/06 10:54:02 Metrics listening on port: 8081
2020/02/06 10:54:31 Upstream HTTP request error: Post http://127.0.0.1:5000/: dial tcp 127.0.0.1:5000: connect: connection refused
2020/02/06 10:54:46 Forked function has terminated: signal: killed

when I try this in another Terminal window

curl -X POST -H 'Accept: */*' -H 'Content-Type: application/json' -d '{"smiles": "CC(=O)Oc1ccccc1C(=O)O"}' http://127.0.0.1:8080
Eloy said…
Hi Chris,

Are you using Docker on Windows or Mac?
It's default config (Docker on Windows and Mac actually runs inside a tiny VM) allows it only to use 2GB of RAM and it looks like it's killing the container process because Docker runs out of memory when loading the models.
You'll need to change Docker config to allow it to use 8GB of system memory.

Kind regards,
Eloy

Popular posts from this blog

Improvements in SureChEMBL's chemistry search and adoption of RDKit

    Dear SureChEMBL users, If you frequently rely on our "chemistry search" feature, today brings great news! We’ve recently implemented a major update that makes your search experience faster than ever. What's New? Last week, we upgraded our structure search engine by aligning it with the core code base used in ChEMBL . This update allows SureChEMBL to leverage our FPSim2 Python package , returning results in approximately one second. The similarity search relies on 256-bit RDKit -calculated ECFP4 fingerprints, and a single instance requires approximately 1 GB of RAM to run. SureChEMBL’s FPSim2 file is not currently available for download, but we are considering generating it periodicaly and have created it once for you to try in Google Colab ! For substructure searches, we now also use an RDKit -based solution via SubstructLibrary , which returns results several times faster than our previous implementation. Additionally, structure search results are now sorted by

Improved querying for SureChEMBL

    Dear SureChEMBL users, Earlier this year we ran a survey to identify what you, the users, would like to see next in SureChEMBL. Thank you for offering your feedback! This gave us the opportunity to have some interesting discussions both internally and externally. While we can't publicly reveal precisely our plans for the coming months (everything will be delivered at the right time), we can at least say that improving the compound structure extraction quality is a priority. Unfortunately, the change won't happen overnight as reprocessing 167 millions patents takes a while. However, the good news is that the new generation of optical chemical structure recognition shows good performance, even for patent images! We hope we can share our results with you soon. So in the meantime, what are we doing? You may have noticed a few changes on the SureChEMBL main page. No more "Beta" flag since we consider the system to be stable enough (it does not mean that you will never

ChEMBL brings drug bioactivity data to the Protein Data Bank in Europe

In the quest to develop new drugs, understanding the 3D structure of molecules is crucial. Resources like the Protein Data Bank in Europe (PDBe) and the Cambridge Structural Database (CSD) provide these 3D blueprints for many biological molecules. However, researchers also need to know how these molecules interact with their biological target – their bioactivity. ChEMBL is a treasure trove of bioactivity data for countless drug-like molecules. It tells us how strongly a molecule binds to a target, how it affects a biological process, and even how it might be metabolized. But here's the catch: while ChEMBL provides extensive information on a molecule's activity and cross references to other data sources, it doesn't always tell us if a 3D structure is available for a specific drug-target complex. This can be a roadblock for researchers who need that structural information to design effective drugs. Therefore, connecting ChEMBL data with resources like PDBe and CSD is essen

ChEMBL 34 is out!

We are delighted to announce the release of ChEMBL 34, which includes a full update to drug and clinical candidate drug data. This version of the database, prepared on 28/03/2024 contains:         2,431,025 compounds (of which 2,409,270 have mol files)         3,106,257 compound records (non-unique compounds)         20,772,701 activities         1,644,390 assays         15,598 targets         89,892 documents Data can be downloaded from the ChEMBL FTP site:  https://ftp.ebi.ac.uk/pub/databases/chembl/ChEMBLdb/releases/chembl_34/ Please see ChEMBL_34 release notes for full details of all changes in this release:  https://ftp.ebi.ac.uk/pub/databases/chembl/ChEMBLdb/releases/chembl_34/chembl_34_release_notes.txt New Data Sources European Medicines Agency (src_id = 66): European Medicines Agency's data correspond to EMA drugs prior to 20 January 2023 (excluding vaccines). 71 out of the 882 newly added EMA drugs are only authorised by EMA, rather than from other regulatory bodies e.g.

In search of the perfect assay description

Credit: Science biotech, CC BY-SA 4.0 Assays des cribe the experimental set-up when testing the activity of drug-like compounds against biological targets; they provide useful context for researchers interested in drug-target relationships. Ver sion 33 of ChEMBL contains 1.6 million diverse assays spanning ADMET, physicochemical, binding, functional and toxicity experiments. A set of well-defined and structured assay descriptions would be valuable for the drug discovery community, particularly for text mining and NLP projects. These would also support ChEMBL's ongoing efforts towards an  in vitro  assay classification. This Blog post will consider the features of the 'perfect' assay description and provide a guide for depositors on the submission of high quality data. ChEMBL's assays are typically structured with the overall aim, target, and method .  The ideal assay description is succinct but contains all the necessary information for easy interpretation by database u