Phylogenetics: Parsimony Lab

From EEBedia
Revision as of 14:15, 28 January 2007 by PaulLewis (Talk | contribs)

Jump to: navigation, search
This article is part of an EEB course.
Please do not edit the content of this page without the approval of the course instructor.

Part A: Using PAUP* to check your answers for homework #2

  • Create a NEXUS data file containing the data for the one DNA site you examined for homework assignment #2. To do this, start PAUP*, cancel the opening dialog box (because you have not created a file to open yet), then select File > New from the main menu to create an empty file. Referring to the description of a nexus data block from the previous lab, build a NEXUS file containing 4 taxa and 1 character corresponding to the data in homework assignment #2. Be sure to save the file, giving it a name like homework2.nex.
  • Execute your new data file to make sure there were no mistakes. Even though you are not yet finished setting up the file, it is always a good idea to periodically check to make sure PAUP* can interpret the contents. If you wait too long before doing this check, then you end up making multiple mistakes and it gets increasingly hard to figure out how to fix all of them! If it is still open, you can execute it in PAUP* using the key combination <Ctrl-r>. If it is not open, use File > Open... to open it again. If your file executes successfully, you should see a line such as the following:
    Processing of file "homework2.nex" completed.
  • Add a stepmatrix definition to specify that transitions should cost 1 step while transvesions should cost 2 steps. Add an assumptions block to your data file (note: do not add another "#nexus" to your file, this should appear only as the first thing in a NEXUS file). Your assumptions block should look like this:
    begin assumptions;<br>usertype my_ctype stepmatrix=4<br> A C G T<br> [A] . 2 1 2<br> [C] 2 . 2 1<br> [G] 1 2 . 2<br> [T] 2 1 2 .<br> ;<br>end;
    Feel free to replace "my_ctype" with a name of your choosing (but avoid using spaces or punctuation; note that I used an underscore character instead of a space). Save your file (using <Ctrl-s> is easiest), then re-execute using <Ctrl-r> to ensure that you haven't made any mistakes.