Jun 13, 2025
AU Test with IQTree
- Dakota Betz1
- 1ucsd
- Rouse Lab
Protocol Citation: Dakota Betz 2025. AU Test with IQTree . protocols.io https://dx.doi.org/10.17504/protocols.io.e6nvw5w7zvmk/v1
License: This is an open access protocol distributed under the terms of the Creative Commons Attribution License,  which permits unrestricted use, distribution, and reproduction in any medium, provided the original author and source are credited
Protocol status: Working
We use this protocol and it's working
Created: October 27, 2021
Last Modified: June 13, 2025
Protocol Integer ID: 54586
Keywords: au test with iqtree, iqtree, au test, protocol
Disclaimer
Our protocols are constantly evolving and old versions will be deleted.
The documents here are not intended to be cited in publications
Abstract
Our protocols are constantly evolving and old versions will be deleted.
The documents here are not intended to be cited in publications
Troubleshooting
Programs and Dependencies
IQ-Tree
Download: http://www.iqtree.org/
Additional information/tutorials: http://www.iqtree.org/doc/Advanced-Tutorial
Mesquite
RAxML-ng
Download: https://github.com/amkozlov/raxml-ng
GUI 2.0 (compatible with ng): https://antonellilab.github.io/raxmlGUI/
Text Editor (options below)
SublimeText: https://www.sublimetext.com/3
This protocol assumes you have already completed initial tree inference. It is designed to test another topology (constrained) against your unconstrained analysis. Before beginning this protocol, you will need:
- a copy of your unconstrained tree (.tre file)
- the data you used to create the unconstrained tree (.phy file, probably nucleotide data)
- knowledge/list of model(s) applied to your data
- if you're running a partitioned analysis (multiple genes or data types), you will also need a partition file (.txt or .nex file)
File Preparation
Make sure you have a copy of your original RAxML tree (against which you would like to test your constraint tree, which you have not created yet).
Open your original tree in FigTree if it is a .tre file and convert it to a nexus file. To do this, click:
File > Export Trees
And choose Nexus from the dropdown menu.
Append the filename of this nexus file with "_original.nex" so that it's easy to tell apart from the constraint you will make.
You will use the original file as a base to start your constraint. Open your tree file "_original.nex" in Mesquite. Re-save it as "_constraint.nex" before you begin making changes.
Collapse all of the nodes in your tree into a single polytomy, including the outgroup. See image below of the collapse tool:
Now select only the taxa you want to constrain and make those a single polytomy using the arrow cursor tool (they should be separate from the other polytomy which is the rest of the tree). The tree should now have a total of 2 polytomies.
Reminder: the outgroup is not separated out--it can be in the polytomy with the remaining taxa that you are not intending to constrain. Save again just in case (remember filename should now be "_constraint.nex").
Select Tree > Store tree in other block as and give your tree a name (e.g. "constraint"). Then Store in new tree block and name the new tree block. Select switch to new tree and select your new tree. To export this, click File > Export > Export Nexus tree file from tree source > stored trees. Make sure you select the tree you want (constraint). Check the box to include taxa block, then click Export > Save.
You should be able to open the newly saved "_constraint.nex" file in FigTree. If not, make a copy of this file outside mesquite (should be a .nex file) and add the extension .tre instead (works on Mac OS only). Now open the "_constraint.tre" tree in FigTree.
Once you have confirmed that Mesquite/FigTree saved the topology you wanted, export as a .nex file again from FigTree.
Drag this file ("_constraint.nex") into a text editor (e.g. SublimeText) and remove everything except the tree notation/newick format (the portion in parentheses). See below for an example of what this looks like. Save this as "_constraint.txt". in case the .nex version fails in RAxML.
RAxML Likelihood Estimation
For this part of the protocol, you will need the data and partitions you used to create your original/unconstrained tree, i.e.:
- your concatenated dataset (nucleotide or amino acid)
- your partitions for your concatenated dataset (if applicable)
Note
If you used RAxML-ng and the GUI 2.0 to make your unconstrainted tree, your concatenated file will be generated for you, and should end in "concat.txt". Your partitions file should also be generated for you, ending in "concat.part.txt".
Open the RAxML GUI and ensure you're set to run using RAxML-ng. Load in your concatenated dataset (concat.txt) file from your original/unconstrained phylogenetic analysis in RAxML. Load in your partition file (part.txt) from that analysis as well.
Now you will import the constraint tree file into RAxMLng as a multifurcating constraint. You can do this in the GUI by selecting (at the top menu) Analysis > Enforce Constraint > Use multifurcating constraint. When prompted, open your constraint tree file in either .nex or .txt format (either should work, but if .nex fails, try .txt).
Make sure you have the following settings in the RAxML GUI: RAxML-ng, ML Tree Inference, 1 run. Select the same outgroup that you used in your unconstrained analysis. Change the output name and folder to something that makes sense (e.g. "_RAxMLconstrained").
Note
Note: You do NOT need to bootstrap anything at this point in RAxML.
Run RAxML. The resulting "best tree" will be the constrained tree that you test against your "_original" unconstrained tree for the AU test. Name it something like "_RAxMLconstrained" so you can tell the difference between this and the constraint tree you made in Mesquite. To make the tree easier to open in FigTree, add the .tre extension to the end of the filename.
Combining Tree Files
Ensure both your "_original" and your new "_RAxMLconstrained" trees are in Nexus format. You can do this by opening them in FigTree and exporting them as Nexus files as in this step:
Open one of your trees in a text editor (e.g. SublimeText). Resave it as "_combined.nex" before you begin to make changes.
Make sure the label (probably "tree_1" in the text file) is edited to reflect which tree this is. For ex: if you opened your constrained tree first and renamed the file, make sure "tree_1" in this file is replaced with "constrained".
Open your other tree in a text editor. Copy and paste the tree notation (with the name, be sure to edit it to reflect which tree it is like you did in the previous step) into your "_combined.nex" file. Be sure to appropriately label this tree as well (this will be "original" if you opened the constrained first in the above step). Save and close your "_combined.nex" file.
When you save this tree in newick format, you'll lose the tree names youo created. This step will help you create a record or which tree was which so you can check back later if needed. Re-save tthe combined.nex file you just created as "_combined.tre". Now delete everything except the tree notation (look for parentheses/at example in this step : ). This includes the tree names and any other symbols, except the parentheses involved with the trees themselves (do not delete those) and the semicolon after each tree. Now if you forget which tree is which, you know they're in the same order in this file as in the "_combined.nex" file and can check back there if needed.
Open your "_combined.tre" file in FigTree to check that the trees look as expected. Export the tree in Newick format (same procedure as exporting for nexus, but select newick from the dropdown menu and "select all trees") with a .txt extension at the end of the filename.
For Multiple Models: Prepare Partition File
Note
If you plan on only applying a SINGLE model to your data (with or without partitions) for the AU test, ignore this section. You can proceed with a RAxML-style partition file.
If you would like to apply different models to different partitions for the AU test, you will need to create the more flexible nexus-style partition file (instead of the RAxML-style). Proceed with this section for detailed instructions.
Open your RAxML-style partition file in a text editor. You will need to convert it to a nexus-style partition file (example below). This file constrains a SETS block with CharSet and CharPartition commands to specify individual genes and the partition, respectively.
Example of nexus-style partition file. HKY+G model is applied to the first partition, while GTR+I+G is applied to the second partition.
Note
It is very easy to make typos in this file (missing or extra semicolons, commas, spaces, etc), so if you run into any errors during your AU test and are unsure what the issue is, double/triple-check this file first.
Save your nexus-style partition file as a .nex file (e.g. "partitions.nex")
Note
IQTree also allows combining sub-alignments from different alignment files, which is helpful if you want to combine mixed data (e.g. DNA and protein) in a single analysis. You can see an example of this at http://www.iqtree.org/doc/Advanced-Tutorial (search "Partitioned analysis with mixed data").
Running the AU Test
It's easiest to proceed if your terminal working directory is the same one that IQTree is in. For ease of use, open the IQTree folder on your computer and place a copy of the following files:
- your combined trees in newick format ("_combined.txt")
- your nucleotide dataset (concatenated) in phylip format ("nuc_concat.phy")
- your partitions for above dataset ("partitions.txt" or "partitions.nex")
Note
Alternatively, you can keep your files where they are if you make sure you use absolute paths to all files and programs involved (including IQTree, your files, etc).
Use the following code to run the AU Test with a likelihood approximation:
For partitioned data that uses a single model:
Command
Note: GTR+I+G is an example model. Other models can be specified in the format MODEL+FreqType+RateType
new command name
For partitioned data using multiple models (remember you will need the nexus-style partition file from Steps 18-20 for this):
Command
new command name
The results of the test are contained in the file ending in ".iqtree".