I have used the following assemblers

• Spades (v. 3.10.1)
• CANU (v. 1.6)
• Unicycler (v. v0.4.1)
• Miniasm (v. 0.2-r137-dirty)

I have used the following mappers

• minimap2 (v. 2.0rc1-r232)
• minimap (v. 0.2-r124-dirty)
• bwa (v. 0.7.12-r1039)

I have used the following polishing tools

• Racon (v. not available)
• Pilon (v. 1.18)
• Nanopolish (v. 0.8.3)

I have used the following tools to assess genome assembly characteristics

• ANI.pl (https://github.com/chjp/ANI)
• CheckM (v. 1.0.7)
• Prokka (v. 1.12)
• QUAST (v. 2.3)
• mummer (v. not available)

If you have any ideas or superior tools we have missed please let us know in the comments.

No. CSE/14/1038

Walk in Interview for the post of JRF under TEQIP-II

SN Department – Qualification Post Graduation – Time

1 Bio-Informatics & Mathematics M.Tech Bio-informatics/M.Sc.* Maths 10.00 AM

2 Biological Sciences M.Sc.* in any branch of Biological Sciences 10.30 AM

3 Chemical Engineering M.Tech Chemical Engineering 11.00 AM

4 Chemistry M.Sc.* Chemistry 11.30 AM

5 Civil Engineering M.Tech Structure/GeoTech. /Water -Resources/Hydraulics/Environment/Transport 12.00 Noon

6 GIS M.Tech GIS/Civil 12.30 PM

7 Computer Science & Engineering M.Tech CSE/Information Security 01.00 PM

8 Electrical Engineering M.Tech Electrical Derives 01.30 PM

9 Electronics & Communication M.Tech Digital Communication 02.00 PM

10 MSME M.Tech Material Science/ Mechanical/Metallurgy 02.30 PM

11 Physics M.Sc.* Physics 03.00 PM

* M.Sc. with NET/GATE qualified

Resume along with one passport size photograph and relevant documents are required at the time of interview

Amount of Fellowship: Rs 18000/-month+ HRA

Duration: 31st Dec 2014 (End of TEQIP-II project)

Date of Interview: 7th February 2014

Venue Institute Committee Room

Advertisement:

http://www.manit.ac.in/manitbhopal/Year2014/Recruitment/Advertisement%20JRF.pdf

More at http://evolscientist.com/

Qualifications

PhD or Post-Graduated Master degree is required. Successful candidates will have some expertise in data analysis of NGS data by using methods running in R and UNIX environment. Familiarity with genome databases and browsers is required.

Application

Candidates should send a CV and a brief personal statement focusing on their skills and interests related to the research project.

Contacts

Start date: 1° April 2014
Salary on grant: 25,000 euros per year.
Contact Person (Referent): Mario Capasso
Ref. Email: mario.capasso@unina.it and achille.iolascon@unina.it
Tel: +39 081 3737889

Daniel A Dalquen, Maria Anisimova, Gaston H Gonnet, Christophe Dessimoz: ALF - A Simulation Framework for Genome Evolution. Mol Biol Evol, 29(4):1115-1123, April 2012.
http://mbe.oxfordjournals.org/content/29/4/1115

Address of the bookmark: http://alfsim.org/#index

If you have a license key for Modeller 8 or 9, there is no need to reregister for Modeller 9.13 - the same license key will work. (It won't do any harm to reregister if you want to, though!)

9.13 is primarily a bugfix release relative to the last public release(9.12). Major user-visible changes include:

# Modeller now includes a variety of SOAP (statistically optimized atomic potential) scores for assessing proteins, loops, and interfaces.

# The Lennard-Jones interaction energy is now artificially truncated at very short distance; this makes simulations with poor starting conditions much less likely to 'blow up'.

# model.get_insertions(), model.get_deletions() and model.loops() now have an include_termini option; if False, residue ranges that include chain termini are excluded from the output.

See the Modeller manual for a full change log: http://salilab.org/modeller/9.13/manual/node39.html

If you encounter bugs in Modeller 9.13, please see http://salilab.org/modeller/9.13/manual/node10.html for information on how to report them.

Reference:

http://salilab.org/modeller/

Computational methods used by the Shasta assembler include:

• Using a run-length representation of the read sequence. This makes the assembly process more resilient to errors in homopolymer repeat counts, which are the most common type of errors in Oxford Nanopore reads.
• Using in some phases of the computation a representation of the read sequence based on markers, a fixed subset of short k-mers (k ≈ 10).

More at https://chanzuckerberg.github.io/shasta/index.html

Address of the bookmark: https://github.com/chanzuckerberg/shasta

Bioinformatician are not anti-social; We are just genome friendly.

Bioinformatician would love to change the biological world, but they won't give us the genetic code :P

If at first you don't succeed; call it version 1.0

The glass is neither half-full nor half-empty: it's actually have several genomes.

I'm BioGeek.

Fedup with LIPS, try God script.

Idiot, Go ahead, make my data!

Thank god, my genome just compiled.

Error message: "Out of space on genome drive:"

Shut up mobile elements, or i'll flush you out.

Never underestimate the internet bandwidth, u gotta incomplete.

Applied fuzzy logic to understand God's logic?

Warning! Overflow, delete chromosome !

Be nice to the BioGeek, for all you know they might be the next curator!

Beware of computational biologist they screw genes and protein.

Warning! Your genome is full of garbage, delete it !

Bad or missing mouse genome. Spank the cat? (Y/N)

Genome make very fast, very accurate mistakes.

Let's BLAST it.

Some genome never has transposons. It just develops random features.

Go watch CINEMA and have BLAST.

Address of the bookmark: https://github.com/vpc-ccg/haslr

1. Update new things continuously
As per my personal experience, it’s not always easy to work as a bioinformatician!  There are couple of reasons to say that; First computational part of biology make our life’s a little harder compared to other professional categories. The fact - for instance - that the technology cycle in the bioinformatics world is very short, the actual knowledge becomes outdated in a few months or years. Therefore, we need to learn continuously - new things get important. Second, to stay on top of things we really need the strong will to be good at our job. That's probably the most important characteristic to bioinformatician. They are usually an excellent knowledge worker with great technical abilities, and have the will to be that over decades!

2. Avoid the sentence "I did not know what to do!"
In our computational biology lab, we generally face lots of technical problems. But as you know, it's impossible to know everything to do the computational biology jobs ( Yup.. because you need diverse and multidisciplinary knowledge to understand biological problems and resolve their respective solutions), therefore it's absolutely necessary that a bioinformatician finds its way through a new topic. How I typically do that is I use google and I talk to other experts in our laboratory or online biostar community to find out what they think. "I did not know what to do!" should not be an argument for us.

3. To make oneself useful
Several time it does happen, you finished our task earlier than expected; in such cases if you have some time left then: Take a coffee and play chess; reversi, etc. In my case I take a rest. Afterwards I think about what I could do that helps the team to achieve its targets, 'cause some of my team mates probably didn't finish! (at least if I didn't met them at coffee bar !!)

4. Care for all
During my rigorous research duration; I attended several workshop organized by my University departments. I had a discussion with other research fellow, professors; I generally ask … what it really takes to make a team successful or to be a successful research leader. They always said: "Well, you need some caring people!" I think there is a lot truth in that statement. If we do not care about quality, timelines, good team culture, respectful communication (!!), clean code, if all this doesn’t matter to us, then I believe the probability is higher that we fail in research and analysis.

5. Be good with people
Because bioinformatician and computational biologist jobs typically involves to work in a (most wanted J cross-departmental!) team, therefore it's important that we're (more or less) good in dealing with other individuals. Everyone have their own strengths and weaknesses, just like us. It's important to treat all the research team mates with respect, regardless of their technical competence or contributions. Of course, sometimes people deserve a clear statement (!!!), but try to do these things one-on-one. Make sure nobody loses his face. Attend the meetings at the coffee bar; be good at table top soccer and go out once in a while to have a beer with your team. You know what I'm talking about.

At the end of a week I look back and I ask myself what I have produced. This could be paperwork, community days or (best!!) programming code. Always remember there is always a solution to a problem. Most of the times there are at least three solutions. So, don’t just blame, suggest a solution.

That's it. I am looking forward to your thoughts and comments!