In 2011, the first prototype of RInChI was introduced as version 0.02 based on Python programming (Grethe, Goodman, Allen, 2013). To make the resulting libraries comparable with InChI deliveries, to increase the search ability of RInChIKeys in the Web by the introduction of the Web-RInChIKey and to fix a number of bugs and development gaps in the former version this new version (version number 1.00) has been created. This version is supposed to be published for general usage by the InChI Trust.
For more details see: http://www-rinchi.ch.cam.ac.uk/.
The RInChI format is a hierarchical, layered description of a reaction with different levels based on the Standard InChI representation (version 1.04) of each structural component participating in the reaction.
RInChIKeys are hashed representations of the RInChI strings. The hashing process creates shorter strings that are unique representations of the original (longer) RInChIs. However, RInChIs (and therefore the original RXN and/or RD file) cannot be rebuilt out of the hashed string. That makes RInChIKeys an encrypted unique depiction of chemical reactions especially suitable for database processes and web operations. For the anticipated usage, three different types of RInChIKeys have been developed:
Accepts RXN or RDF input. Note: If agents occur, the RXN file format is not sufficient as agents in an rxn string are ignored by the RInChI library.
Instead, the reaction must be described in the RD file format that contains catalysts, solvents and other reagents as molfiles following the reaction section in RXN format within the RD file section.
You want to see the source code for this node? Click the following button and we’ll use our super-powers to find it for you.
To use this node in KNIME, install the extension Lhasa reaction contributions from the below update site following our NodePit Product and Node Installation Guide:
A zipped version of the software site can be downloaded here.
Do you have feedback, questions, comments about NodePit, want to support this platform, or want your own nodes or workflows listed here as well? Do you think, the search results could be improved or something is missing? Then please get in touch! Alternatively, you can send us an email to email@example.com, follow @NodePit on Twitter, or chat on Gitter!
Please note that this is only about NodePit. We do not provide general support for KNIME — please use the KNIME forums instead.