Compiling inchi-1 to JavaScript

There are more and more software libraries being ported to JavaScript. The best example is JavaScript/HTML5 Citadel demo of the Unreal Engine. So why not to try with some chemical stuff? One of the most important chemical software libraries is IUPAC InChi. It's also extremely hard to reimplement as it's written in low-level, functional-style C. On the other hand it's just a few headers and source files, without any dependencies so it's a perfect use case for Emscripten.

Emscripten 'is an LLVM-to-JavaScript compiler'. It can be used as a drop-in replacement for standard tools such as gcc or make. Recently it got support for asm.js - optimizable, low-level subset of JavaScript.

I wasn't the first to come up with this idea - one of our local heroes, Noel O'Boyle wrote a set of articles about translating the InChI code into JavaScript on his blog. I didn't know about his work during my experiments, which is good, because I took slightly different approach and came up with different results:

I decided to compile inchi-1 binary (by exposing its main function) not the library, because, according to readme file in InChI distribution package, the binary 'does extensively check the input data and does provide diagnostic concerning input structure' so it's the only tool that can be used as an InChi generator with 100% guarantee of having correct results for all input files.
I used '-O2 -s ASM_JS=1' flags to optimize speed.
The resulting JavaScript code (emscripten generated html with embedded JS) weighted 2.8 MB and 732 kB after zip compression (all modern servers and browsers support compressed files). The original inchi-1 binary is about 1.1 MB large so this sounds reasonable.

Of course there are some drawbacks of my approach - the most obvious one is IO. inchi-1 is command line tool expecting a file or plain text as input and printing some text to stdoutand stderr. JavaScript doesn't have any standard input or output. This means that this behavior must be somehow mapped to browser environment. Emscripten maps output to specific textarea element which is reasonable. On the other hand any request for user input is mapped to javascript prompt window. This prompt can accept one line of text at time. Molfiles contain many lines so putting a molfile line by line is tedious.

The solution to this problem would be adding a file input to the webpage and accessing it via Javascript Blob interface. Having the files selected allocating some memory in Emscripten using hints from this SO question and pass it to process_single_input function from inchimain.c file (this should be exported instead of main).

So far I haven't solved the last issue. You can check proof-of-concept here. To use it, open link in your browser, open javascript console (Control-Shift-K on Firefox, Control-Shift-J on Chrome), then type (as two separate commands, pressing Enter after each one):


bla = Module.cwrap('process_single_input', 'string', 'string')

bla('bla -STDIO')

After that, the standard javascript prompt will pop up. You have to copy there your mol file - line by line. If the line should be empty (usually 1st and 3rd lines are) just press enter in the input box. After last line (M END) hit cancel instead of OK. Then select a checkbox suppressing all further popups and press OK. If you entered all mol file lines correctly you will see the result!

michal

Comments

Noel O'Boyle said…

Nice. Here's the missing link: http://baoilleach.blogspot.co.uk/2011/05/almost-translate-inchi-code-into.html

9 May 2013 at 22:23

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.

ChEMBL 26 Released

We are pleased to announce the release of ChEMBL_26 This version of the database, prepared on 10/01/2020 contains: 2,425,876 compound records 1,950,765 compounds (of which 1,940,733 have mol files) 15,996,368 activities 1,221,311 assays 13,377 targets 76,076 documents You can query the ChEMBL 26 data online via the ChEMBL Interface and you can also download the data from the ChEMBL FTP site . Please see ChEMBL_26 release notes for full details of all changes in this release. Changes since the last release: * Deposited Data Sets: CO-ADD antimicrobial screening data: Two new data sets have been included from the Community for Open Access Drug Discovery (CO-ADD). These data sets are screening of the NIH NCI Natural Product Set III in the CO-ADD assays (src_id = 40, Document ChEMBL_ID = CHEMBL4296183, DOI = 10.6019/CHEMBL4296183) and screening of the NIH NCI Diversity Set V in the CO-ADD assays (src_id = 40, Document ChEMBL_ID = CHEMBL4296182, DOI = 10.601

The ChEMBL-og

Search This Blog