More at http://www.binc.co.in/College/Index_New.aspx

BINC notification http://www.binc.co.in/PdfDocuments/Notification.pdf

Few dates to remember:

Starting of online submission of application: March 9, 2015
Last date for submission of application: April 30,2015
Examination consists of two parts:
Part I (Paper I) : June 7, 2015 (10 AM-12 PM)
Part II ( Paper II & III) :June 28, 2015 (9 AM-12 PM & 2 PM-4 PM)

Bioinformatics Textbook Track

Find more about Rosalind puzzle at http://rosalind.info/problems/list-view/?location=bioinformatics-textbook-track

I will provide solution of all the Rosalind problem with Perl for community.

Check out the right sidebar for more links ...

Back in August, van Rossum published a proposal on the Python mailing list recommending type-checking annotations as a valuable feature for the next version of Python to improve the performance of editors and IDEs, linter capabilities, standard notation, and refactoring. Van Rossum’s latest proposal, posted late last month, outlined plans to publish a Python Enhancement Proposal (PEP) in early January to put the feature now known as type hinting on track for inclusion in Python 3.5, slated for release this September.

Reference

https://quip.com/r69HA9GhGa7J

This is a short post giving steps on how to actually install R packages. Let’s suppose you want to install the ggplot2 package. Well nothing could be easier. We just fire up an R shell and type:

> install.packages("ggplot2")

In theory the package should just install, however:

• if you are using Linux and don’t have root access, this command won’t work.
• you will be asked to select your local mirror, i.e. which server should you use to download the package.

Installing packages without root access

First, you need to designate a directory where you will store the downloaded packages. On my machine, I use the directory /data/Rpackages/ After creating a package directory, to install a package we use the command:

> install.packages("ggplot2", lib="/data/Rpackages/")
> library(ggplot2, lib.loc="/data/Rpackages/")


It’s a bit of a pain having to type /data/Rpackages/ all the time. To avoid this burden,  we create a file .Renviron in our home area, and add the line R_LIBS=/data/Rpackages/ to it. This means that whenever you start R, the directory /data/Rpackages/ is added to the list of places to look for R packages and so:

> install.packages("ggplot2")
> library(ggplot2)

just works!

Setting the repository

Every time you install a R package, you are asked which repository R should use. To set the repository and avoid having to specify this at every package install, simply:

• create a file .Rprofile in your home area.
• Add the following piece of code to it:


cat(".Rprofile: Setting UK repositoryn")
r = getOption("repos") # hard code the UK repo for CRAN
r["CRAN"] = "http://cran.uk.r-project.org"
options(repos = r)
rm(r)


I found this tip in a stackoverflow answer .

http://www.thestreet.com/story/13151062/1/affymetrix-acquires-assets-of-eureka-genomics-corporation-to-provide-high-throughput-and-economical-crop-and-animal-genotyping.html

http://www.stratosgenomics.com/stratos-genomics-technology

While your PhD or PostDoc application, it is more common that you got rejected by many professors. Don't disappoint reply it calmly.

In grad school, I shared a house with three Bioinformatics PhD students. One, when he applied to a particular professor, received a letter that said, essentially, "If you are applying because you want to enrich yourself, great. If you are applying because you want a job, you should know that you won't get one." I am trying to tell you this is because if you, with a good background in Bioinformatics, are passing up opportunities, you must be a strong candidate in many areas. Enrich yourself.

So, my suggestion is take a deep breath, forgot about all. Don’t take it personally. It's been usual processes while hunting for a good lab and professor. Take is positive, I am not sure why they reject, but don't worry perhaps the lab don't deserve you. Always remember there are billions of reasons not to hire someone for projects, especially in a research sector.

My suggestion, please do not whine about how you were a great research candidate for the post, and you just can't understand why they were so stupid as to have rejected you! This feeling will not win you any points in research, community. Especially, when in todays socially connected era everyone is linked. Remember, a nice E-mail saying, "I really wished to working with you on this project and I hope we cross paths again," is all you need to send to the professor. Send a thank you note to the professor. Thank them for the time they spend to judge you. In the future, If you and the professor (of your dream) are attending a bioinformatics conference, invite him/her to lunch (please remember to pay the bill). In today evolving scientific ere, always remember to build your solid network in order to get a job of interest. Join all possible networking sites like LinkedIn, ResearchGate, Acamedia, FB for the same reason. You as a researcher always build a bridge with student/researcher/colleague/professor who have the research potential to lead in research and hire you. Just because you didn't get this project, doesn't mean there isn't another that will open up in couple of month.

Mostly, jobs that are hard to get are hard to get. Only you can decide if the continued sacrifices are worth the expected payout. If it is, keep on plowing. Build relationships. Attend conferences.

Image ref @ JaSonYa

More at https://github.com/dentearl/n50PlottingTools

Address of the bookmark: https://github.com/dentearl/n50PlottingTools

Source:  Igor Ulitsky & Ron Shamir

Address of the bookmark: http://acgt.cs.tau.ac.il/guides/LiteratureGuide.htm