This chapter contains the docstrings for the public portion of the chemfp API. Chemfp also has internal modules and functions that should not be imported or used directly. If you use parts of the undocumented API then your code is more likely to break with newer chemfp releases.
See “Getting started with the API” for some introductory examples.
- chemfp top-level
The top-level chemfp module is the starting point for using chemfp. It contains functions to read and write fingerprint files, “high-level” commands for working with chemfp, and more.
The API for the FPS and FPS fingerprint readers and writers are
chemfp.fpb_io, which may refer to
a Location object defined in
The fingerprint arena class is defined in
The chemfp.search module contains similarity search functions for
searching fingerprint arenas, and the search result class
definitions. This is a more low-level API than using
The chemfp.fps_search module contains similarity search functions for searching FPS files, and the search result class definitions. This is only needed when working in a streaming environment where fingerprint arena creation overhead is too large.
The chemfp.diversity module contains chemfp’s diversity pickers, all
of which require a fingerprint arena. This is a more low-level API
chemfp.rdkit\_toolkit contain the
public-facing API for chemfp’s cheminformatics toolkit wrapper
Sometimes you need to work with SMILES or SD files as text records,
not molecules. For that, use the
chemfp.bitops module has functions to work with fingerprints
represented as byte strings or hex-encoded strings, as well as
configuration functions for configuring chemfp’s bit operations. Use
chemfp.encodings to decode from various fingerprint string
representations to a byte string.
chemfp.types module contains a few public exceptions
which derived from ValueError but which don’t yet also derive from