The Kripo data can be updated in 2 ways:
.. toctree:: :maxdepth: 1 Baseline update <baseline-update.rst> Incremental update <incremental-update.rst>
Overview of steps involved in updating Kripo:
- Create staging directory
- Create sub-pocket pharmacophore fingerprints
- Create fragment information
- Add new fragment information to fragment sqlite db
- Populate PDB metadata in fragments database
- Check no fragments are duplicated
- Calculate similarity scores between fingerprints
- Convert pairs file into dense similarity matrix
- Switch staging to current
- Update web service
Note
Steps 2 through 3 require undisclosed scripts or https://github.com/3D-e-Chem/kripo
Note
Steps 4 and 6 through 7 can be done using the KripoDB Python library.
.. todo:: Remove Kripo fragment/fingerprints of obsolete PDBs (ftp://ftp.wwpdb.org/pub/pdb/data/status/obsolete.dat)
Directories for Kripo:
- current/, directory which holds current dataset
- staging/, which is used to compute new items and combine new and old items.
- old/, which is used as a backup containing the previous update.
Files and directories for a data set (inside current, staging and old directories):
- pharmacophores.h5, pharmacophores database file
- out.fp.sqlite, fingerprints file
- fragments.sqlite, fragment information database file
- similarities.h5, similarities as pairs table
- similarities.packedfrozen.h5, similarities as dense matrix
Input directories:
- $PDBS_ADDED_DIR, directory containing new PDB files to be processed
- Slurm batch scheduler
- KripoDB and it's dependencies installed and in path
- Posix filesystem, NFS of Virtualbox share do not accept writing of hdf5 or sqlite files