Skip to main content

myChEMBL 20 has landed




We are very pleased to announce that the latest myChEMBL release, based on the ChEMBL 20 database, is now available to download. In addition to the ChEMBL upgrade, you will also find a number of changes and new features:


  • Updates in system and Python libraries, including the iPython notebook server
  • Upgrade in the web services (data and utils) to match the new functionality provided by the main ChEMBL ones
  • Current stable version of RDKit (2015.03)
  • Two brand new notebooks, namely an RDKit tutorial and a tutorial on SureChEMBL data mining, increasing the total number of notebooks to 14
  • Updates in several other iPython notebooks and the KNIME workflow, in order to take advantage of the new data, models and web services functionality
  • Several bug fixes
  • A CentOS 7 VM version, in addition to the existing Ubuntu 14.04 one
  • New virtualisation technologies, as explained in the section below


Lots of flavours

dipping case3.JPG

This new myChEMBL release is technical feature-rich, as we’ve decided to focus on providing a  variety of myChEMBL boxes and image formats via different distribution channels:

  1. New CentOS-based distribution - as requested by many users, we now provide a CentOS-based image, along with the existing Ubuntu one. CentOS is a Linux distribution that is focused on security and enterprise-class computing. It’s free and widely used in industry so no further introduction is needed. Our box is based on the latest stable version 7. One thing worth noting is that CentOS-based images are significantly smaller than Ubuntu ones.
  2. Different image formats - in addition to the standard vmdk images now available for Ubuntu and CentOS, we also provide other image formats. Although VMDK is an open format, it’s mainly used by proprietary software, such as vSphere. We decided to support free and open-source hypevisors as well, so this is why we are now publishing QEMU compatible qcow2 format. To help even more, we are providing a generic raw disk image dumps in img format which can then be converted to any other specific format to provide support for other virtualisation platforms. In fact, we used img files to generate qqow2 by running qemu-img convert -f raw -O qcow2 ubuntu.img ubuntu.qcow2
  3. Distribution channels - the traditional way to get myChEMBL image is to visit our FTP page. You can find there compressed images of our Ubuntu and CentOS myChEMBL distributions in different image formats. If you want to save time creating and configuring your Virtual Machine from scratch, you can use Vagrant instead of FTP. If you have Vagrant already installed, all you need to do is to open the terminal and type:
    vagrant init chembl/mychembl_20_ubuntu && vagrant up or:
    vagrant init chembl/mychembl_20_centos && vagrant up
    depending on the version you would like to use.
  4. An additional cool new feature is docker support but, since docker is a quite new technology, we would like to dedicate a separate blog post to this topic - so come back soon for exciting details.


Installation

There are now several different ways for installing myChEMBL:

  1. Follow the instructions in the INSTALL file on the ftpsite. This will import the myChEMBL VM into VirtualBox.
  2. Use Vagrant to install myChEMBL. See  point 3 in the section above.
  3. Bare metal - if you have a clean Ubuntu or CentOS box with root access and want to install myChEMBL software directly, then you may run:
    wget https://raw.githubusercontent.com/chembl/mychembl/master/bootstrap.sh && chmod +x bootstrap.sh && bash bootstrap.sh
    for Ubuntu or:
    wget https://github.com/chembl/mychembl/blob/master/bootstrap_centOS.sh && chmod +x bootstrap_centOS.sh && bash bootstrap_centOS.sh
    for CentOS.
  4. Instructions for Docker will be released #soon in a coming blog post.

As usual, the full codebase lives on GitHub


Publications and webinars

myChEMBL is reported and documented in two Open Access publications, namely here and here. In case you're new to myChEMBL, there is also a recorded webinar and its associated slides here


Future plans

The myChEMBL resource is an evolving system and we are always interested in new open source projects, tools and notebooks. Please get in touch if you have any suggestions or questions.



The myChEMBL team

Comments

Unknown said…
CentOS based myChembl is brilliant.. ! To bad i have just finished installing remus... :(

Unknown said…
Hey, why won't you use qcow2's compression instead of tar.gz? You wouldn't need to decompress it and save some more disk space. I had a blog post about using myCHEMBL in KVM about a year or so, and the compression worked like a charm. The initial image was roughly the same size as tarball, but functional. It will grow over time. I don't know how big is the performance hit, although for light usage there was no difference at all. For reference see http://maciek.wojcikowski.pl/2014/06/mychembl-running-on-kvm/
kott said…
Thank you Maciek, we will use qcow2 compression for myChEMBL 21.

Popular posts from this blog

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 29 Released

  We are pleased to announce the release of ChEMBL 29. This version of the database, prepared on 01/07/2021 contains: 2,703,543 compound records 2,105,464 compounds (of which 2,084,724 have mol files) 18,635,916 activities 1,383,553 assays 14,554 targets 81,544 documents Data can be downloaded from the ChEMBL FTP site:   https://ftp.ebi.ac.uk/pub/databases/chembl/ChEMBLdb/releases/chembl_29 .  Please see ChEMBL_29 release notes for full details of all changes in this release: https://ftp.ebi.ac.uk/pub/databases/chembl/ChEMBLdb/releases/chembl_29/chembl_29_release_notes.txt New Deposited Datasets EUbOPEN Chemogenomic Library (src_id = 55, ChEMBL Document IDs CHEMBL4649982-CHEMBL4649998): 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 synthesiz

Julia meets RDKit

Julia is a young programming language that is getting some traction in the scientific community. It is a dynamically typed, memory safe and high performance JIT compiled language that was designed to replace languages such as Matlab, R and Python. We've been keeping an an eye on it for a while but we were missing something... yes, RDKit! Fortunately, Greg very recently added the MinimalLib CFFI interface to the RDKit repertoire. This is nothing else than a C API that makes it very easy to call RDKit from almost any programming language. More information about the MinimalLib is available directly from the source . The existence of this MinimalLib CFFI interface meant that we no longer had an excuse to not give it a go! First, we added a BinaryBuilder recipe for building RDKit's MinimalLib into Julia's Yggdrasil repository (thanks Mosè for reviewing!). The recipe builds and automatically uploads the library to Julia's general package registry. The build currently targe

Identifying relevant compounds in patents

  As you may know, patents can be inherently noisy documents which can make it challenging to extract drug discovery information from them, such as the key targets or compounds being claimed. There are many reasons for this, ranging from deliberate obfuscation through to the long and detailed nature of the documents. For example, a typical small molecule patent may contain extensive background information relating to the target biology and disease area, chemical synthesis information, biological assay protocols and pharmacological measurements (which may refer to endogenous substances, existing therapies, reaction intermediates, reagents and reference compounds), in addition to description of the claimed compounds themselves.  The SureChEMBL system extracts this chemical information from patent documents through recognition of chemical names, conversion of images and extraction of attached files, and allows patents to be searched for chemical structures of interest. However, the curren

New Drug Warnings Browser

As mentioned in the announcement post of  ChEMBL 29 , a new Drug Warnings Browser has been created. This is an updated version of the entity browsers in ChEMBL ( Compounds , Targets , Activities , etc). It contains new features that will be tried out with the Drug Warnings and will be applied to the other entities gradually. The new features of the Drug Warnings Browser are described below. More visible buttons to link to other entities This functionality is already available in the old entity browsers, but the button to use it is not easily recognised. In the new version, the buttons are more visible. By using those buttons, users can see the related activities, compounds, drugs, mechanisms of action and drug indications to the drug warnings selected. The page will take users to the corresponding entity browser with the items related to the ones selected, or to all the items in the dataset if the user didn’t select any. Additionally, the process of creating the join query is no