jgwill commited on
Commit
c012963
·
1 Parent(s): 79f7257

@STCMastery Jupyter Book

Browse files
mynewbook/_config.yml ADDED
@@ -0,0 +1,32 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ # Book settings
2
+ # Learn more at https://jupyterbook.org/customize/config.html
3
+
4
+ title: JGT sample book no 24081618
5
+ author: The Jupyter Book Community
6
+ logo: logo.png
7
+
8
+ # Force re-execution of notebooks on each build.
9
+ # See https://jupyterbook.org/content/execute.html
10
+ execute:
11
+ execute_notebooks: force
12
+
13
+ # Define the name of the latex output file for PDF builds
14
+ latex:
15
+ latex_documents:
16
+ targetname: book.tex
17
+
18
+ # Add a bibtex file so that we can create citations
19
+ bibtex_bibfiles:
20
+ - references.bib
21
+
22
+ # Information about where the book exists on the web
23
+ repository:
24
+ url: https://github.com/executablebooks/jupyter-book # Online location of your book
25
+ path_to_book: docs # Optional path to your book, relative to the repository root
26
+ branch: master # Which branch of the repository should be used when creating links (optional)
27
+
28
+ # Add GitHub buttons to your book
29
+ # See https://jupyterbook.org/customize/config.html#add-a-link-to-your-repository
30
+ html:
31
+ use_issues_button: true
32
+ use_repository_button: true
mynewbook/_toc.yml ADDED
@@ -0,0 +1,9 @@
 
 
 
 
 
 
 
 
 
 
1
+ # Table of contents
2
+ # Learn more at https://jupyterbook.org/customize/toc.html
3
+
4
+ format: jb-book
5
+ root: intro
6
+ chapters:
7
+ - file: markdown
8
+ - file: notebooks
9
+ - file: markdown-notebooks
mynewbook/intro.md ADDED
@@ -0,0 +1,11 @@
 
 
 
 
 
 
 
 
 
 
 
 
1
+ # Welcome to your Jupyter Book
2
+
3
+ This is a small sample book to give you a feel for how book content is
4
+ structured.
5
+ It shows off a few of the major file types, as well as some sample content.
6
+ It does not go in-depth into any particular topic - check out [the Jupyter Book documentation](https://jupyterbook.org) for more information.
7
+
8
+ Check out the content pages bundled with this sample book to see more.
9
+
10
+ ```{tableofcontents}
11
+ ```
mynewbook/logo.png ADDED
mynewbook/markdown-notebooks.md ADDED
@@ -0,0 +1,53 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ ---
2
+ jupytext:
3
+ formats: md:myst
4
+ text_representation:
5
+ extension: .md
6
+ format_name: myst
7
+ format_version: 0.13
8
+ jupytext_version: 1.11.5
9
+ kernelspec:
10
+ display_name: Python 3
11
+ language: python
12
+ name: python3
13
+ ---
14
+
15
+ # Notebooks with MyST Markdown
16
+
17
+ Jupyter Book also lets you write text-based notebooks using MyST Markdown.
18
+ See [the Notebooks with MyST Markdown documentation](https://jupyterbook.org/file-types/myst-notebooks.html) for more detailed instructions.
19
+ This page shows off a notebook written in MyST Markdown.
20
+
21
+ ## An example cell
22
+
23
+ With MyST Markdown, you can define code cells with a directive like so:
24
+
25
+ ```{code-cell}
26
+ print(2 + 2)
27
+ ```
28
+
29
+ When your book is built, the contents of any `{code-cell}` blocks will be
30
+ executed with your default Jupyter kernel, and their outputs will be displayed
31
+ in-line with the rest of your content.
32
+
33
+ ```{seealso}
34
+ Jupyter Book uses [Jupytext](https://jupytext.readthedocs.io/en/latest/) to convert text-based files to notebooks, and can support [many other text-based notebook files](https://jupyterbook.org/file-types/jupytext.html).
35
+ ```
36
+
37
+ ## Create a notebook with MyST Markdown
38
+
39
+ MyST Markdown notebooks are defined by two things:
40
+
41
+ 1. YAML metadata that is needed to understand if / how it should convert text files to notebooks (including information about the kernel needed).
42
+ See the YAML at the top of this page for example.
43
+ 2. The presence of `{code-cell}` directives, which will be executed with your book.
44
+
45
+ That's all that is needed to get started!
46
+
47
+ ## Quickly add YAML metadata for MyST Notebooks
48
+
49
+ If you have a markdown file and you'd like to quickly add YAML metadata to it, so that Jupyter Book will treat it as a MyST Markdown Notebook, run the following command:
50
+
51
+ ```
52
+ jupyter-book myst init path/to/markdownfile.md
53
+ ```
mynewbook/markdown.md ADDED
@@ -0,0 +1,55 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ # Markdown Files
2
+
3
+ Whether you write your book's content in Jupyter Notebooks (`.ipynb`) or
4
+ in regular markdown files (`.md`), you'll write in the same flavor of markdown
5
+ called **MyST Markdown**.
6
+ This is a simple file to help you get started and show off some syntax.
7
+
8
+ ## What is MyST?
9
+
10
+ MyST stands for "Markedly Structured Text". It
11
+ is a slight variation on a flavor of markdown called "CommonMark" markdown,
12
+ with small syntax extensions to allow you to write **roles** and **directives**
13
+ in the Sphinx ecosystem.
14
+
15
+ For more about MyST, see [the MyST Markdown Overview](https://jupyterbook.org/content/myst.html).
16
+
17
+ ## Sample Roles and Directives
18
+
19
+ Roles and directives are two of the most powerful tools in Jupyter Book. They
20
+ are like functions, but written in a markup language. They both
21
+ serve a similar purpose, but **roles are written in one line**, whereas
22
+ **directives span many lines**. They both accept different kinds of inputs,
23
+ and what they do with those inputs depends on the specific role or directive
24
+ that is being called.
25
+
26
+ Here is a "note" directive:
27
+
28
+ ```{note}
29
+ Here is a note
30
+ ```
31
+
32
+ It will be rendered in a special box when you build your book.
33
+
34
+ Here is an inline directive to refer to a document: {doc}`markdown-notebooks`.
35
+
36
+
37
+ ## Citations
38
+
39
+ You can also cite references that are stored in a `bibtex` file. For example,
40
+ the following syntax: `` {cite}`holdgraf_evidence_2014` `` will render like
41
+ this: {cite}`holdgraf_evidence_2014`.
42
+
43
+ Moreover, you can insert a bibliography into your page with this syntax:
44
+ The `{bibliography}` directive must be used for all the `{cite}` roles to
45
+ render properly.
46
+ For example, if the references for your book are stored in `references.bib`,
47
+ then the bibliography is inserted with:
48
+
49
+ ```{bibliography}
50
+ ```
51
+
52
+ ## Learn more
53
+
54
+ This is just a simple starter to get you started.
55
+ You can learn a lot more at [jupyterbook.org](https://jupyterbook.org).
mynewbook/notebooks.ipynb ADDED
The diff for this file is too large to render. See raw diff
 
mynewbook/references.bib ADDED
@@ -0,0 +1,56 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ ---
2
+ ---
3
+
4
+ @inproceedings{holdgraf_evidence_2014,
5
+ address = {Brisbane, Australia, Australia},
6
+ title = {Evidence for {Predictive} {Coding} in {Human} {Auditory} {Cortex}},
7
+ booktitle = {International {Conference} on {Cognitive} {Neuroscience}},
8
+ publisher = {Frontiers in Neuroscience},
9
+ author = {Holdgraf, Christopher Ramsay and de Heer, Wendy and Pasley, Brian N. and Knight, Robert T.},
10
+ year = {2014}
11
+ }
12
+
13
+ @article{holdgraf_rapid_2016,
14
+ title = {Rapid tuning shifts in human auditory cortex enhance speech intelligibility},
15
+ volume = {7},
16
+ issn = {2041-1723},
17
+ url = {http://www.nature.com/doifinder/10.1038/ncomms13654},
18
+ doi = {10.1038/ncomms13654},
19
+ number = {May},
20
+ journal = {Nature Communications},
21
+ author = {Holdgraf, Christopher Ramsay and de Heer, Wendy and Pasley, Brian N. and Rieger, Jochem W. and Crone, Nathan and Lin, Jack J. and Knight, Robert T. and Theunissen, Frédéric E.},
22
+ year = {2016},
23
+ pages = {13654},
24
+ file = {Holdgraf et al. - 2016 - Rapid tuning shifts in human auditory cortex enhance speech intelligibility.pdf:C\:\\Users\\chold\\Zotero\\storage\\MDQP3JWE\\Holdgraf et al. - 2016 - Rapid tuning shifts in human auditory cortex enhance speech intelligibility.pdf:application/pdf}
25
+ }
26
+
27
+ @inproceedings{holdgraf_portable_2017,
28
+ title = {Portable learning environments for hands-on computational instruction using container-and cloud-based technology to teach data science},
29
+ volume = {Part F1287},
30
+ isbn = {978-1-4503-5272-7},
31
+ doi = {10.1145/3093338.3093370},
32
+ abstract = {© 2017 ACM. There is an increasing interest in learning outside of the traditional classroom setting. This is especially true for topics covering computational tools and data science, as both are challenging to incorporate in the standard curriculum. These atypical learning environments offer new opportunities for teaching, particularly when it comes to combining conceptual knowledge with hands-on experience/expertise with methods and skills. Advances in cloud computing and containerized environments provide an attractive opportunity to improve the effciency and ease with which students can learn. This manuscript details recent advances towards using commonly-Available cloud computing services and advanced cyberinfrastructure support for improving the learning experience in bootcamp-style events. We cover the benets (and challenges) of using a server hosted remotely instead of relying on student laptops, discuss the technology that was used in order to make this possible, and give suggestions for how others could implement and improve upon this model for pedagogy and reproducibility.},
33
+ booktitle = {{ACM} {International} {Conference} {Proceeding} {Series}},
34
+ author = {Holdgraf, Christopher Ramsay and Culich, A. and Rokem, A. and Deniz, F. and Alegro, M. and Ushizima, D.},
35
+ year = {2017},
36
+ keywords = {Teaching, Bootcamps, Cloud computing, Data science, Docker, Pedagogy}
37
+ }
38
+
39
+ @article{holdgraf_encoding_2017,
40
+ title = {Encoding and decoding models in cognitive electrophysiology},
41
+ volume = {11},
42
+ issn = {16625137},
43
+ doi = {10.3389/fnsys.2017.00061},
44
+ abstract = {© 2017 Holdgraf, Rieger, Micheli, Martin, Knight and Theunissen. Cognitive neuroscience has seen rapid growth in the size and complexity of data recorded from the human brain as well as in the computational tools available to analyze this data. This data explosion has resulted in an increased use of multivariate, model-based methods for asking neuroscience questions, allowing scientists to investigate multiple hypotheses with a single dataset, to use complex, time-varying stimuli, and to study the human brain under more naturalistic conditions. These tools come in the form of “Encoding” models, in which stimulus features are used to model brain activity, and “Decoding” models, in which neural features are used to generated a stimulus output. Here we review the current state of encoding and decoding models in cognitive electrophysiology and provide a practical guide toward conducting experiments and analyses in this emerging field. Our examples focus on using linear models in the study of human language and audition. We show how to calculate auditory receptive fields from natural sounds as well as how to decode neural recordings to predict speech. The paper aims to be a useful tutorial to these approaches, and a practical introduction to using machine learning and applied statistics to build models of neural activity. The data analytic approaches we discuss may also be applied to other sensory modalities, motor systems, and cognitive systems, and we cover some examples in these areas. In addition, a collection of Jupyter notebooks is publicly available as a complement to the material covered in this paper, providing code examples and tutorials for predictive modeling in python. The aimis to provide a practical understanding of predictivemodeling of human brain data and to propose best-practices in conducting these analyses.},
45
+ journal = {Frontiers in Systems Neuroscience},
46
+ author = {Holdgraf, Christopher Ramsay and Rieger, J.W. and Micheli, C. and Martin, S. and Knight, R.T. and Theunissen, F.E.},
47
+ year = {2017},
48
+ keywords = {Decoding models, Encoding models, Electrocorticography (ECoG), Electrophysiology/evoked potentials, Machine learning applied to neuroscience, Natural stimuli, Predictive modeling, Tutorials}
49
+ }
50
+
51
+ @book{ruby,
52
+ title = {The Ruby Programming Language},
53
+ author = {Flanagan, David and Matsumoto, Yukihiro},
54
+ year = {2008},
55
+ publisher = {O'Reilly Media}
56
+ }
mynewbook/requirements.txt ADDED
@@ -0,0 +1,3 @@
 
 
 
 
1
+ jupyter-book
2
+ matplotlib
3
+ numpy