syssettings

[mc]

Hi all,

I have a question regarding interpolation options in syssettings.

For a reason we don't understand we cannot get VEDA4 to interpolate shares (nor FLO_SHAR neither FLO_SHAR+) for generic processes defined in baseyear templates.
This problem never turned up before.
We have tried VEDA3 and VEDA4 table headers without any success.
FLO_SHAR for other processes is interpolated correctly.

The defined shares in baseyear are read and displayed correctly in TIMES view. Syssettings.dd is much too small compared to earlier version of syssettings.

Since we haven't changed the syssettings we would appreciate any insight in how to trigger VEDA to interpolate the  shares of baseyear templates, why this problem occurred and how we could solve the issue.

Many thanks in advance,

Monika

[Antti-L]

Can you reproduce the problem with the DEMO model or some other very small test model?

If you can, you could upload the templates of the test model that replicate the issue, and then I am sure it would be very easy to investigate (if you also mention the version of VEDA4 and Office you are using).

[mc]

Hello Antti,

thanks for your reply.

actually a small database produces the same problem.
Independent of VEDA3 or VEDA4 tableheader format.

I may explain by example:
VEDA3:


Now, if you look at the 3rd line, this AGR000 is a process defined in baseyear templates. The initial shares are displayed in TIMES View correctly, the corresponding interpolationsettings in syssettings are not recognised.

VEDA4

Same problem here.

We are using VEDA4.3.43 with excel 2010 (though is use the syssettings file in excel 1997-2003 due to problems with excel).

Generally, we construct the model in several steps due to regular "database too big" issues which delivers us a syssettings.dd for every step.
After checking with TIMES Tutorial (Part II, p39) I can confirm that the "Year 0" is correctly entered in all attributes.

The process in question is defined in BY templates as follows:



As you can see (below) the bound is displayed correctly - only the syssettings information is missing



Furthermore we encounter problems when sync VEDA4 syssettings:



Is the "*"-wildcard still working with VEDA4 headern?

Any help would be greatly appreciated,
greetings,
Monika

[mc]

[mc]

[mc]

[mc]

[Antti-L]

Did you actually reproduce the problem with the DEMO model?

If you did, I suggest that you upload the templates of the test model that replicate the issue. Then I am sure it would be very easy to investigate the problem.

If you didn't try replicating it with the DEMO model, please try it now. If you don't already have the DEMO model templates, you can use the following templates:

uploads/30/demoplugin.zip

Simply add your sample technology into the OTH Base Template, with the Share parameters, and then see if you can reproduce the problem. If you can reproduce it, then upload the Excel templates back here (packed into a ZIP or RAR file), and then I might be able to help you.

But if you cannot provide a reproducible test case, then I guess only Amit can help you out.

[AKanudia]

Monika, have you used "*" in the CSET_SET column? wild cards are not allowed in the proc/comm set columns as there are only a handful of them. They are allowed in all other proc/comm filter columns.

[mc]

Hello,

thanks for your reply.
Actually no, there are no wildcards neither in Pset_Set nor in Cset_Set. There used to be in the old (Veda3) Syssettings in Cset_Set, which I changed in DMD, MAT, etc..
But good to know that wildcards are not allowed in Pset_Set, Cset_Set.

We have included by e.g. *MN and excluded by '-*UN (in Cset_CN), which should be fine, no?

Actually, the problem with not interpolating BY process shares seems to be on a good way to be resolved.
I'll keep you posted as soon as I can confirm that the solution works indeed properly.
Still, if you have any ideas on why this interpolation error showed up, I'd be very happy to hear from you.

[Antti-L]

Well, in my opinion it is very difficult to identify the cause of your problem without seeing the templates. You have showed neither the full process specification for the AGR000 process (only a single line for one input commodity of AGRCOA) nor the SysSettings table where you have the interpolation options. That's why I suggested that you reproduce the problem in the DEMO model, and upload the templates so that we can see what's involved. But I guess you cannot reproduce it?