Skip to content

Commit 592b272

Browse files
committed
docs: add file download links in examples
1 parent 5729b2e commit 592b272

File tree

6 files changed

+6
-6
lines changed

6 files changed

+6
-6
lines changed

examples/custom_workflow.ipynb

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,7 @@
1111
"\n",
1212
"In this example, we simulate the day-ahead operation for three consecutive days. Specifically, we show how to solve the problem using the rounding heuristic, solving for locational marginal prices, and plotting the activity of storage units.\n",
1313
"\n",
14-
" The power system model, named \"solar_ess\", includes one thermal unit and one integrated solar photovoltaic (PV) and battery energy storage system (BESS) unit, connected across two substations. The system configuration is illustrated below."
14+
"The power system model, named \"solar_ess\", includes one thermal unit and one integrated solar photovoltaic (PV) and battery energy storage system (BESS) unit, connected across two substations. The system configuration is illustrated below. Data files for this case study, called \"solar_ess\", can be found [here](https://github.com/Critical-Infrastructure-Systems-Lab/PowNet/tree/master/model_library). Please download them to a folder on your local machine."
1515
]
1616
},
1717
{

examples/quickstart.ipynb

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@
77
"source": [
88
"# Quick start example\n",
99
"\n",
10-
"PowNet provides the Simulator class to simplify the process of analyzing how electricity is generated and flows through the network. In this example, we will simulate the day-ahead scheduling (24-hours) over two days. The system has three thermal units, one import node, and one hydropower unit. There are four substations with demand. Generators are treated as their own nodes. The dummy system is depicted below."
10+
"PowNet provides the Simulator class to simplify the process of analyzing how electricity is generated and flows through the network. In this example, we will simulate the day-ahead scheduling (24-hours) over two days. The system has three thermal units, one import node, and one hydropower unit. Data files for this case study, called \"dummy\", can be found [here](https://github.com/Critical-Infrastructure-Systems-Lab/PowNet/tree/master/model_library). Please download them to a folder on your local machine. There are four substations with demand. Generators are treated as their own nodes. The dummy system is depicted below."
1111
]
1212
},
1313
{

examples/reservoir_reoperation.ipynb

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,7 @@
1111
"\n",
1212
"This example follows the code shown in the \"Custom Workflow Example\". Additional steps involved calling `ReservoirManager` and `PowerWaterCoupler` classes. Outputs from the regular model and the re-operation model are also compared.\n",
1313
"\n",
14-
"In this example, we simulate the reservoir re-operation over one simulation year (365 days). The power system model, named \"hydro_system\", includes two nodes connected by a trasmission line. Node1 has two hydropower units (\"Atay\" and \"Kamchay\") and one thermal unit. The two hydropower units are located on a river cascade. Node 2 has one hydropower unit (\"Kirirom\") and one thermal unit."
14+
"In this example, we simulate the reservoir re-operation over one simulation year (365 days). The power system model, named \"hydro_system\", includes two nodes connected by a trasmission line. Node1 has two hydropower units (\"Atay\" and \"Kamchay\") and one thermal unit. The two hydropower units are located on a river cascade. Node 2 has one hydropower unit (\"Kirirom\") and one thermal unit. Data files for this case study, called \"hydro_system\", can be found [here](https://github.com/Critical-Infrastructure-Systems-Lab/PowNet/tree/master/model_library). Please download them to a folder on your local machine."
1515
]
1616
},
1717
{

examples/reservoir_simulation.ipynb

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@
99
"\n",
1010
"This notebook shows an example of estimating daily hydropower time series given a water system. Here, we will work with a system called \"complex_river\", comprising four reservoirs: Atay, Kamchay, Kirirom1, and Kirirom2. These reservoirs are situated in a cascade. Water flow from Kamchay are diverted 25% to Kirirom1 and 75% to Kirirom2. Hydropower capacities are shown in the figure below.\n",
1111
"\n",
12-
"The following code imports necessary libraries and displays a diagram of the 'complex_river' water system, illustrating reservoir connections and hydropower capacities."
12+
"The following code imports necessary libraries and displays a diagram of the 'complex_river' water system, illustrating reservoir connections and hydropower capacities. Data files for this case study, called \"complex_river\", can be found [here](https://github.com/Critical-Infrastructure-Systems-Lab/PowNet/tree/master/model_library). Please download them to a folder on your local machine."
1313
]
1414
},
1515
{

examples/synthetic_load.ipynb

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@
77
"source": [
88
"# Creating Synthetic Load Time Series\n",
99
"\n",
10-
"PowNet is designed to work with time series data, facilitating seamless sensitivity analysis within its modeling framework. This example demonstrates how to generate multiple synthetic hourly load profile scenarios (specifically, 5 scenarios) using PowNet's time series capabilities. We will use a simplified system model, partly based on the 2023 Thai power system, as our case study.\n",
10+
"PowNet is designed to work with time series data, facilitating seamless sensitivity analysis within its modeling framework. This example demonstrates how to generate multiple synthetic hourly load profile scenarios (specifically, 5 scenarios) using PowNet's time series capabilities. We will use a simplified system model, partly based on the 2023 Thai power system, as our case study. Data files for this case study, called \"synthetic_timeseries\", can be found [here](https://github.com/Critical-Infrastructure-Systems-Lab/PowNet/tree/master/model_library). Please download them to a folder on your local machine.\n",
1111
"\n",
1212
"**Note:** PowNet requires the `pmdarima` package for advanced time series analysis. Ensure it is installed in your environment. If you use Conda, you can install it with: `conda install pmdarima`. This package is not included as a dependency in PowNet by default."
1313
]

examples/synthetic_solar.ipynb

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@
77
"source": [
88
"# Creating Synthetic Solar Time Series\n",
99
"\n",
10-
"PowNet is designed to work with time series data, facilitating seamless sensitivity analysis within its modeling framework. This example demonstrates how to generate multiple synthetic hourly solar time series (5 scenarios) using PowNet's time series capabilities. The original time series is an estimated one of a large solar farm (\"EASNS\") found in the 2023 Thai power system.\n",
10+
"PowNet is designed to work with time series data, facilitating seamless sensitivity analysis within its modeling framework. This example demonstrates how to generate multiple synthetic hourly solar time series (5 scenarios) using PowNet's time series capabilities. The original time series is an estimated one of a large solar farm (\"EASNS\") found in the 2023 Thai power system. Data files for this case study, called \"synthetic_timeseries\", can be found [here](https://github.com/Critical-Infrastructure-Systems-Lab/PowNet/tree/master/model_library). Please download them to a folder on your local machine.\n",
1111
"\n",
1212
"**Note:** PowNet requires the `pmdarima` package for advanced time series analysis. Ensure it is installed in your environment. This package is not included as a dependency in PowNet by default.\n",
1313
"\n",

0 commit comments

Comments
 (0)