https://github.com/davidwhogg/DataAnalysisRecipes

chapters of a book Hogg will never write
https://github.com/davidwhogg/DataAnalysisRecipes

Last synced: about 1 month ago
JSON representation

chapters of a book Hogg will never write

• Host: GitHub
• URL: https://github.com/davidwhogg/DataAnalysisRecipes
• Owner: davidwhogg
• Created: 2012-03-11T17:14:45.000Z (almost 13 years ago)
• Default Branch: master
• Last Pushed: 2023-01-02T23:18:52.000Z (almost 2 years ago)
• Last Synced: 2024-10-16T01:29:07.258Z (about 2 months ago)
• Language: TeX
• Homepage:
• Size: 3.91 MB
• Stars: 89
• Watchers: 25
• Forks: 20
• Open Issues: 22
• Metadata Files:
  • Readme: README.md

Awesome Lists containing this project

• awesome-astrodata - A textbook Hogg will never write

README

        
# Data Analysis Recipes

Chapters from Hogg's non-existent book.

### Authors: ###

(Contributions have come from all of the following.)

* **David W. Hogg**, New York University

* **Jo Bovy**, Institute for Advanced Study

* **Dan Foreman-Mackey**, University of Washington

* **Dustin Lang**, Princeton University

### License: ###

**Copyright 2010, 2011, 2012, 2013, 2014, 2015, 2016 the authors.  All rights reserved.**

If you have interest in using or re-using any of this content, get in

touch with Hogg.

### Style notes: ###

- *tentative:* use "pdf" not "PDF".

- When at the end of the sentence, put the `\note` after the period,

  but when at the end of a phrase, put the `\note` before the comma or

  parenthesis.

- Make sure the endnotes can be read on their own, outside of context.

- Be careful with the words "error", "uncertainty", "probability",

  "frequency", "likelihood".

- Use `()` for function arguments, and `[]` for grouping/precedence.

- Define macros; remember "1, 2, infinity".

- Put new terms in `\emph{}`, put only referred-to words in quotation marks.

- Do in-text itemized lists with `\textsl{(a)}~` and so on.

### Git migration notes: ###

When I want to import stuff from the old SVN repository, I do the

following:

1. I create a new github repository called `foo` and follow the svn

   import instructions.

2. I `git clone` that repository and do things like move the files into

   a directory structure that won't conflict with the current

   structure, like:

        cd

        git clone [email protected]:davidwhogg/foo.git

        cd foo

        mkdir straightline

        git add straightline # I think this is maybe needed?

        git mv *.pdf straightline

        # etc

        # . . .

        git commit -a -m "fixed up directory structure"

        git push

3. I make a subtree merge or something like that (I am new to all this)

   like so:

        cd

        cd DataAnalysisRecipes

        git pull # to get up-to-date

        git remote add foo [email protected]:davidwhogg/foo.git

        git fetch foo

        git merge foo/master

        git push

4. Then I delete the `foo` repo from github so as not to confuse myself.