· A lot faster and more robust with a lot of data processing logic and query optimization
· RES view has been redone:
o Now it shows UCs that are linked with processes/commodities
§ Dbl-Clicking the UC shows all the intersecting processes/commodities
o The main browse form has been integrated in this view.
§ All browse functionality is available here via the "T" and "V" icons on the RES menu bar.
· The process/commodity master forms have been improved
o Element counts appear below the lists
o "Back" button added on the form (bottom left)
o The region combo holds its value across clicks and sessions
· In the models that are distributed by KanORS/KanLo, comments written in the Excel file are visible on the browse form.
· It is now possible to associate a VEDA-BE database with the model. This makes it possible to use the VEDA-BE sets in:
o Browse
o Process/commodity filter specifications in transformation tables
§ Note that VEDA-BE sets are processed more efficiently in transformation tables when they are used as the only filter specification.
· The help menu now opens the VEDA support site. Further, the support site is also installed locally and activated when you access help without Internet connection.
· The Model Variants facility on the Solve form has been renamed to Control Panel (thanks Antti) and many new options have been added.
· New in data declarations
o EOH and BOH are recognized as years in all VEDA-FE tables
o Commodity declaration is not inherited across rows in ~FI_T tables anymore
o *UC_RHS* attributes can now be updated/inserted via transformation tables using the Other_Indexes column for UC_N
· New post-SYNC log files:
o Processes that are redefined across BASE and SubRES or across different SubRES files are reported. The first case is definitely an error. The second one could be OK if you are sure that this is not polluting any of the downstream scenario files and you use only of these SubRES's in each run.
o Commodities that have inconsistent definitions (Sets, Units, LimType, Peak etc.) across BASE and SubRES or across different SubRES files are reported. All the commodities defined in BASE are inherited in each SubRES, so they should normally not be re-declared at all.