- Archaeopteryx. This is my favorite. It is responsive given large trees and is one of the few supporting topology editing. Nonetheless, the circular view, which is in alpha, is not as good as others. I do not like its black background, either.
- FigTree. A nice tree viewer. Work efficiently with medium to large trees. It is more versatile than Archaeopteryx on viewing (e.g. the fish-eye mode and the circular layout). No topology editing.
- Dendroscope. A viewer (almost no editing options) designed for huge trees. The selling point is its efficiency, better than both FigTree and Archaeopteryx. Nonetheless, it does not seem to aim to produce publication-ready figures (e.g. no subtree highlighting). The circular view, like in Archaeopteryx, looks ugly because texts are not rotated.
- Jstree. My hobby. The first Javascript based tree editor, supporting operations such as subtree cut-and-paste. In firefox/opera/chrome/safari, it is pretty responsive for medium to large trees.
- PhyloWidget. It has a very impressive user interface, smooth and responsive given large trees. It supports topology editing. My major complaints are: a) I frequently scroll the tree out of the canvas but do not know how to get it back quickly; b) at least on my laptop, it is eating up CPU without actually doing anything.
- iTOL. A very nice tree viewer (no editing) written in Flash, but the responsiveness is not as good as those Java-based viewers. For medium trees, its rectangle view only displays the first tens of leaves.
- TreeGraph2. As is stated in its paper, treegraph2 mainly aim to produce beautiful high-quality figures for small trees. It supports many operations on trees, but its responsiveness is very bad.
- Mesquite. A very comprehensive software suite. It is efficient enough for large trees, but the user interface is not very friendly.
- TreeDyn. I have heard a lot of good things about it, but unfortunately, its Mac binary is not working in Mac OS X 10.6, so I have not tried.
- TreeViewJ. Nice UI, but not efficient enough for medium trees.
- Treevoletion. Nice UI, but inefficient for medium trees.
In GROMACS , while converting pdb file (monomer or multimer) into .gro file, it do not preserve the chain ID information. Due to the lack of chain ID information, pdb file retrieved from .gro file at any stage of the simulation has missing chain IDs and pdb file can not be visualized properly in PYMOL / RASMOL . There are two ways to convert .gro file into .pdb Lets say your protein name is xyz.pdb 1] gmx editconf -f xyz.gro -o xyz.pdb 2] gmx trjconv -f xyz.gro -o xyz.pdb -s xyz.tpr Only ' trjconv ' will retrieve the chain ID information for all the chains. and not ' editconf '. If you have monomer protein and wish to assign any chain ID then following command will be of your interest: gmx editconf -f xyz.gro -o xyz.pdb -label [ chain-ID ]
Comments
Post a Comment