Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Encode information from a HADDOCK run to a cif file to be deposited in PDB-Dev.

License

NotificationsYou must be signed in to change notification settings

haddocking/haddock-mmcif

Repository files navigation

🚧 Attention 🚧

This code is under development and subject to change. Please report any bugs by opening an issue in the repository.


Encode information from a HADDOCK run into a.cif to be deposited in PDB-Dev.

Currently the follow information is encoded in the.cif

  • Models are represented as:

    1. Whole structure as rigid
    2. Interface as flexible, defined by theflcut parmameter inrun.cns
  • Top4 models from each clusters withinModelGroup, ranked by their top4 HADDOCK score

  • Restraints asDataset represented asDerivedDistanceRestraint

    1. Ambiguous, Active/Passive asResidueFeature with probability defined byncvpart inrun.cns read fromambig.tbl
    2. Unambiguous, theResidueFeature are read fromunambig.tbl

To-be-implemented

  • HADDOCK-score

Installation

$ git clone https://github.com/haddocking/haddock2mmcif$ cd haddock2mmcif$ python setup.py develop$ cd tools$ g++ -o contact-chainID contact-chainid.cpp$ cd ..

Usage

The input forhaddock2mmcif is the folder of a run-directory, either downloaded from the web server or executed locally.

$ cd example_data$ tar zxvf 6269-E2A-HPR.tgz$ haddock2mmcif --output example.cif E2A-HPR/

About

Encode information from a HADDOCK run to a cif file to be deposited in PDB-Dev.

Topics

Resources

License

Stars

Watchers

Forks

Contributors2

  •  
  •  

[8]ページ先頭

©2009-2025 Movatter.jp