gabriel
/
my-datascience-cookiecutter
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
35 Commits
1 Branch
0 Tags
299 KiB
 
 
 
Tree: ad96dfc6f1
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from 'ad96dfc6f1'
${ noResults }
Peter Bull ad96dfc6f1
Documentation updates! 		9 years ago
docs Documentation updates! 9 years ago
{{ cookiecutter.repo_name }} Fix missing imports 9 years ago
.gitattributes Start to flesh out READMEs 9 years ago
.gitignore Initial docs commit 9 years ago
README.md Add cookiecutter dependency version 9 years ago
cookiecutter.json Stupidest part of the JSON spec. 9 years ago
requirements.txt Initial docs commit 9 years ago

README.md

cookiecutter-data-science

An opinionated, but not-afraid-to-be-wrong project template for data science projects. Pull requests welcome. Debate encouraged.

Requirements to create project:

To start a new project:

cookiecutter https://github.com/drivendata/cookiecutter-data-science

asciicast

Data

** By default, the data folder is included in the .gitignore file.** If you have a small amount of data that rarely changes, you may want to include the data in the repository. Github currently warns if files are over 50MB and rejects files over 100MB. Some other options for storing large data include AWS S3 with a syncing tool (e.g., s3cmd), Git Large File Storage, Git Annex, and dat.

The prefered workflow if data is not in the repository is to have a make command make data that will download or create the relevant datasets.