Description for and list of popular special files like README/CHANGELOG/LICENSE and others.
The ReadMe is usually the first document people will see of your project. Depending on your project it should give a short introduction and usage/build examples. It should only contain the information you expect users to read. It is usually possible to link to other documentation files using the markdown syntax which gets rendered as html by popular repository hosting platforms.
| # Detecting correlation | |
| # Defines three functions using base R to illustrate techniques for identifying correlations | |
| # between continuous random variables, then tests against different types of data | |
| # Pearsons r, distance correlation, Maximal Information Coefficient (approximated) | |
| # A simple bootstrap function to estimate confidence intervals | |
| bootstrap <- function(x,y,func,reps,alpha){ | |
| estimates <- c() |
| # see https://www.topbug.net/blog/2013/04/14/install-and-use-gnu-command-line-tools-in-mac-os-x/ | |
| # core | |
| brew install coreutils | |
| # key commands | |
| brew install binutils | |
| brew install diffutils | |
| brew install ed --default-names | |
| brew install findutils --with-default-names |
Project Euler Sprint Hack Nights are beginner friendly events where you can work on your own projects or engage in a friendly competition called the Project Euler Sprint.
The Project Euler Sprint is a friendly competition involving solving Project Euler ([http://projecteuler.net][projecteuler]) problems for points. Project Euler is a series of increasingly difficult computational math problems that must be solved with code (generally speaking - we've had some impressive solutions in pen and paper as well as on an Excel spreadsheet).
Each problem is harder than the last, so each problem is worth its problem number in points. Problem #1 is easy, so it's worth 1 point, while problem #50 is much harder, but worth 50 points. You can form teams of 4 people and solutions can be in any language as long as it's coded there. More detailed rules below.
| #!/bin/bash | |
| #------------------------------------------------------------------------------ | |
| # Name: sbtmkdirs | |
| # Version: 1.5 | |
| # Purpose: Create an SBT project directory structure with a few simple options. | |
| # Author: Alvin Alexander, http://alvinalexander.com | |
| # License: Creative Commons Attribution-ShareAlike 2.5 Generic | |
| # http://creativecommons.org/licenses/by-sa/2.5/ | |
| #------------------------------------------------------------------------------ |
