Miguel D Prieto G azmigueldario

Using Git Commit Message Templates to Write Better Commit Messages

The always enthusiastic and knowledgeable mr. @jasaltvik shared with our team an article on writing (good) Git commit messages: How to Write a Git Commit Message. This excellent article explains why good Git commit messages are important, and explains what constitutes a good commit message. I wholeheartedly agree with what @cbeams writes in his article. (Have you read it yet? If not, go read it now. I'll wait.) It's sensible stuff. So I decided to start following the

	# Notes:
	# * Works for SAMN, SAME, and SAMD BioSamples (should also work for SRS/ERS format)
	# * Grabs date and location of sample isolation, host, sample source, and strain
	# * edirect tools needs to be on $PATH, or you can use my Docker image for a pre-installed version: https://hub.docker.com/r/ashedpotatoes/sranwrp/tags
	# * elink is known to randomly fail so this code doesn't use it -- however, without elink, you can't get the SRA reads (SRR/ERR/DRR) that make up a BioSample


	import subprocess

	biosamples = ["SAMEA6451356","SAMEA6451357","SAMEA6451358","SAMEA6451360","SAMEA6451361","SAMEA6451362","SAMEA6451363","SAMEA6451366","SAMEA6451367","SAMEA6451368","SAMEA6451369","SAMEA6451370","SAMEA6451371","SAMEA6451372","SAMEA6451373","SAMEA6451374","SAMEA6451375","SAMEA6451377"]

	# 0. Prep -----------------------------------------------------------------

	library(tidyverse)
	library(here)

	# 1. Load and clean EggNOG output -----------------------------------------

	## The output was downloaded from the eggnog-mapper online run.
	eggnog_go <- read_tsv(here("data", "misc", "out.emapper.annotations.gz"),
	skip = 4) %>%

	#!/usr/bin/env bash
	# make_rRNA.sh
	# Kamil Slowikowski
	# December 12, 2014
	#
	# Modified: Arindam Ghosh (July 24, 2019 )
	#
	#
	# Referenc Genome: GRCh38.p5 Ensembl release 84
	#