Issue inserting small values for RCAP_BND

[till]

Dear Kanors developers and all,

I have recently faced an issue when trying to insert values for the RCAP_BND attribute that are smaller than 1. (here my implementation     )

Veda throws the warning: "The value is not a number". (see     )

However, Veda reads the values correct if they are set to 1 and the model works, when I manually insert smaller values in the corresponding dd file. That's why I assume, it's reading issue on the Veda side.

Has someone also experienced this or can replicate the issue? Or am I doing something wrong?

Edit: I'm using Veda2.0 version 4.0.1.0

Thanks in advance and best regards,
Till

[Antti-L]

It looks like the decimal symbol you used "," may be wrong, or VEDA somehow does not understand it.
What do you see in Excel, if you enter the formula =1/3 in a cell?  Does the value shown have a comma as the decimal symbol?

[till]

Thanks for coming back to it, Antti.

I use commas as the decimal separator. That works for all other input data with Veda. I also tried changing the cell formatting to Number, which didn't help.

[Antti-L]

Ok thanks for confirming, it then indeed looks like a strange issue...

[Ravinder]

Hi Till,

Could you please share the log file with us?
You can access the log files via the Help menu -> Error Log.

Please share the latest one with us.

[till]

Hi Ravinder, thanks for joining the thread. Sure, here it is: 
  2025-03-05.log (Size: 11.13 KB / Downloads: 4) .

[Antti-L]

While as yet there seems to be no resolution to the issue by the VEDA Support staff, I have a simple question about the purpose of the small bounds.  The retirement variables have a default lower bound of zero, and you seem to be imposing a small positive values, why is that?  If it is for activating retirements, note that it is sufficient to define any value for RCAP_BND, e.g. just an interpolation option without any effect like RCAP_BND(r,'0',p,'N')=1.

This is not to say that the issue shouldn't be resolved; I find it very intriguing. 

[till]

Hi Antti, fair question  

I wanted to test that the retirement works for specific technologies, so forcing it in. Some of those happen to have a capacity below 1. Thus, setting the RCAP_BND to one would not work.

Since I know now that it works, I changed the setup to LimType 'N' and value 0 (as outlined by you).

Thus, resolving the issue would be great, but is luckily not crucial for the current development on my end.

[Ravinder]

Hi Till,

We have reproduced the case, identified the issue, and will address it in the next update.

[Antti-L]

@Ravinder: For our curiosity (and possible mitigation), could you also tell us what was the reason for this strange issue? 

[Ravinder]

Dear Antti,

The issue we are experiencing is indeed related to reading the decimal symbol. While we have measures in place to handle this across different language settings and can implement additional solutions if needed, we are unsure why it is failing in this specific case. Our investigation is still ongoing.

@Till, could you please confirm if there are any additional TFM_INS tables in your model that use decimal (,) values? Also, have you encountered the same issue with them in Veda? Your insights will help us identify a more effective resolution.

[till]

Hi Ravinder,

it was the first time I’ve encountered this issue. I’m using “,” as the decimal separator in all other Veda tables, incl. other TFM_INS tables, which works well.

Best, Till

[Ravinder]

Dear Till,

Thank you for the update.

It appears that the issue is specific to this particular file. We are currently investigating and will resolve it in the next update