What can be the reason of getting negative branches lengths after treeannotator analysis?
I thought that BEAST does not allow negative lengths of branches on prior distribution level so I got very surprised when I have looked at my consensus tree in FigTree.
What could be the reason of this and how to wrestle with this phenomenon?
I am analysing about 1500 taxa of HAV (subtype: IA, region: VP1) under the next parameters: GTR+Г, Strict Clock, Coalescent constant population. Tree was generated by treeannotator through ~/beast/bin/treeannotator -heights median -burnin 20 -limit 0.5 VP1_test_bt_ExpPop.trees VP1_test_bt_ExpPop.tree
I found the answer on ResearchGate from Santiago Sanchez-Ramirez & let me quote it here:
Try using the option
-heights cawhen you run TreeAnnotator. This stands for "common ancestor trees" and aims at summarizing clade ages across all posterior trees and not only the values for subset of trees that have that clade. If that subset of trees is low in frequency the average node height might end up being older than the direct ancestor. Here is the explanation for negative branches: "MCC trees produced by TreeAnnotator can have a descendent node that is older than its direct ancestor (a negative branch length). This may seem like an error but is actually the correct behaviour. The MCC tree is, by default, generated with average node heights across all trees in the sample which contain that clade. The negative branch lengths result when a clade is at low frequency and tends not to occur in those trees that have the MCC tree's ancestral clade (or vice versa). This means the average heights are for the adjacent nodes are derived from different sets of trees and may not have any direct ancestor-descendent relationship." In this paper you will find more information about thecaoption: Looking for trees in the forest: Summary tree from posterior samples
- netEmbedding() Function in CellChat - UMAP not recognized
- Filter a .fasta file
- Nextflow pipeline: Accessing files from a channel when handling single and multiple inputs
- Using Bio.SeqIO to write single-line FASTA
- Using Biopython (Python) to extract sequence from FASTA file
- Reduce Grange and keep meta column
- Pandas dataframe is mangled when writing to csv
- Questions about DESeq2 and setting up logical vectors to select a result file
- Find non-overlapping intervals within DNA coordinates
- Accurately Compute Overlapping and Non-Overlapping Genomic Intervals Across Two DataFrames in Python
- How to compare two tab-separated files and mark 'Fail' if col6 of file1 matches col2 of file2, else 'Pass'?
- bulk operation with reformat.sh (bbmap)
- Filter strings with high proportion of lowercase letters
- Replacing PDB atom names with Biopython
- snakemake: MissingOutputException in rule hifiasm in file /home/usr/path/to/Snakefile, line 13
- TaskRun failed to finish due to an error for Coretex BioInformatics workflow
- Merging fastq files with same barcode in two different folders to another folder
- Efficiently fetch sequences for sliding window (large dataset)
- If else for "temp" in snakemake
- Snakemake rule fails after doing only 1 job - Sortmerna
- Writing Python output as xlsx
- Making lines not overlap
- Failed to load expression data from Geodataset in R
- How to select files in subdirectories by name and move all files containing "XXX" and "YYY" into new directories
- Multiple variables in input and output using wildcards snakemake
- How to enable "output" to detect variables in "run" in snakemake
- Reverse complement of DNA strand using Python
- Is there a way to make two scatter density plots share the same legend in R
- config file taking it as literal string snakemake
- Ignoring Sample Information when Making VCF with Freebayes