Skip to main content

Random Notes on Open Drug Discovery/Data Sharing: Part 1

There are some fantastic initiatives in Open Drug Discovery going on at the moment. I for one, are convinced that we are on the cusp of a large structural change in drug discovery, and like at the beginning of all revolutions, the future is not clear, and we all a little bit excited and nervous at the same time. One of the commonly quoted benefits of an Open strategy is that it can avoid duplication, and if you avoid duplication, it means that you get to the goal, faster and cheaper (since other researchers can explore alternative approaches), and there is no repetition. There, you've just read it, and it's quite seductive isn't it?

I've never quite bought this "avoid duplication" argument for the following three reasons. (I should declare my political/philosophical hand here, I have a very deep rooted empathy with the concept of The Free Market. Not the goofy, fudged form that we've had in Western Economies for some time - but that really is a different story, for another time).

1) Scientists are not perfect and they mess things up now and then. The "no duplication" strategy places a lot of weight on the capabilities of a single group, who may not follow the best decision making, have the best approach to data analysis/design etc. There is a lot of discussion at the moment in the literature of the non-repeatability of key pharmacology data, to not have several parallel attempts at a problem seems a little rash given the probably high likelihood of individual failure. If an individual group has a likelihood of 0.6 of getting something done within a given time and given funding. Two groups (with the same likelihood of success/failure) in parallel have a probability of getting it done of 0.84. Simples.

2) Competition is well established to be one of the major drivers of rapid completion in almost all endeavours of life; if you have someone breathing down your neck, potentially scooping you on a paper, you think in a different way, and tend to stay focussed on the task in hand. Given a finite time to complete a piece of work with preplanned and coordinated deliverables, the work miraculously fills the time and funding available.

3) Who will take the decisions over non-duplication? Effectively saying you will not work on this compound series, and another group will, and will people abide with the decisions? We all know that grant committees are useless (unless we are on them of course), and without a lot of process transparency, things could rapidly descend into slow chaos and confusion.

However, I think the arguments for rapid data sharing are very very strong, primarily because they increase liquidity and transparency in the market, and allow market participants to take more rational decisions on the allocation of their resources (individual labs and funders). For me this is the biggest single reason for data sharing (i.e. it actually increases competition, not decreases it). The Free Market of Knowledge in Drug Discovery will drive participants to their best composite roles, based on their abilities.


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 . In addition to it, the most popular legacy REST endpoints will also remain implemented in the new web services: 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

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: Please see ChEMBL_30 release notes for full details of all changes in this release: 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

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

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