Address of the bookmark: https://github.com/dthill196/SARS-2-Dashboard-Tutorial

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!

the evolutionary history of genes and species, building phylogenetic trees of life
the contrasting roles of horizontal gene transfer and introgression in shaping evolution
the biology of symbioses, especially symbioses between eukaryotes and bacteria, and between parasites and their hosts
the processes that drive the evolution of pattern in the structure of chromosomes
the diversity of meiofauna, particularly tardigrades, nematodes and other Ecdysozoa
the genomics of extremophilia

More at https://www.sanger.ac.uk/group/blaxter-group/

Candidates must have: a PhD degree in statistics, biostatistics or bioinformatics, extensive experience in analyzing high-dimensional data (microarray, SNP, CNVs) and of validation approaches. In addition, experience in penalized regression methods, data base manipulation; and strong programming skills in order to conduct Monte Carlo studies and applications (R). Candidate must have excellent communication skills (verbal, written and presentation), a strong proficiency in Linux system.

This position is available immediately and will be filled as soon as possible. Appointment could be extended beyond the first year based on additional funding.

For more information about the Department of Biostatistics and Bioinformatics, please visit our website: http://www.biostat.duke.edu.

For more info: http://biostat.duke.edu/sites/biostat.duke.edu/files/Halabi%20-%20Postdoc%20Job%20Posting%202013%20updated.pdf

Duke University is an Equal Opportunity/Affirmative Action Employer.

First cover a full workflow from preparation, reads counting, data preprocessing, gene set test, to pathway visualization in about 40 lines of codes. The same workflow can be used for GO analysis or other types of gene set analysis too. We also describe joint workflows, i.e. to do gene-level analysis using one of the major RNA-Seq analysis tools, DEseq/DEseq2, edgeR, limma and Cufflinks, and feed the results into GAGE/Pahview for pathway analysis or visualization. All these workflows are implemented in R/Bioconductor.

The work ows cover the most common situations and issues for RNA-Seq data pathway analysis. Issues like data quality assessment are relevant for data analysis in general yet out the scope of this tutorial. Although we focus on RNA-Seq data here, but pathway analysis work ow remains similar for microarray, particularly step 3-4 would be the same. Please check gage and pathview vigenttes for details.

Note: You need to update to current release versions of R(3.0.2)/ Bioconductor(2.13) to use all the features. 

Reference: 

Please check it out:
http://bioconductor.org/packages/release/bioc/html/gage.html
http://bioconductor.org/packages/release/bioc/vignettes/gage/inst/doc/RNA-seqWorkflow.pdf

Finally, I find the underlying R code in a file created by GrapheR. For more details read also the package vignette, which is available in English, French and German!

The developers and expert trainers are the authors of several popular R packages, including ggplot2, plyr, lubridate, and others.

More at http://www.rstudio.com/

http://www.rstudio.com/products/RStudio/

Address of the bookmark: http://www.rstudio.com/

• Function(data, options)

Even quit is a function

• q()

So is help

help(read.table)

Provides the help page for the FUNCTION ‘read.table’

help.search(“t test”)

Searches for help pages that might relate to the phrase ‘t test’

NOTE: quotes are needed for search strings, they are not needed when referring to data objects or function names.

There is a short cut for help,

? shows the help page on a function name, same as help(function)

?read.table

?? searches for help pages on functions, same as help.search(‘phrase’)

??“t test”

Information is usually returned from a function, by default this is printed to screen

read.table(‘data.tsv’)

This can always be stored, we call what it is stored in an ‘object’

mydata

here mydata is an object of type dataframe

Reminder:

• Vector: a list of numbers, equivalent to a column in a table
• Data Frame = a collection of vectors. Equivalent to a table

Hint:

• Up/Down arrow keys can be use to cycle through previous commands

Reference@http://www.datasciencecentral.com/profiles/blogs/one-page-r-a-survival-guide-to-data-science-with-r

• Templates for the Data Scientist
  1. A Template for Preparing Data: *OnePageR - *R
  2. A Template for Building Models: *OnePageR - *R
• Getting Started as a Data Scientist
  1. Getting Started with R and Rattle: *Lecture - *Laboratory
  2. Introducing and Interacting with R: *Lecture - *Laboratory
  3. BasicR - OnePage(R) - Writing R scripts
• Dealing With Data
  1. Read Data into R: *OnePageR - *R
  2. Explore and Summarise Data: *OnePageR - *R
  3. Transform Data: *OnePageR - *R
  4. Dealing with Dates and Time: (PDF, R) Dates and Time
  5. Visualising Data with GGPlot2: *OnePageR - *R
  6. Visualising Data with Maps *OnePageR - *R
  7. Spatial (R) Spatial Analysis
  8. Handling Big Data *OnePageR - *R
• Descriptive Analytics
  1. Cluster Analysis: *Lecture - *OnePageR - *R
  2. Association Analysis: *Lecture
• Predictive Analytics
  1. Decision Trees: *Lecture - *OnePageR - *R - *Rattle
  2. Ensembles of Decision Trees: *Lecture - *OnePageR - *R
  3. SVM (R)
  4. KernLab (R)
  5. NeuralNetworks (R)
  6. NNet (R)
• Model Delivery
  1. Evaluating Models: *OnePageR - *R
  2. Evaluation (R)
  3. Scoring (R)
  4. PMML (R) Exporting Models for Deployment
• Advanced Topics
  1. Text Mining: *OnePageR - *R
• Advanced R Topics
  1. Plots (PDF, R) Miscellaneous Plots
  2. Functions (PDF, R) Writing Functions in R
  3. Parallel (PDF, R) Parallel Execution
  4. Packaging (R) Pulling it Together into a Package
  5. Doing R with Style: *OnePageR - *R
  6. Literate Data Mining with KnitR: *Lecture - *OnePageR - *