attempt at fixing backtick problem

spjuhel · May 24, 2024 · 567d930 · 567d930
1 parent 4550920
commit 567d930
Showing 1 changed file with 22 additions and 22 deletions.
diff --git a/docs/source/notebooks/boario-quickstart.ipynb b/docs/source/notebooks/boario-quickstart.ipynb
@@ -2,7 +2,7 @@
  "cells": [
   {
    "cell_type": "markdown",
-   "id": "0a44df26",
+   "id": "20a01490",
    "metadata": {},
    "source": [
     "# Quickstart example\n",
@@ -14,7 +14,7 @@
   },
   {
    "cell_type": "markdown",
-   "id": "82536c42",
+   "id": "6dd240c2",
    "metadata": {},
    "source": [
     "## Instantiating a model from a MRIOT system\n",
@@ -25,7 +25,7 @@
   {
    "cell_type": "code",
    "execution_count": null,
-   "id": "ae5a1f88",
+   "id": "791c6a45",
    "metadata": {},
    "outputs": [],
    "source": [
@@ -37,7 +37,7 @@
   },
   {
    "cell_type": "markdown",
-   "id": "2886099c",
+   "id": "2a687015",
    "metadata": {},
    "source": [
     "Some attributes of the test MRIOT are not computed. Calling calc_all() ensures all required tables are present in the IOSystem object. This ``pymrio.IOSystem`` method automatically identifies which tables are missing and calculates them following the IO formal framework. (See [here](https://pymrio.readthedocs.io/en/latest/math.html) for more details.)"
@@ -46,7 +46,7 @@
   {
    "cell_type": "code",
    "execution_count": null,
-   "id": "db8e3bac",
+   "id": "4c33a21b",
    "metadata": {},
    "outputs": [],
    "source": [
@@ -55,10 +55,10 @@
   },
   {
    "cell_type": "markdown",
-   "id": "1a97ee2a",
+   "id": "7da3a0fe",
    "metadata": {},
    "source": [
-    "If you see multiple: ``FutureWarning: DataFrame.groupby with axis=1 is deprecated. Do `frame.T.groupby(...)` without axis instead.``\n",
+    "If you see multiple: ``FutureWarning: DataFrame.groupby with axis=1 is deprecated. Do \\`frame.T.groupby(...)\\` without axis instead.``\n",
     "don't panic, this comes from `pymrio` but it is not an error, just a syntax warning.\n",
     "\n",
     "In case you find it annoying, you can use the following beforehand:"
@@ -67,7 +67,7 @@
   {
    "cell_type": "code",
    "execution_count": null,
-   "id": "ce74e9de",
+   "id": "beacb97b",
    "metadata": {},
    "outputs": [],
    "source": [
@@ -77,7 +77,7 @@
   },
   {
    "cell_type": "markdown",
-   "id": "455f7c4c",
+   "id": "78dd31c1",
    "metadata": {},
    "source": [
     "Instantiating the model is very straightforward:"
@@ -86,7 +86,7 @@
   {
    "cell_type": "code",
    "execution_count": null,
-   "id": "dbbb1b17",
+   "id": "d4148209",
    "metadata": {},
    "outputs": [],
    "source": [
@@ -95,15 +95,15 @@
   },
   {
    "cell_type": "markdown",
-   "id": "ed93d6ab",
+   "id": "6e1afa65",
    "metadata": {},
    "source": [
     "This sets the model with all the default parameters. We highly recommand you to study the different parameters and their options for actual use. See [Changing the model parameters](../tutorials/model-params.rst)."
    ]
   },
   {
    "cell_type": "markdown",
-   "id": "b9f71932",
+   "id": "838ea49d",
    "metadata": {},
    "source": [
     "Similarly, instantiating a simulation is also quite easy:"
@@ -112,7 +112,7 @@
   {
    "cell_type": "code",
    "execution_count": null,
-   "id": "30774bef",
+   "id": "84637bf8",
    "metadata": {},
    "outputs": [],
    "source": [
@@ -123,7 +123,7 @@
   },
   {
    "cell_type": "markdown",
-   "id": "c27682a8",
+   "id": "c4c9c837",
    "metadata": {},
    "source": [
     "Once the model and simulation have been instantiated, you can now define an event:"
@@ -132,7 +132,7 @@
   {
    "cell_type": "code",
    "execution_count": null,
-   "id": "0a89e40e",
+   "id": "3094f309",
    "metadata": {},
    "outputs": [],
    "source": [
@@ -152,7 +152,7 @@
   },
   {
    "cell_type": "markdown",
-   "id": "0060a8a9",
+   "id": "3a249cfe",
    "metadata": {},
    "source": [
     "Here we define an event happening in region ``reg1`` impacting the productive capital of the ``manufactoring``[^note-1] and ``mining`` sectors. The impact is distributed among the two sectors proportional to their participation to ``reg1``'s GDP.\n",
@@ -166,7 +166,7 @@
   },
   {
    "cell_type": "markdown",
-   "id": "5b3ca3ed",
+   "id": "61f8a87a",
    "metadata": {},
    "source": [
     "The event can then be added to the simulation:"
@@ -175,7 +175,7 @@
   {
    "cell_type": "code",
    "execution_count": null,
-   "id": "4d2de8d8",
+   "id": "5c491b66",
    "metadata": {},
    "outputs": [],
    "source": [
@@ -185,7 +185,7 @@
   },
   {
    "cell_type": "markdown",
-   "id": "bfb22c7a",
+   "id": "9f8c8135",
    "metadata": {},
    "source": [
     "And the loop can be run:"
@@ -194,7 +194,7 @@
   {
    "cell_type": "code",
    "execution_count": null,
-   "id": "d5f9145d",
+   "id": "095c92f6",
    "metadata": {},
    "outputs": [],
    "source": [
@@ -204,7 +204,7 @@
   },
   {
    "cell_type": "markdown",
-   "id": "2575d395",
+   "id": "fc23c887",
    "metadata": {},
    "source": [
     "Once the simulation ran, you can access and plot the timeseries of the variables (see [Monitoring the variables](../tutorials/simulation-context.rst#monitoring-the-model-variables) for a list of accessible variables).\n",
@@ -215,7 +215,7 @@
   {
    "cell_type": "code",
    "execution_count": null,
-   "id": "2ea4c69b",
+   "id": "e56d6b9c",
    "metadata": {},
    "outputs": [],
    "source": [