Skip to main content

Data checks

 


ChEMBL contains a broad range of binding, functional and ADMET type assays in formats ranging from in vitro single protein assays to anti proliferative cell-based assays. Some variation is expected, even for very similar assays, since these are often performed by different groups and institutes. ChEMBL includes references for all bioactivity values so that full assay details can be reviewed if needed, however there are a number of other data checks that can be used to identify potentially problematic results.

1) Data validity comments:

The data validity column was first included in ChEMBL v15 and flags activities with potential validity issues such as a non-standard unit for type or activities outside of the expected range. Users can review flagged activities and decide how these should be handled. The data validity column can be viewed on the interface (click 'Show/Hide columns' and select 'data validity comments') and can be found in the activities table in the full database.

* Acceptable ranges/units for standard_types are provided in the ACTIVITY_STDS_LOOKUP table. An exception is made for certain fragment-based activities (MW <= 350) where the data validity comment is not applied.

2) Confidence scores:

The confidence scores reflect both the target type and the confidence that the mapped target is correct (e.g. score 0 = no target assigned, score 9 = direct single protein target assigned). In cases where target protein accessions were unavailable during initial mapping, homologues from different species/strains have sometimes been assigned with lower confidence scores. Curation is ongoing and confidence scores may change between releases as additional assays are mapped (or re-mapped) to targets. The confidence scores can be viewed on the interface and are found in the assays table in the database.


3) Activity comments:

Activity comments capture the author or depositor’s overall activity conclusions and may take into account counter screens, curve fitting etc. It may be worth reviewing the activity comments to identify cases where apparently potent compounds have been deemed inactive by depositors. For further details on activity comments, see our previous Blog post. The activity comments can be viewed on the interface and are available in the activities table of the database.

4) Potential duplicates:

Bioactivity data is extracted from seven core journals and this may include secondary citations. Potential duplicates are flagged when identical compound, target, activity, type and unit values are reported. The potential duplicates field is available on the interface and is found in the activities table of the database.

5) Variants:

Protein variation can change the affinity of drugs for targets. On the interface, variant proteins are recorded in the assay descriptions which can be used to check whether activities correspond to variant or 'wild-type' targets. The variant sequences table was added to the database in version 22 and is linked to the assays table through the variant ID. The variant ID can be used to include or exclude variants from assay results. Curation is underway to annotate additional variants from historical assays (more on this to follow).

Hopefully this provides an idea of some of the available data checks. Questions? Please get in touch on the Helpdesk or have a look through our training materials and FAQs.

Data checks using Imatinib as an example:










Comments

Popular posts from this blog

SureChEMBL Available Now

Followers of the ChEMBL group's activities and this blog will be aware of our involvement in the migration of the previously commercially available SureChem chemistry patent system, to a new, free-for-all system, known as SureChEMBL. Today we are very pleased to announce that the migration process is complete and the SureChEMBL website is now online. SureChEMBL provides the research community with the ability to search the patent literature using Lucene-based keyword queries and, much more importantly, chemistry-based queries. If you are not familiar with SureChEMBL, we recommend you review the content of these earlier blogposts here and here . SureChEMBL is a live system, which is continuously extracting chemical entities from the patent literature. The time it takes for a new chemical in the patent literature to become searchable in the SureChEMBL system is 1-2 days (WO patents can sometimes take a bit longer due to an additional reprocessing step). At time of writi

New SureChEMBL announcement

(Generated with DALL-E 3 ∙ 30 October 2023 at 1:48 pm) We have some very exciting news to report: the new SureChEMBL is now available! Hooray! What is SureChEMBL, you may ask. Good question! In our portfolio of chemical biology services, alongside our established database of bioactivity data for drug-like molecules ChEMBL , our dictionary of annotated small molecule entities ChEBI , and our compound cross-referencing system UniChem , we also deliver a database of annotated patents! Almost 10 years ago , EMBL-EBI acquired the SureChem system of chemically annotated patents and made this freely accessible in the public domain as SureChEMBL. Since then, our team has continued to maintain and deliver SureChEMBL. However, this has become increasingly challenging due to the complexities of the underlying codebase. We were awarded a Wellcome Trust grant in 2021 to completely overhaul SureChEMBL, with a new UI, backend infrastructure, and new f

ChEMBL & SureChEMBL anniversary symposium

  In 2024 we celebrate the 15th anniversary of the first public release of the ChEMBL database as well as the 10th anniversary of SureChEMBL. To recognise this important landmark we are organising a two-day symposium to celebrate the work achieved by ChEMBL and SureChEMBL, and look forward to its future.   Save the date for the ChEMBL 15 Year Symposium October 1-2, 2024     Day one will consist of four workshops, a basic ChEMBL drug design workshop; an advanced ChEMBL workshop (EUbOPEN community workshop); a ChEMBL data deposition workshop; and a SureChEMBL workshop. Day two will consist of a series of talks from invited speakers, a few poster flash talks, a local nature walk, as well as celebratory cake. During the breaks, the poster session will be a great opportunity to catch up with other users and collaborators of the ChEMBL resources and chat to colleagues, co-workers and others to find out more about how the database is being used. Lunch and refreshments will be pro

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.

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_cling docker run -d -p 9999:9999 eloyfelix/rdkit_jupyter_cling open  http://localhost:9999/notebooks/rdkit_cling.ipynb  in a browser