diff --git a/.nojekyll b/.nojekyll
index eae8457..781e6b3 100644
--- a/.nojekyll
+++ b/.nojekyll
@@ -1 +1 @@
-da158a0f
\ No newline at end of file
+2c65db0e
\ No newline at end of file
diff --git a/about.html b/about.html
index ca45f88..00b9989 100644
--- a/about.html
+++ b/about.html
@@ -90,6 +90,9 @@
+
diff --git a/search.json b/search.json
index 5e6f71e..89da94e 100644
--- a/search.json
+++ b/search.json
@@ -14,11 +14,18 @@
"text": "\\[\n\\newcommand{\\trans}{^\\mathsf{T}}\n\\newcommand{\\eps}{\\epsilon}\n\\]"
},
{
- "objectID": "unit1.html",
- "href": "unit1.html",
- "title": "Unit 1: Intro",
+ "objectID": "index.html",
+ "href": "index.html",
+ "title": "Data 100: Principles and Techniques of Data Science",
"section": "",
- "text": "An example of adding a styled div via html.\n\nThis content can be styled via the border class.\n\nAn example of an evaluated Python code chunk.\n\nimport numpy as np\nnp.mean(np.random.normal(size=100))\n\n0.029715716344917712\n\n\n\\[\n\\theta = \\int_0^\\infty f(x,\\theta)d\\theta\n\\]\nUse a \\(\\LaTeX\\) macro.\n\\[\nA = X \\trans Y\n\\]"
+ "text": "Note: DS100/fa23 has a div with templating for the instructors."
+ },
+ {
+ "objectID": "index.html#schedule",
+ "href": "index.html#schedule",
+ "title": "Data 100: Principles and Techniques of Data Science",
+ "section": "Schedule",
+ "text": "Schedule\nNote: DS100 uses templating to fill out the schedule. Here we use Quarto’s EJS templating.\nWe’d like to be able to define custom html classes for the buttons below (presumably in CSS style file)\n\nA templated schedule\nThe templating is basically working in terms of filling in values in the schedule.ejs file based on a schedule.yml file. I’m not sure how to apply the style for the module class (see styles.css) to mimic the styling in the DS100 page.\n\nWeek 1\n\n\n Aug 24:\n \n \n Lecture 1 Introduction\n \n Note 1\n \n\n \n Lecture participation 1 Lecture Participation 1\n\n Aug 25:\n \n Lab 1 Prerequisite Coding (due Aug 29)\n\n \n Homework 1A Plotting and Permutation Test (due Aug 31)\n\n \n Homework 1B Prerequisite Math (due Aug 31)\n\n \n \nWeek 2\n\n\n Aug 29:\n \n Lecture 1 Pandas 1\n\n \n Lecture participation 1 Lecture Participation 2\n\n \n \n\nNo matching items\n\n\n\n\nA manual schedule\nWeek 1\n\n\n\nAug 24:\nLecture 1 Introduction\nNote 1, Note 2, Recording\n\n\n\nLecture Participation 1 Lecture Participation 1\n\n\n\nAug 25:\nLab 1 Prereq coding"
},
{
"objectID": "syllabus.html",
@@ -35,18 +42,32 @@
"text": "About Data 100\nCombining data, computation, and inferential thinking, data science is redefining how people and organizations solve challenging problems and understand their world. This intermediate level class bridges between Data 8 and upper division computer science and statistics courses as well as methods courses in other fields. In this class, we explore key areas of data science including question formulation, data collection and cleaning, visualization, statistical inference, predictive modeling, and decision making. Through a strong emphasis on data centric computing, quantitative critical thinking, and exploratory data analysis, this class covers key principles and techniques of data science. These include languages for transforming, querying and analyzing data; algorithms for machine learning methods including regression, classification and clustering; principles behind creating informative data visualizations; statistical concepts of measurement error and prediction; and techniques for scalable data processing.\n\nGoals\n\nPrepare students for advanced Berkeley courses in data-management, machine learning, and statistics, by providing the necessary foundation and context.\nEnable students to start careers as data scientists by providing experience working with real-world data, tools, and techniques.\nEmpower students to apply computational and inferential thinking to address real-world problems.\n\n\n\nPrerequisites\nWhile we are working to make this class widely accessible, we currently require the following (or equivalent) prerequisites. Prerequisites will be enforced in Data 100. It is your responsibility to know the material in the prerequisites."
},
{
- "objectID": "index.html",
- "href": "index.html",
- "title": "Data 100: Principles and Techniques of Data Science",
+ "objectID": "unit2.html",
+ "href": "unit2.html",
+ "title": "Unit 2: next",
"section": "",
- "text": "Note: DS100/fa23 has a div with templating for the instructors.\nStyling text (not sure why closer to letters than in DS100)."
+ "text": "This is an example of using an ipynb file as source rather than qmd. It follows instructions from https://github.com/DS-100/course-notes/README.md."
},
{
- "objectID": "index.html#schedule",
- "href": "index.html#schedule",
- "title": "Data 100: Principles and Techniques of Data Science",
- "section": "Schedule",
- "text": "Schedule\nNote: DS100 uses templating to fill out the schedule. Here we use Quarto’s EJS templating.\nWe’d like to be able to define custom html classes for the buttons below (presumably in CSS style file)\n\nA templated schedule\nThe templating is basically working in terms of filling in values in the schedule.ejs file based on a schedule.yml file. I’m not sure how to apply the style for the module class (see styles.css) to mimic the styling in the DS100 page.\n\nWeek 1\n\n\n Aug 24:\n \n \n Lecture 1 Introduction\n \n Note 1\n \n\n \n Lecture participation 1 Lecture Participation 1\n\n Aug 25:\n \n Lab 1 Prerequisite Coding (due Aug 29)\n\n \n Homework 1A Plotting and Permutation Test (due Aug 31)\n\n \n Homework 1B Prerequisite Math (due Aug 31)\n\n \n \nWeek 2\n\n\n Aug 29:\n \n Lecture 1 Pandas 1\n\n \n Lecture participation 1 Lecture Participation 2\n\n \n \n\nNo matching items\n\n\n\n\nA manual schedule\nWeek 1\n\n\n\nAug 24:\nLecture 1 Introduction\nNote 1, Note 2, Recording\n\n\n\nLecture Participation 1 Lecture Participation 1\n\n\n\nAug 25:\nLab 1 Prereq coding"
+ "objectID": "unit2.html#title",
+ "href": "unit2.html#title",
+ "title": "Unit 2: next",
+ "section": "Title",
+ "text": "Title\nHere is some \\(\\LaTeX\\). \\[\n\\theta = 7\n\\]\nHere is some code. Note that to get code output shown, the underlying notebook must have executed the code.\n\n\nCode\na=7\nprint(a)\n\n\n7\n\n\n\n\n\n\n\n\nTip with Title\n\n\n\nThis is an example of a callout with a title."
+ },
+ {
+ "objectID": "unit1.html",
+ "href": "unit1.html",
+ "title": "Unit 1: Intro",
+ "section": "",
+ "text": "$$\n\\newcommand{\\trans}{^\\mathsf{T}} \n\\newcommand{\\eps}{\\epsilon}\n$$\n\n\n\nThis is an example of using qmd as the source document.\nAn example of an evaluated Python code chunk.\n\n\nCode\nimport numpy as np\nnp.mean(np.random.normal(size=100))\n\n\n-0.06841232200621428\n\n\n\\[\n\\theta = \\int_0^\\infty f(x,\\theta)d\\theta\n\\]\nUse a \\(\\LaTeX\\) macro. (Note: need to look back at this as having include-before-body in the yaml causes extra space at top of page.)\n\\[\nA = X \\trans Y\n\\]\nAn example of adding a styled div via html.\n\nThis content can be styled via the border class.\n\n\n\n\n\n\n\nTip with Title\n\n\n\nThis is an example of a callout with a title.\n\n\nHere’s a tabset\n\nRPython\n\n\nfizz_buzz <- function(fbnums = 1:50) {\n output <- dplyr::case_when(\n fbnums %% 15 == 0 ~ \"FizzBuzz\",\n fbnums %% 3 == 0 ~ \"Fizz\",\n fbnums %% 5 == 0 ~ \"Buzz\",\n TRUE ~ as.character(fbnums)\n )\n print(output)\n}\n\nfizz_buzz(3)\n\n\n\n\nCode\ndef fizz_buzz(num):\n if num % 15 == 0:\n print(\"FizzBuzz\")\n elif num % 5 == 0:\n print(\"Buzz\")\n elif num % 3 == 0:\n print(\"Fizz\")\n else:\n print(num)\n \nfizz_buzz(3)\n\n\nFizz"
+ },
+ {
+ "objectID": "unit3.html",
+ "href": "unit3.html",
+ "title": "Unit 3: more",
+ "section": "",
+ "text": "$$\n\\newcommand{\\trans}{^\\mathsf{T}} \n\\newcommand{\\eps}{\\epsilon}\n$$\n\n\n\nThis is an example of using qmd as the source document with pdf as one target. I’ve taken out the qmd stuff that doesn’t seem to render to pdf.\nAn example of an evaluated Python code chunk.\n\n\nCode\nimport numpy as np\nnp.mean(np.random.normal(size=100))\n\n\n0.0779802879353334\n\n\n\\[\n\\theta = \\int_0^\\infty f(x,\\theta)d\\theta\n\\]\n(Note: need to look back at this as having include-before-body in the yaml causes extra space at top of page.)\n\\[\nA = X \\trans Y\n\\]"
},
{
"objectID": "calendar.html",
diff --git a/sitemap.xml b/sitemap.xml
index 23fb5ec..d344dc2 100644
--- a/sitemap.xml
+++ b/sitemap.xml
@@ -2,26 +2,34 @@
https://berkeley-scf.github.io/stat999-quarto/about.html
- 2023-10-12T19:14:37.207Z
+ 2023-10-12T23:33:17.144Zhttps://berkeley-scf.github.io/stat999-quarto/macros.html
- 2023-10-12T19:14:36.675Z
+ 2023-10-12T23:33:16.596Z
- https://berkeley-scf.github.io/stat999-quarto/unit1.html
- 2023-10-12T19:14:36.035Z
+ https://berkeley-scf.github.io/stat999-quarto/index.html
+ 2023-10-12T23:33:00.273Zhttps://berkeley-scf.github.io/stat999-quarto/syllabus.html
- 2023-10-12T19:14:28.071Z
+ 2023-10-12T23:32:51.145Z
- https://berkeley-scf.github.io/stat999-quarto/index.html
- 2023-10-12T19:14:36.415Z
+ https://berkeley-scf.github.io/stat999-quarto/unit2.html
+ 2023-10-12T23:32:50.537Z
+
+
+ https://berkeley-scf.github.io/stat999-quarto/unit1.html
+ 2023-10-12T23:32:59.877Z
+
+
+ https://berkeley-scf.github.io/stat999-quarto/unit3.html
+ 2023-10-12T23:33:16.312Zhttps://berkeley-scf.github.io/stat999-quarto/calendar.html
- 2023-10-12T19:14:36.943Z
+ 2023-10-12T23:33:16.880Z
diff --git a/syllabus.html b/syllabus.html
index 1a1b362..40ab46b 100644
--- a/syllabus.html
+++ b/syllabus.html
@@ -90,6 +90,9 @@
+
---
+title: "Unit 1: Intro"
+format:
+ html:
+ code-fold: show
+ code-tools: true
+ include-before-body:
+ - file: macros.md
+---
+
+This is an example of using qmd as the source document.
+
+
+An example of an evaluated Python code chunk.
+
+```{python}
+import numpy as np
+np.mean(np.random.normal(size=100))
+```
+
+$$
+\theta = \int_0^\infty f(x,\theta)d\theta
+$$
+
+Use a $\LaTeX$ macro.
+(Note: need to look back at this as having `include-before-body` in the yaml causes extra space at top of page.)
+
+$$
+A = X \trans Y
+$$
+
+An example of adding a styled div via html.
+
+::: {.border}
+This content can be styled via the border class.
+:::
+
+::: {.callout-tip}
+## Tip with Title
+
+This is an example of a callout with a title.
+:::
+
+Here's a tabset
+
+::: {.panel-tabset}
+## R
+
+```{.r}
+fizz_buzz <-function(fbnums =1:50) {
+ output <- dplyr::case_when(
+ fbnums %%15==0~"FizzBuzz",
+ fbnums %%3==0~"Fizz",
+ fbnums %%5==0~"Buzz",
+TRUE~as.character(fbnums)
+ )
+print(output)
+}
+
+fizz_buzz(3)
+```
+
+## Python
+
+```{python}
+def fizz_buzz(num):
+if num %15==0:
+print("FizzBuzz")
+elif num %5==0:
+print("Buzz")
+elif num %3==0:
+print("Fizz")
+else:
+print(num)
+
+fizz_buzz(3)
+```
+
+:::
+
This is an example of using qmd as the source document with pdf as one target. I’ve taken out the qmd stuff that doesn’t seem to render to pdf.
+
An example of an evaluated Python code chunk.
+
+
+Code
+
import numpy as np
+np.mean(np.random.normal(size=100))
+
+
+
0.0779802879353334
+
+
+
\[
+\theta = \int_0^\infty f(x,\theta)d\theta
+\]
+
(Note: need to look back at this as having include-before-body in the yaml causes extra space at top of page.)
+
\[
+A = X \trans Y
+\]
+
+
+
+
+
+
+
Source Code
+
---
+title: "Unit 3: more"
+format:
+ html:
+ code-fold: show
+ code-tools: true
+ include-before-body:
+ - file: macros.md
+ pdf:
+ include-before-body:
+ - file: macros.tex
+---
+
+This is an example of using qmd as the source document with pdf as one target. I've taken out the qmd stuff that doesn't seem to render to pdf.
+
+
+An example of an evaluated Python code chunk.
+
+```{python}
+import numpy as np
+np.mean(np.random.normal(size=100))
+```
+
+$$
+\theta = \int_0^\infty f(x,\theta)d\theta
+$$
+
+
+(Note: need to look back at this as having `include-before-body` in the yaml causes extra space at top of page.)
+
+$$
+A = X \trans Y
+$$
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/unit3.pdf b/unit3.pdf
new file mode 100644
index 0000000..fa1e7c4
Binary files /dev/null and b/unit3.pdf differ
