Differences between revisions 10 and 13 (spanning 3 versions)
Revision 10 as of 2012-03-16 21:59:51
Size: 3392
Editor: IanRees
Comment:
Revision 13 as of 2012-03-22 19:02:29
Size: 3385
Editor: IanRees
Comment:
Deletions are marked like this. Additions are marked like this.
Line 5: Line 5:
e2pathwalker.py is a key component of Pathwalker, described in the following publication: e2pathwalker.py is a component of [[Pathwalker]], described in the following publication:
Line 16: Line 16:
We generally use LKH as the TSP solver for Pathwalker; it is fast, works well, and is relatively easy to compile.

You can download LKH from the author's site:
We generally use LKH as the TSP solver for Pathwalker; it is fast, works well, and is relatively easy to compile. You can download LKH from the author's site:
Line 23: Line 21:
and run "make".

This will result in a binary "LKH" in LKH-2.0.5. You can copy this to
and run "make". This will result in a binary "LKH" in LKH-2.0.5. You can copy this to

e2pathwalker.py

e2pathwalker.py is a component of Pathwalker, described in the following publication:

Installing a TSP Solver

e2pathwalker.py is included in the EMAN2 distribution, but requires a third party Traveling Salesman Problem (TSP) solver to run. Two TSP solvers are supported: LKH and Concorde.

Installing LKH

We generally use LKH as the TSP solver for Pathwalker; it is fast, works well, and is relatively easy to compile. You can download LKH from the author's site:

It is pretty easy to compile -- go into the LKH-2.0.5/SRC directory and run "make". This will result in a binary "LKH" in LKH-2.0.5. You can copy this to /usr/local/bin or somewhere in your $PATH.

Installing Concorde

...

Running Pathwalker

e2pathwalker.py operates on a single PDB file. With no additional options, it will simply read the PDB file and print out some statistics. To actually run the TSP solver, use the --solve option, with either --solve=lkh to use the LKH solver, or --solve=concorde to use the Concorde solver.

To save the TSP results, use the --output option with a filename: e.g. --output=test.pdb

By default, e2pathwalker.py will use the 'CA' atoms in 'A' chain in the input file; this can be changed with the --atomtype and --chain options.

There are several additional options; the current e2pathwalker.py options can be displayed using --help.

muta:~ irees$ e2pathwalker.py --help
usage: prog [options] <pdb file>
        
        Find paths between two atoms in a PDB model. You can also specify two PDB files to calculate an RMSD.
        
        Use "--solve=<solver>" to run the TSP solver and save the output.
        Use "--output" to save the output to a PDB file.

optional arguments:
  -h, --help            show this help message and exit
  --version             show program's version number and exit
  --output OUTPUT       Output file
  --start START         Start ATOM
  --end END             End ATOM
  --average AVERAGE     Average Ca-Ca length
  --dmin DMIN           Mininum Ca-Ca length
  --dmax DMAX           Maximum Ca-Ca length
  --noise NOISE         Add Gaussian Noise
  --solver SOLVER       Run TSP Solver: concorde or lkh
  --atomtype ATOMTYPE   Load Atom Type. Default: 'CA'. Options: 'C' or 'all'
  --chain CHAIN         Load Chain. Default: load all chains
  --edgefile EDGEFILE   Load fixed fragment file; one sequence of forced
                        connections per line, separated by space.
  -e EDGE, --edge EDGE  Forced edge: e.g. -e1,3
  --iterations ITERATIONS
                        Iterations
  --json JSON           If writing output pdb, also write JSON metadata.
                        Default: 1. Options: 0, 1
  --overwrite           Overwrite files without prompting
  --verbose n, -v n     verbose level [0-9], higher number means higher level
                        of verboseness
  --ppid PPID           Set the PID of the parent process, used for cross
                        platform PPID

Examples

FAQ

EMAN2/Programs/e2pathwalker (last edited 2016-09-06 12:21:24 by MuyuanChen)