GROMACS conda https://bioconda.github.io/recipes/gromacs/README.html 

Address of the bookmark: http://haddock.science.uu.nl/enmr/services/GROMACS/main.php

More at https://github.com/snakemake/snakemake-wrappers

Address of the bookmark: https://snakemake-wrappers.readthedocs.io/en/stable/

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 .

Getting Started with Nextflow

Objectives Understand

What a workflow management system is.

Understand the benefits of using a workflow management system.

Explain the benefits of using Nextflow as part of your bioinformatics workflow.

Explain the components of a Nextflow script.

Run a Nextflow script.

Introduction to Bioinformatics workflows with Nextflow and nf-core

Getting Started with Nextflow

Address of the bookmark: https://carpentries-incubator.github.io/workflows-nextflow/aio/index.html

Gene expression and protein expression patterns between normal and non-normal tissues is a growing area of research that may lead to the identification of candidate genes for understanding the etiology of common, complex diseases.

Lab homepage @ http://ritchielab.psu.edu/ritchielab/

Address of the bookmark: http://www.gigasciencejournal.com/content/2/1/15?utm_content=buffer25ee0&utm_medium=social&utm_source=twitter.com&utm_campaign=buffer

Address of the bookmark: http://www.cytoscape.org/

Job Qualifications
Education and Experience
• Master Degree in Bioinformatics, Computational biology, Scientific Computing or related field
• 3-5 years of Post-Master’s experience in Bioinformatics software development
• Proven experience developing high throughput bioinformatics applications
Required Competencies
• Strong proven experience in Python programming language in Linux environment
• Proven High Performance computing experience (LSF/SGE/OGE)
• Exposure in code versioning and repository management (GIT/SVN)
• Proven experience in Bioinformatics algorithm development
• Deep understanding in Bioinformatics tools, data types
Desired Competencies
• Familiarity working in a scientific computing environment (NumPy, SciPy, Pandas etc.)
• Familiarity working with Cloud technologies (AWS, Azure)
• Ability to demonstrate solid analytical skills and exceptional attention to detail.
• Experience in relational databases and data structures
• Proven experience working with teams using agile software development methodologies and processes
• Familiarity with Service Oriented Architecture (SOA)
• Familiarity with build tools (Jenkins, make, ANT, Maven)
• Exposure to project management tools (JIRA, Confluence, RED MINE, etc.)

More at http://careers.dupont.com/jobsearch/job-details/senior-bioinformatics-software-developer/012939W-01/

AutoDock

Stochastic (GA)

Flexible ligand and partially flexible target

ArgusLab

Systematic

Flexible ligandX-Score based

DOCK

Systematic (IC)

Flexible ligandDOCK 3.5 (force field)

eHITS

Systematic (RBD of fragments followed by reconstruction)Flexible ligand and partially flexible targetHiTS_Score (empirical)

FlexX

Systematic (IC)Flexible ligandFlexX SF (empirical)Commercial

FLIPDock

Stochastic (GA)Flexible ligand and flexible targetAUTODOCK (empirical)

FRED

Systematic (RBD)Flexible ligandChemScore, PLP, ScreenScore, ChemGauss (empirical/consensus)

GOLD

Stochastic (GA)

Flexible ligand and partially flexible targetGoldScore, ChemScore (empirical), ASP (knowledge based)

ICM

Stochastic (MC)

Flexible ligand and partially flexible targetICM SF (empirical)

ParDOCK

Stochastic (MC)

RigidBAPPL (empirical)

PLANTS

Stochastic (ACO)Flexible ligand and partially flexible target

CHEMPLP, PLP (empirical)

Surflex

Systematic (IC/MA)Flexible ligandHammerhead based (empirical)

Point to note:

Several studies have shown that the performance of most docking tools is highly dependent on the particular characteristics of both the binding site and the ligand to be investigated, and the determination which method would be more suitable in a specific context is difficult. We encouraged you to check several docking methods to determine which one(s) work best for your system.

Address of the bookmark: https://github.com/PapenfussLab/gridss