Last updated: 2019-03-31
Checks: 6 0
Knit directory: fiveMinuteStats/analysis/
This reproducible R Markdown analysis was created with workflowr (version 1.2.0). The Report tab describes the reproducibility checks that were applied when the results were created. The Past versions tab lists the development history.
Great! Since the R Markdown file has been committed to the Git repository, you know the exact version of the code that produced these results.
Great job! The global environment was empty. Objects defined in the global environment can affect the analysis in your R Markdown file in unknown ways. For reproduciblity it’s best to always run the code in an empty environment.
The command set.seed(12345) was run prior to running the code in the R Markdown file. Setting a seed ensures that any results that rely on randomness, e.g. subsampling or permutations, are reproducible.
Great job! Recording the operating system, R version, and package versions is critical for reproducibility.
Nice! There were no cached chunks for this analysis, so you can be confident that you successfully produced the results during this run.
Great! You are using Git for version control. Tracking code development and connecting the code version to the results is critical for reproducibility. The version displayed above was the version of the Git repository at the time these results were generated.
Note that you need to be careful to ensure that all relevant files for the analysis have been committed to Git prior to generating the results (you can use wflow_publish or wflow_git_commit). workflowr only checks the R Markdown file, but you know if there are other scripts or data files that it depends on. Below is the status of the Git repository when the results were generated:
Ignored files:
Ignored: .Rhistory
Ignored: .Rproj.user/
Ignored: analysis/.Rhistory
Ignored: analysis/bernoulli_poisson_process_cache/
Untracked files:
Untracked: _workflowr.yml
Untracked: analysis/CI.Rmd
Untracked: analysis/gibbs_structure.Rmd
Untracked: analysis/libs/
Untracked: analysis/results.Rmd
Untracked: analysis/shiny/tester/
Untracked: docs/MH_intro_files/
Untracked: docs/citations.bib
Untracked: docs/figure/MH_intro.Rmd/
Untracked: docs/figure/hmm.Rmd/
Untracked: docs/hmm_files/
Untracked: docs/libs/
Untracked: docs/shiny/tester/
Note that any generated files, e.g. HTML, png, CSS, etc., are not included in this status report because it is ok for generated content to have uncommitted changes.
These are the previous versions of the R Markdown and HTML files. If you’ve configured a remote Git repository (see ?wflow_git_remote), click on the hyperlinks in the table below to view them.
| File | Version | Author | Date | Message |
|---|---|---|---|---|
| html | c26499b | stephens999 | 2017-04-24 | Build site. |
| Rmd | ebc0b7a | stephens999 | 2017-04-24 | Files commited by wflow_commit. |
| html | 723317b | stephens999 | 2017-04-17 | Build site. |
| Rmd | 335d169 | stephens999 | 2017-04-17 | Files commited by wflow_commit. |
| Rmd | d6d38ff | stephens999 | 2017-04-17 | Files commited by wflow_commit. |
You should know what a \(p\) value is.
A key problem with \(p\) values, when testing null hypotheses, is that they can be difficult to calibrate. That is, it is hard to answer the question “If I get a \(p\)-value of 0.01 (or any other number) how strong is the evidence against the null hypothesis?”
Here we just give a simple (but artificial) example of an test in which a \(p\) value of 0.01 actually corresponds to evidence for the null, even though 0.01 is usually considered to be strong evidence against the null. (This example is modified from the book Bayesian Analysis, by J Berger, p25.)
Suppose \(x \in \{1,2,3\}\) and \(\theta \in \{0,1\}\) with
| x | 1 | 2 | 3 |
|---|---|---|---|
| \(p(x | \theta=0)\) | 0.005 | 0.005 | 0.99 |
| \(p(x | \theta=1)\) | 0.999 | 0.001 | 0 |
Note that the likelihood ratios for \(H_1\) vs \(H_0\) for \(x=1,2,3\) are \(999/5, 1/5\) and \(0\) respectively. So as \(x\) increases the evidence against \(H_0\) decreases.
Now, let us suppose that we observe \(x=2\). Then by definition the \(p\) value for this observation is \[p:= \Pr(\text{we would see evidence as strong or stronger against $H_0$ than $x=2$} | \theta=0).\]
Here “evidence as strong or stronger against \(H_0\) than \(x=2\)” is \(x \in \{1,2\}\). And the probability of this under \(H_0\) is \[\Pr(x \in \{1,2\} | H_0) = 0.005+0.005 = 0.01.\]
So the \(p\) value for \(x=2\) is 0.01.
And yet, the observation \(x=2\) is 5 times more probable under \(H_0\) than under \(H_1\)! So \(x=2\) has \(p\) value 0.01 but is actually evidence for \(H_0\).
This example is obviously contrived to make a point: so it only demonstrates that it is possible to contrive a situation where \(p=0.01\) corresponds to evidence for \(H_0\).
However, given this it seems natural to ask: in “typical” situations, does \(p=0.01\) correspond to evidence for or against \(H_0\)? Of course, the answer to this depends on what one views as “typical”. For a start towards answering this question see here.
sessionInfo()R version 3.5.2 (2018-12-20)
Platform: x86_64-apple-darwin15.6.0 (64-bit)
Running under: macOS Mojave 10.14.1
Matrix products: default
BLAS: /Library/Frameworks/R.framework/Versions/3.5/Resources/lib/libRblas.0.dylib
LAPACK: /Library/Frameworks/R.framework/Versions/3.5/Resources/lib/libRlapack.dylib
locale:
[1] en_US.UTF-8/en_US.UTF-8/en_US.UTF-8/C/en_US.UTF-8/en_US.UTF-8
attached base packages:
[1] stats graphics grDevices utils datasets methods base
loaded via a namespace (and not attached):
[1] workflowr_1.2.0 Rcpp_1.0.0 digest_0.6.18 rprojroot_1.3-2
[5] backports_1.1.3 git2r_0.24.0 magrittr_1.5 evaluate_0.12
[9] highr_0.7 stringi_1.2.4 fs_1.2.6 whisker_0.3-2
[13] rmarkdown_1.11 tools_3.5.2 stringr_1.3.1 glue_1.3.0
[17] xfun_0.4 yaml_2.2.0 compiler_3.5.2 htmltools_0.3.6
[21] knitr_1.21 This site was created with R Markdown