Citation

Orion ® Floes

To cite use of an Orion-based Floe package, please use the following:

OpenEye <package-name> <version-number>. OpenEye, Cadence Molecular Sciences, Santa Fe, NM. http://www.eyesopen.com.

For example:

OpenEye Classic Floes 0.11.2. OpenEye, Cadence Molecular Sciences, Santa Fe, NM. http://www.eyesopen.com.

The version number for a Floe package is displayed on the first page of the package’s release notes. For example: https://docs.eyesopen.com/floe/modules/classic-floes/docs/source/releasenotes.html.

Toolkits and Applications

To cite OpenEye toolkits or applications used in your work, please use the following:

OpenEye Toolkits [or Applications] <version-number>. OpenEye, Cadence Molecular Sciences, Santa Fe, NM. http://www.eyesopen.com.

For example:

OpenEye Toolkits 2023.1. OpenEye, Cadence Molecular Sciences, Santa Fe, NM. http://www.eyesopen.com.

The Applications and Toolkits are released as a package, multiple times per year. The first part of the version number designates the calendar year. The version number appears on the summary document for the package.

If you want to cite an individual application or toolkit, you can use the syntax:

<product name> <version-number>. OpenEye, Cadence Molecular Sciences, Santa Fe, NM. http://www.eyesopen.com.

where <product name> is:

  • OEChem TK

  • OEDepict TK

  • FastROCS TK

  • Grapheme TK

  • GraphSim TK

  • Lexichem TK

  • OEMedChem TK

  • MolProp TK

  • Quacpac TK

  • OEFF TK

  • OEDocking TK

  • Omega TK

  • Shape TK

  • Spicoli TK

  • Spruce TK

  • Szmap TK

  • Szybki TK

  • Zap TK

  • AFITT Application

  • BROOD Application

  • EON Application

  • OEDocking Application

  • OMEGA Application

  • PICTO Application

  • pKa-Prospector Application

  • QUACPAC Application

  • ROCS Application

  • SiteHopper Application

  • SPRUCE Application

  • SZMAP Application

  • SZYBKI Application

  • VIDA Application

You can use the version number of the individual Application or Toolkit. For example:

SZYBKI Application 2.5.1.2. OpenEye, Cadence Molecular Sciences, Santa Fe, NM. http://www.eyesopen.com.

Szybki TK 2.5.1.2. OpenEye, Cadence Molecular Sciences, Santa Fe, NM. http://www.eyesopen.com.

The first documentation pages give the product names and version numbers, as in https://docs.eyesopen.com/applications/szybki/index.html and https://docs.eyesopen.com/toolkits/python/szybkitk/index.html.

OpenEye Web Services

To cite use of the Macromolecular Data Service (MMDS) web service, please use the syntax:

Macromolecular Data Service <version-number>. OpenEye, Cadence Molecular Sciences, Santa Fe, NM. http://www.eyesopen.com.

For example:

Macromolecular Data Service 1.1. OpenEye, Cadence Molecular Sciences, Santa Fe, NM. http://www.eyesopen.com.

The MMDS version number appears on the web service’s release notes.

To cite use of the FastROCS TM server, please use the syntax:

FastROCS <version-number>. OpenEye, Cadence Molecular Sciences, Santa Fe, NM. http://www.eyesopen.com.

For example:

FastROCS 1.4.4. OpenEye, Cadence Molecular Sciences, Santa Fe, NM. http://www.eyesopen.com.

The FastROCS version number appears on the web service’s release notes.

To cite use of the Molecules as a Service (MaaS) web service, please use the syntax:

MaaS <version-number>. OpenEye, Cadence Molecular Sciences, Santa Fe, NM. http://www.eyesopen.com.

For example:

MaaS 1.0. OpenEye, Cadence Molecular Sciences, Santa Fe, NM. http://www.eyesopen.com.

The MaaS version number appears on the web service’s release notes.