Difference between revisions of "Phylogenetics: NEXUS Format"

From EEBedia
Jump to: navigation, search
Line 9: Line 9:
 
== Using PAUP to create a NEXUS data file ==
 
== Using PAUP to create a NEXUS data file ==
  
First, download the file [{{SERVER}}/people/plewis/phylogenetics/data/angio35.nex angio35.txt] to your hard drive and then upload it to the cluster (instructions in [[Phylogenetics: Bioinformatics Cluster]]).
+
First, download the file [{{SERVER}}/people/plewis/courses/phylogenetics/data/angio35.txt angio35.txt] to your hard drive and then upload it to the cluster (instructions in [[Phylogenetics: Bioinformatics Cluster]]).
  
 
Now login to the cluster (<tt>bbcxsrv1.biotech.uconn.edu</tt>) and type <tt>paup</tt> to start the PAUP* program.
 
Now login to the cluster (<tt>bbcxsrv1.biotech.uconn.edu</tt>) and type <tt>paup</tt> to start the PAUP* program.

Revision as of 17:04, 21 January 2009

Adiantum.png EEB 349: Phylogenetics
The goal of this lab exercise is to show you how to easily create a NEXUS-formatted data file from a set of sequences. The NEXUS format is widely used in phylogenetics, and its basic features are described in the second part of this tutorial.

Using PAUP to create a NEXUS data file

First, download the file angio35.txt to your hard drive and then upload it to the cluster (instructions in Phylogenetics: Bioinformatics Cluster).

Now login to the cluster (bbcxsrv1.biotech.uconn.edu) and type paup to start the PAUP* program.

Important! Ordinarily, you should not run PAUP* directly like this. Only use this method for extremely short-lived activities. To run an analysis on the cluster, you should use the Sun Grid Engine's qsub program to submit a job. Using qsub starts your run on one of the computing nodes (whichever is free at the moment), while typing paup starts PAUP* on the head node, which is the node that everyone logs into to start runs. Bogging down the head node with a long PAUP* run is the quickest way to lose your cluster privileges! That said, what we are doing today will not be computationally demanding and thus should not attract the attention of Jeff Lary (if it does, I will take the blame).

Now type in the following (PAUP) command:

tonexus from=angio35.txt to=angio35.nex datatype=nucleotide format=text;

After the conversion, the file angio35.nex should be present. Open this Nexus file in the pico editor to see what PAUP* did to convert the original file to Nexus format.