Small content updates.

Author: jtkiley

notebooks/0b_anaconda.ipynb

@@ -506,8 +506,8 @@
     "1. The cell structure is flexible, but it will allow you to do things out of order, and anything you import or assign is still there, even if you change the code. To avoid this issue:\n",
     "    1. Purposefully try to keep your code in the order that it should be run.\n",
     "    1. Periodically, use \"Restart Kernel and Run All Cells...\" to make sure that your notebook runs in order.\n",
-    "1. It is not ideal for version controlled environments like Github. If you want to version control projects, you may find yourself moving code into `.py` files and using Jupyter for prototyping. Otherwise, this may not be a big concern.\n",
-    "1. It is not a good format for a manuscript (unlike [R notebooks](https://bookdown.org/yihui/rmarkdown/notebook.html)). However, it is much more capable.\n",
+    "1. It is not ideal for version controlled environments like Github. If you want to version control projects, you may find yourself moving code into `.py` files and using Jupyter for prototyping, or you might remove cell outputs before committing (like the course resposity does). Otherwise, this may not be a big concern.\n",
+    "1. It is not a good format for a manuscript (unlike [R notebooks](https://bookdown.org/yihui/rmarkdown/notebook.html)). However, it is much more capable. For something more like R notebooks, [Quarto](https://quarto.org) is shaping up to be a high-quality Python alternative.\n",
     "\n",
     "Overall, the Jupyter notebook is a great tool.\n",
     "Once you have some experience using them, you may find them fairly natural to work with."
@@ -615,7 +615,7 @@
    "name": "python",
    "nbconvert_exporter": "python",
    "pygments_lexer": "ipython3",
-   "version": "3.11.3"
+   "version": "3.11.4"
   },
   "vscode": {
    "interpreter": {

notebooks/1a_python2.ipynb

@@ -47,6 +47,22 @@
     "    return (temp_f - 32) * 5 / 9"
    ]
   },
+  {
+   "cell_type": "markdown",
+   "metadata": {},
+   "source": [
+    "There are names for the parts of a function.\n",
+    "\n",
+    "- **Defining a function.** We use the keyword `def` to define a function.\n",
+    "- **Function name.** Following the `def` keyword, we give the function a name. In this example, it is `f_to_c`.\n",
+    "- **Parameter(s).** After the name, we have a set of parentheses that contains zero or more parameters. This is how we define what the function expects as input.\n",
+    "- **Argument(s).** When we call the function after defining it, the values to pass in to the parameters are called the arguments. You will sometimes hear \"parameters\" and \"arguments\" used interchangeably (including from me; old habits die hard), but they are technically distinct.\n",
+    "- **Body.** After the colon, we indent the body of the function, which is one or more lines of code providing the procedure to be executed.\n",
+    "- **Return.** We use the `return` keyword to return a value back to where the function was called. This is optional to use, and `None` is returned if a return value is not otherwise provided.\n",
+    "\n",
+    "Note: Using `def` only defines the function and points the specified name to the function object. The code itself does not run until called."
+   ]
+  },
   {
    "cell_type": "code",
    "execution_count": null,

notebooks/1c_visualization.ipynb

@@ -504,6 +504,65 @@
    "source": [
     "# 1-2 code"
    ]
+  },
+  {
+   "cell_type": "markdown",
+   "metadata": {},
+   "source": [
+    "# Bonus Content\n",
+    "\n",
+    "Did you notice that, once we figured out the height, width, and template that we wanted, we ended up reusing those arguments again and again?\n",
+    "There is a way to capture those and reuse them.\n",
+    "We use a dictionary and [dictionary unpacking](https://docs.python.org/3/tutorial/controlflow.html?highlight=unpack%20dictionary#unpacking-argument-lists).\n",
+    "See the example below."
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": null,
+   "metadata": {},
+   "outputs": [],
+   "source": [
+    "fig_b03 = px.line(\n",
+    "    vis,\n",
+    "    x=\"year\",\n",
+    "    y=\"vis\",\n",
+    "    title=\"WSJ Coverage by Firm-year\",\n",
+    "    color=\"ticker\",\n",
+    "    template=\"plotly_dark\",\n",
+    "    width=800,\n",
+    "    height=600,\n",
+    ")\n",
+    "\n",
+    "fig_b03.show()"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": null,
+   "metadata": {},
+   "outputs": [],
+   "source": [
+    "GRAPH_FORMAT = {\"template\": \"plotly_dark\", \"width\": 800, \"height\": 600}\n",
+    "\n",
+    "fig_b03a = px.line(\n",
+    "    vis,\n",
+    "    x=\"year\",\n",
+    "    y=\"vis\",\n",
+    "    title=\"WSJ Coverage by Firm-year\",\n",
+    "    color=\"ticker\",\n",
+    "    **GRAPH_FORMAT,\n",
+    ")\n",
+    "\n",
+    "fig_b03a.show()"
+   ]
+  },
+  {
+   "cell_type": "markdown",
+   "metadata": {},
+   "source": [
+    "A key benefit of extracting our favorite formatiing options this way is that we can change all of our graphs by making a single change to a single dictionary."
+   ]
   }
  ],
  "metadata": {
@@ -526,7 +585,7 @@
    "name": "python",
    "nbconvert_exporter": "python",
    "pygments_lexer": "ipython3",
-   "version": "3.11.3"
+   "version": "3.11.4"
   },
   "vscode": {
    "interpreter": {

notebooks/2b_retrieval1.ipynb

@@ -460,7 +460,7 @@
    "name": "python",
    "nbconvert_exporter": "python",
    "pygments_lexer": "ipython3",
-   "version": "3.11.3"
+   "version": "3.11.4"
   },
   "vscode": {
    "interpreter": {

notebooks/2c_retrieval2.ipynb

@@ -145,7 +145,7 @@
    "outputs": [],
    "source": [
     "start = datetime.datetime(2012, 1, 1)\n",
-    "end = datetime.datetime(2023, 2, 28)\n",
+    "end = datetime.datetime(2023, 12, 31)\n",
     "\n",
     "fred_gs10 = pdr.DataReader(\"GS10\", \"fred\", start, end).reset_index()\n",
     "fred_gs10.head()"
@@ -228,7 +228,7 @@
    "name": "python",
    "nbconvert_exporter": "python",
    "pygments_lexer": "ipython3",
-   "version": "3.11.3"
+   "version": "3.11.4"
   },
   "vscode": {
    "interpreter": {