EMarket 4 Release Notes

EMarket 4.2.9 -> 4.3.1

- A batch can be run to produce water values only, it can also be set to wait for water values to appear

- A text file 'SubDirs.txt', when placed in the top level working directory, can redirect EMarket to use data and results directories that are not the default ones. E.g. The following line in the 'SubDirs.txt' file will make EMarket use 'C:\data\emarket\new_demand\TempWVs' as its water value directory.

Data\WVs=C:\data\emarket\new_demand\TempWVs

- The format of the output binary files has been changed, the output file is split by version now to avoid files becoming oversize.

EMarket 4.2.13 -> 4.2.2

EMarket 4.2.13

EMarket 4.2.12

EMarket 4.2.11

EMarket 4.2.10a

Data\WVs=C:\data\emarket\new_demand\TempWVs

EMarket 4.2.7 -> 4.2.9

- EMarket now handles negative demand profile figures without producing screwy demand in the water value calculation

- Reverted the changes made to file handling in 4.2.7, these changes produced errors so more attention is required in this area.

EMarket 4.1.10 -> 4.2.7

- Bug fix - too many file connections were being created (1 for each trait) causing an VB6 style IO error. This has been fixed, a single file connection is used for writing to the output database.

EMarket 4.2.6

EMarket 3.10.6 -> 3.10.7

- .7 is the same as .6 except the transmission constraints correction has been turned off again due to concerns about its accuracy.

EMarket 4.2.4

EMarket 4.2.3

EMarket 4.2.2

EMarket 4.2.1

EMarket 4.1.9

- Fixed a bug that allowed line and equation constraints to be relaxed before all stations were removed from the embedded list. This resulted in unexpected relaxation of line limits.

EMarket 4.1.7

- Added the special global variable 'HydroRestriction', which, if defined, will define the amount to which maximum generation in all main hydros is restricted. a value of 0 will imply no restriction, any value between 0 and 1 will represent the proportion of nominal maximum generation removed from available generation. Thus a value of 0.1 with a nominal maximum of 1000MW will lead to a maximum generation of 900MW. Must-run will still be offered in even if exceed the maximum generation value.

EMarket 4.1.5 -> 4.1.7

- improved iteration and convergence of water values

EMarket 4.1.4 -> 4.1.5

- fixed 'week 53' problem with water values

EMarket 4.1.2 -> 4.1.4

- Emarket is now designed to run multiple copies, a working folder can only be opened by one copy of emarket. If a working is being used the EMarket instance will look for another.

- Added the 'Import multiple resource reports' feature

- Handles incorrect volatility matrix better

EMarket 4.1.10

- The seasonal line limit adjustments were not being applied to reverse limits on the lines, this has been fixed.

EMarket 4.0.12 -> 4.1.2

- Corrected an error in water valuation whereby generic hydros were being modelled but their averaged offers were not removed from the stack, causing them to be double counted. WV's are a bit more expensive due to this change.

- Correction to a linear programming module, the removal of the infeasibility variable was causing numeric errors unneccessarily by choosing and innapropriate pivot variable. This was causing hydro offering to malfunction occasionally.

- Hydro offer prices are now limited to a maximum effectively

- All offer prices are limited to a maximum in the dispatch algorithm

- A Map error has been fixed.

EMarket 4.0.11 -> 4.0.12

Added tributary system functionality, so release from Tekapo can be sent to Pukaki

The format of the WV2 water value files has been changed, to allow for water values involving tributary systems

Changed WV calculation iteration weighting slightly, to assist convergence.

Hidden features for turning on extra dp iterations and using more accurate dp pricing (+CP = corrected pricing, +EI(n) = extra iterations)

Added HydroSystem.CatchmentStorage trait, which include water from tributary system to calculate potential

energy storage. This also includes uncontrolled lakes in the Clutha system.

EMarket 4.0.11

EMarket 4.0.10

-Fixed bug in water values calculations. Minimum flow constraints were not being reset before the calculation of hydro system properties, resulting in bad minimum flow levels for Waikato if the starting storage was set to overfull.

-Water value calculation will not allow marginal values to exceed the shortage cost (as can happen when buffers are applied) - this has been done primarily to improve convergence in the water value calculation.

EMarket 4.0.9

Fixed bug in the calculation of water values using the water value profile. The last contour was effectively ignored and water values set to 0.

EMarket 4.0.8

Fixed bug (Again?) that kept Tekapo flowing into Pukaki from one run to the next!

EMarket 4.0.7

- Water values fix - marginal values do not go below a floor value set by the spill penalty

EMarket 4.0.6

- Use only the storage up to the storage maximum indicated in the water value profile to determine water value

- WV auditing files are output to WVs/Audit if required

- Fixed bug that zeroed the must run offer rather than the discretionary offer when no discretionary was available

- Corrected a bug in the generic hydros that was miscalculating other storage

EMarket 4.0.5

EMarket 4.0.4

EMarket 4.0.3

EMarket 4.0.2

EMarket 4.0.1

Back