This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
lecture_notes:04-16-2010 [2010/04/19 19:40] karplus added a caveat about example that wasn't from the lecture, fixed indenting on last list |
lecture_notes:04-16-2010 [2010/04/20 03:09] (current) karplus fixed punctuation that was messing up final list |
||
---|---|---|---|
Line 13: | Line 13: | ||
* Currently, tools are installed under /campusdata/BME235/bin/old_Newbler/. | * Currently, tools are installed under /campusdata/BME235/bin/old_Newbler/. | ||
* Tools with prefix "gs" are not supposed to be run directly. | * Tools with prefix "gs" are not supposed to be run directly. | ||
- | * Kevin has written several scripts in Python (version 2.6) which aid in building and analyzing genomes. Currently, these scripts do not work on Campusrocks, as the version of Python installed is 2.4 and it is under the process of being updated to version 2.6. | + | * Kevin has written several scripts in Python (version 2.6) which aid in building and analyzing genomes. Currently, these scripts do not work on Campusrocks, as the version of Python installed is 2.4 and it is under the process of being updated to version 2.6. (Python2.6.5 has now been installed in /campusdata/BME235/bin/ --- //[[karplus@soe.ucsc.edu|Kevin Karplus]] 2010/04/19 20:03//) |
* Newbler assembly tools take .sff (color space and quality data) files as input and converts them into .fna (fasta file with nucleotide information) files. | * Newbler assembly tools take .sff (color space and quality data) files as input and converts them into .fna (fasta file with nucleotide information) files. | ||
* Good only with 454 data, and is not good on reads with length < 50. | * Good only with 454 data, and is not good on reads with length < 50. | ||
Line 58: | Line 58: | ||
* Its better to run the tool in the current working directory. | * Its better to run the tool in the current working directory. | ||
* Create a README file in each new directory and it should contain all the necessary stuff required to run the assembly tool. | * Create a README file in each new directory and it should contain all the necessary stuff required to run the assembly tool. | ||
- | * Create Makefile for each assembly tool. (Makefile for newbler_assembly tool is in /campusdata/BME235/assemblies/Pog//newbler-assembly1/). You can use it as a template and modify the data source and the expected coverage as required. Makefile should be considered as "a book for lab protocols". | + | * Create Makefile for each assembly tool. (Makefile for newbler_assembly tool is in /campusdata/BME235/assemblies/Pog/newbler-assembly1/ ). You can use it as a template and modify the data source and the expected coverage as required. Makefile should be considered as "a book for lab protocols". |
- | * Its always better to say append to make.log in Makefile. | + | * It is always better to say append to make.log in Makefile. |
* Wiki page for assembly tools should contain a summary of how to run the tool and other things that might be useful to look at. | * Wiki page for assembly tools should contain a summary of how to run the tool and other things that might be useful to look at. | ||