Skip to content

Why different default ChemCompProviders for different parsers? #169

Closed

Description

@josemduarte

It seems that the ChemCompProvider defaults are:

  • for PDB parser it is ReducedChemCompProvider
  • for mmCIF parser it is DownloadChemCompProvider

is there a reason for that?

See also issue #145

Activity

  1. andreasprlic commented on Sep 17, 2014

    @andreasprlic
    Member

    The short answer is that the PDB parser is set up to quickly get going and the mmCif parser to support a full and chemically correct representation of all compounds.

    The long answer is that all ChemCompProviders have strengths and weaknesses and there is not a single one which is best. Each of them serves different purposes:

    The AllChemCompProvider loads all definitions of compounds into memory at startup. This initial loading is slow and is not ideal when working with single PDB entries. As such the DownloadChemCompProvider was written, which offers a quick startup and downloads missing defitions on demand. However it requires a working network connection and overall performance is much slower when working with large sets of PDBs. Finally the ReducedChemCompProvider offers a quick startup time, while not requiring a network connection. The cost for this is that it does not offer a full chemically correct representation of all the data.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    questionOpen discussions about the library

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions