Skip to main content

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 heroesNoel 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:
  1. 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.
  2. I used '-O2 -s ASM_JS=1' flags to optimize speed.
  3. 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!



Noel O'Boyle said…
Nice. Here's the missing link:

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

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

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

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