<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<style type="text/css" style="display:none;"> P {margin-top:0;margin-bottom:0;} </style>
</head>
<body dir="ltr">
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Hi Ben,</div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Thanks for the guidance.</div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
I should mention that in my own modelling I have had occasion to wish that I could plot a curve with 8760 points on it. Understanding nemo should help me to do that. I am looking forward to acquiring that understanding.</div>
<div>
<div id="appendonsend"></div>
<div style="font-family:Calibri,Helvetica,sans-serif; font-size:12pt; color:rgb(0,0,0)">
<br>
</div>
<div style="font-family:Calibri,Helvetica,sans-serif; font-size:12pt; color:rgb(0,0,0)">
There are no mistakes in the Notebook. There is the one anomaly that I mentioned in another email about "%matplotlib inline" that is an artifact of running in Pycharm and not in IPython. I think that is worth mentioning in the Notebook. Nemo runs in Python3
but was it started using Python2?</div>
<div style="font-family:Calibri,Helvetica,sans-serif; font-size:12pt; color:rgb(0,0,0)">
<br>
</div>
<div style="font-family:Calibri,Helvetica,sans-serif; font-size:12pt; color:rgb(0,0,0)">
I think it is also worth specifying when a user needs to use the evolve script to get useful results. A reference to documentation that describes the cost optimization algorithm would be useful too.</div>
<div style="font-family:Calibri,Helvetica,sans-serif; font-size:12pt; color:rgb(0,0,0)">
<br>
</div>
<div style="font-family:Calibri,Helvetica,sans-serif; font-size:12pt; color:rgb(0,0,0)">
<span style="caret-color: rgb(0, 0, 0); font-family: Calibri, Helvetica, sans-serif; background-color: rgb(255, 255, 255); display: inline !important">I will fetch the trace files from the Canberra server and access them locally by replacing the web reference
in the config file to a local path reference.</span><br>
</div>
<div style="font-family:Calibri,Helvetica,sans-serif; font-size:12pt; color:rgb(0,0,0)">
<br>
</div>
<div style="font-family:Calibri,Helvetica,sans-serif; font-size:12pt; color:rgb(0,0,0)">
I can then step through the OCGT/CCGT scenario to understand the mechanics of the nemo code.</div>
<div style="font-family:Calibri,Helvetica,sans-serif; font-size:12pt; color:rgb(0,0,0)">
<br>
</div>
<div style="font-family:Calibri,Helvetica,sans-serif; font-size:12pt; color:rgb(0,0,0)">
I will also use the evolve script to run the re100_batteries scenario. I need to understand the storage capacity provisioning rules documented by Blakers, Lu, and Stocks in their paper.</div>
<div style="font-family:Calibri,Helvetica,sans-serif; font-size:12pt; color:rgb(0,0,0)">
<br>
</div>
<div style="font-family:Calibri,Helvetica,sans-serif; font-size:12pt; color:rgb(0,0,0)">
Regards,</div>
<div style="font-family:Calibri,Helvetica,sans-serif; font-size:12pt; color:rgb(0,0,0)">
Don</div>
<br>
<hr tabindex="-1" style="display:inline-block; width:98%">
<div id="divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" color="#000000" style="font-size:11pt"><b>From:</b> Ben Elliston <bje@air.net.au><br>
<b>Sent:</b> December 13, 2019 9:01 PM<br>
<b>To:</b> Don Cameron <dcameron3009@hotmail.com><br>
<b>Cc:</b> nemo-devel@lists.ozlabs.org <nemo-devel@lists.ozlabs.org><br>
<b>Subject:</b> Re: [NEMO-devel] scenarios.re100_batteries(c)</font>
<div> </div>
</div>
<div class="BodyFragment"><font size="2"><span style="font-size:11pt">
<div class="PlainText">Hi Don<br>
<br>
Welcome and thanks for your introduction.<br>
<br>
> I loaded nemo in Pycharm that is running Python 3 and tried out the<br>
> sample code on the Jupyter Notebook page. I had to put() around the<br>
> argument to the print command.<br>
<br>
Were there any mistakes in the notebook that you found?<br>
<br>
> One of the lines is<br>
> print(c.generators).<br>
> All of the solar and wind resources are 0kW. The hydro resources had<br>
> positive capacity values.<br>
<br>
OK, so a bit of background is helpful here. The default scenario was<br>
originally the only scenario before NEMO even had a name. It provides<br>
meaningful capacites for the various types of generators so that you<br>
can set up a context object and then run nemo.run(c). You will then<br>
get meaningful results.<br>
<br>
However, most of the scenarios are never run by hand this way and are<br>
always cost-optimised using the evolve script. For this reason, when<br>
writing a scenario function, I was usually lazy and would specify zero<br>
as the capacity of most generators (except when defining specific<br>
legacy generators with fixed capacities, like Australia's various<br>
pumped hydro systems).<br>
<br>
If you just want to play around with one scenario, the "ccgt" is a<br>
good start. It simulates one mammoth CCGT and one mammoth OCGT.<br>
<br>
> I did a bit of stepping through the code in the debugger but I think<br>
> that probably triggered web request timeouts. So I would have to<br>
> think through a bit more on how to breakpoint the code to avoid the<br>
> timeouts.<br>
<br>
NEMO fetches all of the trace data from a web server in Canberra. This<br>
is convenient in some ways, but inconvenient in others. You will find<br>
it helpful to fetch them all and save them to disk. Then you can<br>
modify the entries in the "generation" section of the nemo.cfg<br>
configuration file to refer to local filenames. This will (a) speed<br>
things up and (b) likely overcome the problem you described when<br>
stepping inside the debugger.<br>
<br>
Happy to help with anything that is missing, confusing or could be<br>
improved. Feedback is most welcome.<br>
<br>
Cheers,<br>
Ben<br>
</div>
</span></font></div>
</div>
</body>
</html>