Address of the bookmark: https://hpcugent.github.io/easybuild/

Tools

• Parsnp - Core-genome alignment and analysis
• Gingr - Interactive visualization of alignments, trees and variants
• HarvestTools - Archiving and postprocessing

Citation

Treangen TJ, Ondov BD, Koren S, Phillippy AM. The Harvest suite for rapid core-genome alignment and visualization of thousands of intraspecific microbial genomes. Genome Biology, 15 (11), 1-15 [PDF]

Address of the bookmark: http://harvest.readthedocs.io/en/latest/index.html

Address of the bookmark: http://www.australianprostatecentre.org/research/software/jcircos

1. Learn and get updated

Some of the bad biological programmers only learn new technical or non-technical things when it’s absolutely necessary. The good biological programmers learn new technical skills proactively. But great biological programmers not only learn new technical skills on their own but also learn non-technical skills, and have an open mind to sources of knowledge that others may shut out.

In other concrete term, the bad biological programmer learn Perl's regular expression when they started a project on comparative genomics; the good biological programmer learned it a year before because it looked interesting; and the great biological programmer also read about the BioPerl packages, genomics, DNA string, genomic theories, or some similar course of study so that they could understand the results and explain it biologically.

2. Not a merely coder!!!

I often encountered with biological programmer who call themself a hard-core computer programmer and avoid biology. I can almost guarantee that if you are one of them then you are not doing research but merely writing "dry" codes.

According to my supervisor most of the computational biologist, don't know what they are doing biologically. Even they struggle to explain their own programs output and results. Therefore, It is highly advisable to learn basic of biology which can assist you to explain the result and understand your discovery. Always remember you are a researcher not a coder.

3. Be Social with biologist

The computational biologist spends most of the time in from of computers, writing codes. They always think their job is to produce working codes, not technical research perfections. But, they are completely wrong. You should not forget that apart from your computational skills you also need some biologist, other than your supervisor, to explain and make you understand the complex biological mechanism.

I highly recommend your to interact with biotech researchers and learn how do they explain their one graph (which they generally produce after one year of work) biologically. Remember, the origin of your research project is complex biological phenomenon, which is more complex than that of your limited programming rules.

4. Do not search, research for answers

Researching for answers means more than typing several keywords into a search engine or posting a question at Stack Overflow or the BioStars forums. I have entered problems into search engines that generate no results, and every question I posted on Stack Overflow or the BioStars forums never got anything resembling an answer, yet I solved the issues and moved on. I’m not a magician — I just know how to find answers or discover root causes.

Many problems are situational, and if you depend on search engines and forums, you can waste a lot of time going down a rabbit hole and possibly never getting a solution. Learn to perform root cause analysis, learn enough about the underlying system to look for other clues and solutions, and learn to take a long distance view of an issue before deep diving into it.

5. Love and defend your research

You cannot rise to the top in this research profession without loving your work. There are some very good “it’s just a job” biological programmers (I’ve been one at times), but if that is your outlook, you won’t be willing to do whatever it takes to succeed. This idea gets a lot of folks in a huff, because they feel it is a personal insult. “I’m a good programmer, but I have other priorities and can’t make work my life.” I understand completely; I have other priorities too. As much as I hate to say it, when I am passionate about my work, I am willing (though not eager) to abandon my other priorities to finish the job. It is not an insult to say that if you aren’t willing to pull out all the stops you can’t be the best, it is a fact.

You must be passionate about more than programming — you must also be excited about your research, the tools and technology you are using, and so on. I have seen very good and even great biological programmers operating at mediocre levels because something was not a good fit, such as they hated the project or were using a technology they disliked. Therefore, like your research project and get excited about your discoveries. You have not only to discover but also defend your finding with scientific words.

Thanks to all of you for reading.

Know of any other open source software for PacBio data? Email us.

Software categories:

• De novo assembly
• Structural Variations Detection
• Reference-based alignment
• Consensus and variant calling
• RNA analysis
• Epigenetic base modifications and methylation
• Barcoding
• Genome Browsers
• Run QC
• Frameworks and APIs

Address of the bookmark: https://github.com/PacificBiosciences/DevNet/wiki/Compatible-Software

MEME Suite software development; gene expression; mathematical modelling; gene regulation and transcription

Specialization:
Pattern recognition and modelling in computational biology

Link @ http://www.imb.uq.edu.au/tim-bailey

Applications are invited for the STUDENTSHIP and TRAINEESHIP vacancies to carry out project/research work in the DBT - Bioinformatics Infrastructure Facility with consolidated stipend of Rs.5,000/- per month.

Essential Qualification

Student Trainee: Those who have completed M.Sc., Bioinformatics/Biophysics/Life sciences or Pursuing M.Tech., Bioinformatics/Biotechnology

Duration : 3-4 Months

Student Trainee: Those who are pursuing M.Sc Bioinformatics/Biophysics/ Life sciences/others

Duration : 2-3 Months

Mail your CV on or before 25th November 2013 to shirai2011@gmail.com and hard copy to "Dr. D. Velmurugan, Professor & Head, CAS in Crystallography and Biophysics, University of Madras, Guindy Campus, Chennai 600 025". Also, the applicants are requested to attend the interview on 29th November, 2013 at 11 A.M.

Advertisement:

www.unom.ac.in/uploads/announcements/bifadvertisement_20131114080003_23240.pdf

Address of the bookmark: https://www.baseclear.com/genomics/bioinformatics/basetools/SSPACE

CABOG is one of many software programs called genome assemblers. These programs exist to overcome the fundamental limitation of all sequencing machines, namely, that they read out very few DNA letters at a time. These programs reconstruct genomes that are billions of letters long from the hundreds of letters per read that modern sequencers provide. What these programs do is often described as a scaled up version of a family solving a jigsaw puzzle.

The CABOG software was the first to accomplish many scientific goals. It was the first to assemble the genome of a multicellular organism (Drosophila melanogaster, 2000). It was the first to assemble both parental haplotypes of one human genome (J. Craig Venter, 2007). It was the first to assemble environmental sequence from the oceans (Sargasso Sea in 2004 and Global Ocean Sampling in 2007). It was first to combine reads from first-generation Sanger sequencing machines and second-generation pyrosequencing machines (Marine microbes, 2006). Today, CABOG is one of the leading assembly programs for data sets that include paired end data from the Roche 454 line of sequencing machines.

Address of the bookmark: http://www.jcvi.org/cms/research/projects/cabog/overview/

Address of the bookmark: https://www.igenbio.com/ergo/