EMK:EMarket 5 Notes - Revision history

NelsonM: /* Additional Output Spec features */

2013-03-21T21:13:20Z

Additional Output Spec features

NelsonM: /* Additional Output Spec features */

2013-03-21T21:11:42Z

Additional Output Spec features

NelsonM: /* Additional Output Spec features */

2013-03-21T21:11:11Z

Additional Output Spec features

NelsonM: /* Multi-year water values */

2013-03-08T02:07:18Z

Multi-year water values

NelsonM: /* Command Line Emarket */

2013-03-08T02:06:10Z

Command Line Emarket

NelsonM: /* Grid updates */

2013-03-08T02:04:27Z

Grid updates

NelsonM: /* Demand input table */

2013-03-08T01:52:54Z

Demand input table

NelsonM: /* Multi-year water values */

2013-03-08T01:33:52Z

Multi-year water values

NelsonM: /* Multi-year water values */

2013-03-08T01:32:26Z

Multi-year water values

NelsonM: /* Multi-year water values */

2013-03-08T01:32:06Z

Multi-year water values

@@ Line 70: / Line 70: @@
 *Reduced digits in .Csv files.
-You can now add a filter that will reduce to the number is digits after a decimal point. The format is ":n" after the function description
+You can now add a filter that will reduce to the number is digits after a decimal point. The format is ":n" after the function description: i.e. Function.Ave(Node.Price):2  would limit the result to 2 decimal places
 ===Command Line Emarket===

@@ Line 69: / Line 69: @@
 The output files can also be divided into years using the year function. Note that this also requires a new function is the Column or Row partition called ‘MonthofYear’ so that the correct months are allocated.
-Reduced digits in .Csv files.
+*Reduced digits in .Csv files.
 You can now add a filter that will reduce to the number is digits after a decimal point. The format is ":n" after the function description

@@ Line 69: / Line 69: @@
 The output files can also be divided into years using the year function. Note that this also requires a new function is the Column or Row partition called ‘MonthofYear’ so that the correct months are allocated.
-Examples are shown in the Resources files (‘Summary_byYear’ and’ Summary_byNode’)
+Reduced digits in .Csv files.
 ===Command Line Emarket===

← Older revision		Revision as of 02:07, 8 March 2013
Line 25:		Line 25:

	The length of the run defines the length of the multi-year water value. As mentioned above, the additional offers and demand need to be incorporated into the run data.		The length of the run defines the length of the multi-year water value. As mentioned above, the additional offers and demand need to be incorporated into the run data.
		+
		+	The Water Value Viewer has been updated to cover all the data.

	[[File:EM5 4 Example.JPG\|600px\|thumb\|left\|EM4 EM5 comparison]]		[[File:EM5 4 Example.JPG\|600px\|thumb\|left\|EM4 EM5 comparison]]

@@ Line 73: / Line 73: @@
 The command switches at present are;
-•	-wd <working directory> , sets the working directory in which EMarket starts up
+*-wd <working directory> , sets the working directory in which EMarket starts up
-•	-r <batch runs>, causes EMarket to run a batch, runs are comma delimited in the argument. Emarket will close when the batch is finished
+*-r <batch runs>, causes EMarket to run a batch, runs are comma delimited in the argument. Emarket will close when the batch is finished
-•	-wvo, runs the batch with the 'Water Values Only' option
+*-wvo, runs the batch with the 'Water Values Only' option
-•	-wwv, runs the batch with the 'Wait for Water Values' option
+*-wwv, runs the batch with the 'Wait for Water Values' option
-•	-vm <volatility matrix>, sets the volatility matrix fo the run and directs the results to a partial database which can be merged with other executions of the same run.  e.g. -vm "InflowYear:1940-1950,1980"
+*-vm <volatility matrix>, sets the volatility matrix fo the run and directs the results to a partial database which can be merged with other executions of the same run.  e.g. -vm "InflowYear:1940-1950,1980"
-•	-rb <reports batch> <run> [<minimum number of run parts>], runs a reports batch on the named run.  If the minimum number of run parts is specified then EMarket will wait until at least this number of run outputs are produced in the latest version of the run results. This option also ensures the current batch number is iterated by 1 value.
+*-rb <reports batch> <run> [<minimum number of run parts>], runs a reports batch on the named run.  If the minimum number of run parts is specified then EMarket will wait until at least this number of run outputs are produced in the latest version of the run results. This option also ensures the current batch number is iterated by 1 value.
-•	-?, displays this help message
+*-?, displays this help message
 ===Additional Tick Sizes===

@@ Line 35: / Line 35: @@
 Timeseries schedule elements are required to activate the lines version; The default lines version is zero.
 Line:CYD2_ROX2.Version  =  Timeseries(0, '1/4/2015', 1)
-The demonstration is still somewhat untested and may have some errors. It was created for testing purposes rather than as a proper forecast grid, although feedback on obvious errors would be welcome.
+Although this feature has always been available, we have further enhanced our ability to use multiple character nodes within the grid. This allows for separate modelling of the 220, 110 and 66 KV part of the grid as well as interconnecting transformers.
 As part of the grid upgrade we discovered a ‘special’ Windows feature where a hidden copy of the map was being read rather than the copy in the program files directory. If you can’t correctly read the map data when you have overwrite the one in the ‘program files’ directory, please call us and we will try and help by finding the culprit.

@@ Line 60: / Line 60: @@
 *The regions are how they are defined in the demand regions (as per EM4).
 *Twenty four months of additional demand data is required the multi-ear water values.
 If you don’t want to determine specific monthly values, demand can be entered as an annual time series or via a variable and the schedule. Examples are given in the resources file.

@@ Line 28: / Line 28: @@
 [[File:EM5 4 Example.JPG|600px|thumb|left|EM4 EM5 comparison]]
-Our testing and analysis of the multi-year water values showed that on an annual average basis there is almost no difference between EM4 and EM5 average prices. However on a monthly basis we experienced a lower winter price, but a higher spring/early summer price. This is a direct result of the weekly generation sampling of EM5 (rather than annual average of EM4). The model now takes into account the high availability of plant during winter, where as (within this particular forecast) the lower availability in the spring and early summer.
+Our testing and analysis of the multi-year water values showed that on an annual average basis there is almost no difference between EM4 and EM5 average prices. However on a monthly basis we experienced a lower winter price, but a higher spring/early summer price. This is a direct result of the weekly generation sampling of EM5 (rather than annual average of EM4). The model now takes into account the higher availability of plant during winter, as well as (within this particular forecast) the lower availability in the spring and early summer.
 ===Grid updates===

@@ Line 25: / Line 25: @@
 The length of the run defines the length of the multi-year water value. As mentioned above, the additional offers and demand need to be incorporated into the run data.
-[[File:EM5 4 Example.JPG|400px|thumb|left|EM4 EM5 comparison]]
 Our testing and analysis of the multi-year water values showed that on an annual average basis there is almost no difference between EM4 and EM5 average prices. However on a monthly basis we experienced a lower winter price, but a higher spring/early summer price. This is a direct result of the weekly generation sampling of EM5 (rather than annual average of EM4). The model now takes into account the high availability of plant during winter, where as (within this particular forecast) the lower availability in the spring and early summer.