Climate module and VEDA Update 4.3.39

[UCL_Will]

Hi there,

We've just updated to Veda FE 4.3.39 and are getting problems synchronizing our climate module. It is clear from our recent model results, that the climate module is not working correctly (and just yesterday it was fine).  We've also checked on another machine running 4.3.37 and the climate module seems fine.

The warning is:

VI: Commodity expected.

Any advice to remedy this?

Kind regards,

Will

P.S. Here's a spreadsheet of the error log:

uploads/62/ImportErrorLog.rar

[AKanudia]

Release notes of 4.3.38 say:

The commodity index has been moved to its regular position from Other_Indexes in two attributes: IRE_TSCVT and IRE_CCV

This means that you have to extract commodity from the Other_Indexes col of these declarations and put them in the CSET_CN col.

[UCL_Will]

Ah, many thanks Amit - I missed that one.

[UCL_Will]

Okay, I've updated the aggregation in our climate module table and it works correctly.  See attached file.

The order of parameters in the 'Other Indexes' field is important and must be joined using a '~'.  For example AFR~CO2-GTC is correct, while CO2-GTC~AFR is not.



Incidentally, when I synchronise this with VEDA-FE, the values of some TOTCO2 are not pasted into the FE database with the correct number of decimal places e.g. concated to 2.700e-7 instead of 2.72727e-7.

[AKanudia]

Right, the order must be respected and you can see what is expected in Attributes Master.

I suspect that you see the loss of precision in numbers only for regions east of IND/JPN (in the sheet)? Unfortunately, the data type of each col is determined based on the first few entries and a long sequence of empty cells makes a col to be read as text. Workaround: insert a first row with numerical values under all regions and a "*" under Attribute.

[UCL_Will]

Hi Amit,

Thank you for the work around.  I've updated the sheet as you recommended and can confirm that the values are imported with the correct level of precision.

Regards,

Will

[Antti-L]

I have already before suggested that ensuring numerical data should be done automatically for all TFM_INS tables except those for SysSettings. To my understanding, apart from SysSettings, all TFM_INS tables can only have numerical data.  So, why doesn't VEDA-FE automatically force the data values to be treated as numerical?  Such a change would be an excellent improvement, because the data must always be numerical anyway. In this way users would no longer have to worry about having loss in their data in TFM_INS tables. Only in SysSettings the TFM_INS tables may also include Text label values, and that would still work as before.