PhySIC: a veto supertree method with desirable properties.
Ranwez V., Berry V., Criscuolo A., Fabre P.H., Guillemot S., Scornavacca C., Douzery E.J.P.
Systematic Biology. 2007 56(5):798-817.
paper if you use PhySIC.
A new version of PhySIC is available here: PhySIC_IST
PhySIC online execution
A maintenance operation on the server hardware is scheduled on Wednesday August 24 at 14:00 (GMT+2).
The running jobs will be lost.
We apologize for the inconvenience.
The online interface
It is a web form that you fill with your data and values for the program options, your name and the country where you are; then click on the "Execute & email results" button to start the program with your settings; after a while you will receive your results by email.
For a quick start, simply select the "Example" radio button, type your email, and click the "Execute & email results" button. This will run the program with default values; the example tree file contains three trees in Newick format.
- Source tree file
The input file contains rooted source trees encoded in standard Newick format, possibly containing edge lengths and bootstrap values:
The same trees viewed with TreeView:
- User supertree (optional)
You have the possibility to study a supertree already inferred by another method (MRP, etc) to know which clades would collapse according to the PI & PC properties. This enables to detect dubious clades such as novel clades not supported by the input trees (thanks to PI) or even contradicting input trees (thanks to PC).
If you use this option, Physic does not infer a supertree by itself, but instead collapses nodes of the given supertree that do not respect PI and/or PC, tagging the resulting multifurcations accordingly, ie by PI and/or PC labels.
- Bootstrap threshold for source clade selection
Before computing the supertree, the program first collapses source tree branches having a bootstrap proportion (bp) lower than the indicated threshold. Hence, only significantly supported clades are considered for supertree building (this is especially important with veto supertree methods). For instance, if bps range from 1 to 100 in the source trees (as in the above example), you can typically use 70 as a clade selection threshold.
Source trees that do not contain bp are not affected by this collapsing step. Thus, the input file can contain a mix of trees with bps and trees without. Note that trees with only some bp missing, are not considered by the collapsing step. If you do not want the program to collapse branches at all, just set the treshold value to 0.
With the above input file you will obtain the following supertree in setting the clade threshold to 60:
The outputted supertree contains labels (either PI, PC or PIPC) indicating the reason for each multifurcating node. These labels can be seen with usual tree viewing/editing softwares such as TreeDyn
, Treeview X
Mainly, PI indicates unsufficient overlap between the source trees to choose any possible resolution of the node; PC indicates that any further resolution of the node would contradict at least one source tree; PIPC is a combination of both phenomena, ie resolving further the node would result in either arbitrary branches or branches contradicting some soure tree(s) (see the paper
To obtain a supertree as resolved as possible (under the constraints of the algorithm), as a rule, if you obtain mainly PC labels, try to increase the threshold, and if you obtain mainly PI labels, try to decrease the threshold.