You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
<li>If required, the sample SIREN simulation of the SWIS - <em>siren_sample.exe</em>
34
34
</ul>
35
35
<h3>Packaging for Windows</h3>
36
-
<p>I use PyInstaller (currently Version 5.6.2) to package SIREN for Windows. I use the multi-package facility to create executables for <code>siren.py, sirenm.py</code> and the tools (<code>flexiplot.py, getmap.py, getmerra2.py, indexweather.py, makegrid.py, makeweatherfiles.py, powermatch.py, powerplot.py, sirenupd.py</code> and <code>updateswis.py</code>). <code>siren_application.spec</code> is the spec file (<code>pyinstaller.exe siren_application.spec</code> with options <code>--log-level ERROR</code> and/or <code>--noconfirm</code> ... <code>pyinstaller.exe --noconfirm --log-level ERROR siren_application.spec</code>). This enables all programs to be included in a single library for distribution. PyInstaller places them in individual directories - I use <code>package_siren.py</code> to copy all the executables into the <em>siren</em> directory and remove some unwanted files that are included as part of the packaging process.</p>
36
+
<p>I use PyInstaller (currently Version 5.6.2) to package SIREN for Windows. I use the multi-package facility to create executables for <code>siren.py, sirenm.py</code> and the tools (<code>flexiplot.py, getera5.py, getmap.py, getmerra2.py, indexweather.py, makegrid.py, makeweatherfiles.py, pmtmldetail.py, powermatch.py, powerplot.py, sirenupd.py</code> and <code>updateswis.py</code>). <code>siren_application.spec</code> is the spec file (<code>pyinstaller.exe siren_application.spec</code> with options <code>--log-level ERROR</code> and/or <code>--noconfirm</code> ... <code>pyinstaller.exe --noconfirm --log-level ERROR siren_application.spec</code>). This enables all programs to be included in a single library for distribution. PyInstaller places them in individual directories - I use <code>package_siren.py</code> to copy all the executables into the <em>siren</em> directory and remove some unwanted files that are included as part of the packaging process.</p>
37
37
<p>All these files have a version file where the version is <code><major>,<minor>.<yyyy>.<mmdd></code>. <code><major></code> and <code><minor></code> refer to the SIREN release. The date part is the date the program was last changed. The version numbering simulates Microsoft version numbers. <code>template_version</code> provides a template for the version files to enable new SIREN releases to be packaged. The current <code>major</code> version is <strong><code>4</code></strong> (<code>1</code> was the initial version, <code>2</code> for the change from Python2 to Python3, and for the change from PyQt4 to PyQt5, and <code>4</code> for a change to a new packaging environment, Windows 10 rather than Windows 7, and a change to 64-bit Python).</p>
38
38
<p>To enable the modules to be built correctly most require <code>hiddenimports</code>, as identified in <code>siren_application.spec</code>, as often PyInstaller will fail to identify all imports from libraries used by the SIREN program.</p>
39
-
<p><code>makeweather_getmerra2.spec</code> and <code>package_makeweatherfiles.py</code> package <code>makeweatherfiles.py</code> and <code>getmerra2.py</code> to provide a standalone tool to create SAM weather files from MERRA-2 datasets.</p>
39
+
<h4>Makeweatherfiles</h4>
40
+
<p>Weather files suitable for SAM can be obtained from either ERA5 or MERRA-2 satellite data. I again use the multi-package facility to create executables for <code>getera5.py, getmerra2.py</code> and <code>makeweatherfiles.py</code> to provide a standalone tool to create SAM weather files from ERA5 or MERRA-2 datasets. <code>package_makeweatherfiles.py</code> packages these three programs.</p>
40
41
<h2id="python">A Python version</h2>
41
42
<p>A Python version of SIREN is a viable alternative for Linux and MacOS (and for Windows users who have Python installed). The following instructions may assist:</p>
42
43
<ul>
@@ -66,7 +67,7 @@ <h2 id="github">github</h2>
66
67
<li><em>siren_application.spec</em> is the specification file used to package the SIREN application using PyInstaller</li>
67
68
<li>You can also view the SIREN help file at <ahref="https://rawgit.com/ozsolarwind/siren/master/help.html" target="_blank">https://rawgit.com/ozsolarwind/siren/master/help.html</a>
68
69
</ul>
69
-
<p>You should download all files (except the spec file) to your target “home” folder for SIREN.<p>
70
+
<p>You should download all files (except the package and spec files) to your target “home” folder for SIREN.<p>
70
71
<h2>SourceForge</h2>
71
72
<p><ahref="https://sourceforge.net/projects/sensiren/" target="_blank">https://sourceforge.net/projects/sensiren/</a> contains a number of self-extracting zip files for the full SIREN Toolkit and a number of the components. See <ahref="help.html#install" target="_blank">Installation</a>.
<tr><td>pmtmldetail.py</td><td>Produce a more detailed Powermatch Detail worksheet which contains hourly details on how RE is used to meet load</td></tr>
156
158
<tr><td>powerclasses.py</td><td>Classes used by PowerModel (powermodel.py)</td></tr>
157
159
<tr><td>powermatch.py</td><td>Match generation to load. Produce costed scenarios</td></tr>
158
160
<tr><td>powermodel.py (*)</td><td>Process SAM models for stations to produce spreadsheets and charts</td></tr>
@@ -193,5 +195,5 @@ <h3>sam_models_list</h3>
193
195
</ul>
194
196
<h3>opt_debug</h3>
195
197
<p><code>opt_debug.py</code> can be used to debug the <code>powermatch</code> optimisation routine. It doesn't need to be packaged with SIREN.</p>
<li>Using SIREN to build scenarios for an energy mix as described in more detail below</li>
3105
+
<li>Using the Powermatch data produced to complete a costed renewable energy scenario. This is described in <ahref="#powermatch">Powermatch</a></li>
3106
+
</ol>
3102
3107
<p>The simulation allows you to build scenarios for the energy mix for your area of interest. It is based around the map of your chosen area and allows you to visualise the layout of the existing electricity network plus the additional stations you place on the map to build your scenario(s). The map initially shows the main skeleton of the existing electricity grid infrastructure and current generation stations.</p>
3103
3108
<p>To add a new station simply right-click on the map at the desired location and then update the details for the station (Name, Technology, Capacity and so forth) and press <em>Save & Exit</em>. You can also copy an existing station and other options as specified above. </p>
3104
3109
<p>As you build your scenario, the simulation adds additional infrastructure to connect the new generation plants to the grid. The colours for the majority of the items on the map are as you specify in the Preferences file. You navigate around the map using normal mouse movements to scroll, zoom, etc. and interact with it as described previously (<ahref="#menus">Menus</a>). Using the various menu options you can model your whole scenario, or by right-clicking you can deal with an individual station. There are a number of additional windows, such as menu options, that can be opened to assist with using SIREN (see <ahref="#windows">Windows</a>)</p>
<p>SIREN accepts a number of file formats for each of the data files it uses. In many cases input files can be either a CSV or Excel (XLS or XLSX) file. Due to the initial source for each data file the format for each may be different. For CSV and Excel files the first cell for each column is usually taken as the column name.</p>
4033
-
<p><strong>Note:</strong> Other than the Powermatch file, all Excel files output by SIREN are currently in XLS format (XLSX files require a different Python library to create them).</p>
4038
+
<p><strong>Note:</strong> Other than the Powermatch file, all Excel files output by SIREN are currently in XLS format (XLSX files require a different Python library to create them). Powermatch itself produces XLSX files.</p>
<strong>Note:</strong> The behaviour of the bounding coordinates fields are a little quirky in that they will adjust themselves so the west (left) value is always west of the east value and the north (upper) value is always higher than the south value
4361
4366
</li>
4362
-
<li><em>Grid</em>. The size of the desired grid latitude and longitude. These can be in increments of 0.25 degrees up to a mximum of 3 degrees</li>
4367
+
<li><em>Grid</em>. The size of the desired grid latitude and longitude. These can be in increments of 0.25 degrees up to a maximum of 3 degrees</li>
4363
4368
<li><em>Start month</em>. The first month to be downloaded. The CDS API is flexible on the range of dates that can be requested. For pragmatic purposes <code>getera5</code> requests data as a range of months</li>
4364
4369
<li><em>End month</em>. The last month to be downloaded. If a Start month of 1 and an End month of 12 is chosen the program will request a year of data as a single file</li>
4365
4370
<li><em>Target Folder</em>. Use this to specify the location for the ERA5 files. To change the location you need to click on the field and navigate to the correct folder (you can't type into the field)</li>
0 commit comments