Inter-residue Current calculation in Proteins from MD trajectory
CURP permits to compute inter-residue flow of energy or heat and atomic stress tensors in a protein, given atomic coordinates and velocity trajectories obtained through molecular dynamics (MD). Energy flow data permit to picture an inter-residue Energy Exchange Network as a graph.
Within thermally fluctuating protein molecules under physiological conditions, tightly packed amino acid residues interact with each other through heat and energy exchanges. Non-uniform pattern of heat flow in proteins are illustrated and characterized with a theoretical model based on “local heat conductivity” between each residue pair. This model demonstrated characteristic features of “hidden dynamic allostery” in PDZ domain  and allosteric transition in the oxygen sensor domain of FixL .
Offical website and tutorial can be found at https://curp.jp/.
To install curp, run
pip install Curp
or your favorite python package manager, like conda or pipenv. You can get curp source code by running
git clone https://github.com/yamatolab/current-calculations-for-proteins.git
Then, go in the installed directory and use
pip install .
New branches should be made only from development branch, except for hotfixes. Same rule applies for merges. The development branch is then merged to master, see A successful Git branching model.
Commit messages should follow these rules:
Separate subject from body with a blank line
Limit the subject line to 50 characters
Capitalize the subject line
Do not end the subject line with a period
Use the imperative mood in the subject line
Wrap the body at 72 characters
Use the body to explain what and why vs. how
Derezz the master control program MCP turned out to be evil and had become intent on world domination. This commit throws Tron's disc into MCP (causing its deresolution) and turns it back into a chess game.
These rules, example and more explanations can be found on How to Write a Git Commit Message article from Chris Beams.
New classes and functions should ALWAYS be written with a docstring. Docstrings follow the rules of numpydoc, as described in numpydoc docstring guide.
Test units use nose, although tests haven’t been properly configured yet.
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.