Request for Help to Solve the Error

[Iram]

Dear Veda Users,

I am not sure from where this error is coming. i checked all my files. But cant find out where is this error coming.
I cant get any results.

[Antti-L]

You have errors due to duplicate elements, which is essentially a VEDA issue, but could be often also fixed by the user.  To see what is causing them, and for the VEDA developers to be able to help you with that, you should better attach the listing file (*.LST) to see the context, and even better, also the base.dd file.  Please zip the file(s) before posting here.

You have also domain violation warnings, which are not fatal, but you should fix them, too...

[Iram]

You have errors due to duplicate elements, which is essentially a VEDA issue, but could be often also fixed by the user.  To see what is causing them, and for the VEDA developers to be able to help you with that, you should better attach the listing file (*.LST) to see the context, and even better, also the base.dd file.  Please zip the file(s) before posting here.

You have also domain violation warnings, which are not fatal, but you should fix them, too...

[Antti-L]

There was a completely different listing file in the ZIP, which was not from the run you showed earlier.  In other words, the listing file you now included does not contain the errors you showed, and therefore it does not provide any information at all to resolve your issue, sorry.

To be more precise, the earlier case with the errors you showed was casetrial.RUN, but the listing file in the ZIP was from cas4.RUN, a completely different case which did not include any of the errors you showed earlier.

[Edit]:
Out of curiosity, I nonetheless tried to reproduce your errors, by creating myself a RUN file and the timeslices data file for a case that just reads the base.dd file. That test case turned out to produce errors of the same kind as you showed for your original case.

The following caused the element redefined errors:

SET TOP_IRE /
'IMPEXP'.'ELC'.'REG1'.'ELC'.'IMP_IRE_NSIC'
'IMPEXP'.'ELC'.'REG1'.'ELC'.'IMP_IRE_NSIC'
'IMPEXP'.'ELC'.'REG1'.'ELC'.'IMP_SCTLND_EWIC'
'IMPEXP'.'ELC'.'REG1'.'ELC'.'IMP_SCTLND_EWIC'
'REG1'.'ELC'.'IMPEXP'.'ELC'.'EXP_IRE_NSIC'
'REG1'.'ELC'.'IMPEXP'.'ELC'.'EXP_IRE_NSIC'
'REG1'.'ELC'.'IMPEXP'.'ELC'.'EXP_SCTLND_EWIC'
'REG1'.'ELC'.'IMPEXP'.'ELC'.'EXP_SCTLND_EWIC'
/;
As you can see, you have duplicate TOP_IRE entries created in the model, which should of course not happen, but while VEDA has this issue, I am sure you can fix the problem also by checking in your Excel templates why these duplicates are created. Maybe you have mistakenly defined those processes somehow in a way that makes VEDA generate the TOP_IRE entries two times?

The domain violations were generated from the following entries:

SET NRG_TMAP /
'REG1'.'ELCH'.'ELCH2L'
/;
SET TOP /
'REG1'.'FT-ELCH2G'.'H2G'.IN
'REG1'.'FT-ELCH2L'.'H2L'.IN
/;
The first one is a typo and easy to fix.  The two other are because the commodities H2G and H2L were not defined.  So, again easy to fix.

[Iram]

There was a completely different listing file in the ZIP, which was not from the run you showed earlier.  In other words, the listing file you now included does not contain the errors you showed, and therefore it does not provide any information at all to resolve your issue, sorry.

To be more precise, the earlier case with the errors you showed was casetrial.RUN, but the listing file in the ZIP was from cas4.RUN, a completely different case which did not include any of the errors you showed earlier.

[Edit]:
Out of curiosity, I nonetheless tried to reproduce your errors, by creating myself a RUN file and the timeslices data file for a case that just reads the base.dd file. That test case turned out to produce errors of the same kind as you showed for your original case.

The following caused the element redefined errors:

SET TOP_IRE /
'IMPEXP'.'ELC'.'REG1'.'ELC'.'IMP_IRE_NSIC'
'IMPEXP'.'ELC'.'REG1'.'ELC'.'IMP_IRE_NSIC'
'IMPEXP'.'ELC'.'REG1'.'ELC'.'IMP_SCTLND_EWIC'
'IMPEXP'.'ELC'.'REG1'.'ELC'.'IMP_SCTLND_EWIC'
'REG1'.'ELC'.'IMPEXP'.'ELC'.'EXP_IRE_NSIC'
'REG1'.'ELC'.'IMPEXP'.'ELC'.'EXP_IRE_NSIC'
'REG1'.'ELC'.'IMPEXP'.'ELC'.'EXP_SCTLND_EWIC'
'REG1'.'ELC'.'IMPEXP'.'ELC'.'EXP_SCTLND_EWIC'
/;
As you can see, you have duplicate TOP_IRE entries created in the model, which should of course not happen, but while VEDA has this issue, I am sure you can fix the problem also by checking in your Excel templates why these duplicates are created. Maybe you have mistakenly defined those processes somehow in a way that makes VEDA generate the TOP_IRE entries two times?

The domain violations were generated from the following entries:

SET NRG_TMAP /
'REG1'.'ELCH'.'ELCH2L'
/;
SET TOP /
'REG1'.'FT-ELCH2G'.'H2G'.IN
'REG1'.'FT-ELCH2L'.'H2L'.IN
/;
The first one is a typo and easy to fix.  The two other are because the commodities H2G and H2L were not defined.  So, again easy to fix.

Dear Antti,

I haven't made any changes to the file yet, but now I am getting different errors. I uninstalled Veda and installed the latest localhost from github, but still it gave the same error. Can you please have a look at it. Thank you for your kind response and help.
Thanks

[Antti-L]

> I haven't made any changes to the file yet, but now I am getting different errors. I uninstalled Veda and installed the latest localhost from github, but still it gave the same error.

No, it is not the same error.  Your latest error does not have anything to do with your model. The new error is related to your VEDA installation: the TIMES source code is not found. Please wait for help from the VEDA support experts, or contact VEDA support directly, if you need help troubleshooting that new error. I am sorry but I am not able to help with VEDA installation problems.

But concerning your original problem, I have given my explanations to the errors in my post above.

[Ravinder]

There was a completely different listing file in the ZIP, which was not from the run you showed earlier.  In other words, the listing file you now included does not contain the errors you showed, and therefore it does not provide any information at all to resolve your issue, sorry.

To be more precise, the earlier case with the errors you showed was casetrial.RUN, but the listing file in the ZIP was from cas4.RUN, a completely different case which did not include any of the errors you showed earlier.

[Edit]:
Out of curiosity, I nonetheless tried to reproduce your errors, by creating myself a RUN file and the timeslices data file for a case that just reads the base.dd file. That test case turned out to produce errors of the same kind as you showed for your original case.

The following caused the element redefined errors:

SET TOP_IRE /
'IMPEXP'.'ELC'.'REG1'.'ELC'.'IMP_IRE_NSIC'
'IMPEXP'.'ELC'.'REG1'.'ELC'.'IMP_IRE_NSIC'
'IMPEXP'.'ELC'.'REG1'.'ELC'.'IMP_SCTLND_EWIC'
'IMPEXP'.'ELC'.'REG1'.'ELC'.'IMP_SCTLND_EWIC'
'REG1'.'ELC'.'IMPEXP'.'ELC'.'EXP_IRE_NSIC'
'REG1'.'ELC'.'IMPEXP'.'ELC'.'EXP_IRE_NSIC'
'REG1'.'ELC'.'IMPEXP'.'ELC'.'EXP_SCTLND_EWIC'
'REG1'.'ELC'.'IMPEXP'.'ELC'.'EXP_SCTLND_EWIC'
/;
As you can see, you have duplicate TOP_IRE entries created in the model, which should of course not happen, but while VEDA has this issue, I am sure you can fix the problem also by checking in your Excel templates why these duplicates are created. Maybe you have mistakenly defined those processes somehow in a way that makes VEDA generate the TOP_IRE entries two times?

The domain violations were generated from the following entries:

SET NRG_TMAP /
'REG1'.'ELCH'.'ELCH2L'
/;
SET TOP /
'REG1'.'FT-ELCH2G'.'H2G'.IN
'REG1'.'FT-ELCH2L'.'H2L'.IN
/;
The first one is a typo and easy to fix.  The two other are because the commodities H2G and H2L were not defined.  So, again easy to fix.

Dear Antti,

I haven't made any changes to the file yet, but now I am getting different errors. I uninstalled Veda and installed the latest localhost from github, but still it gave the same error. Can you please have a look at it. Thank you for your kind response and help.
Thanks

Dear Iram,

Please let me know your availability for the meeting.

[Iram]

> I haven't made any changes to the file yet, but now I am getting different errors. I uninstalled Veda and installed the latest localhost from github, but still it gave the same error.

No, it is not the same error.  Your latest error does not have anything to do with your model. The new error is related to your VEDA installation: the TIMES source code is not found. Please wait for help from the VEDA support experts, or contact VEDA support directly, if you need help troubleshooting that new error. I am sorry but I am not able to help with VEDA installation problems.

But concerning your original problem, I have given my explanations to the errors in my post above.

Dear Antti,

Your kind help is really appreciated.
Thanks

[Iram]

There was a completely different listing file in the ZIP, which was not from the run you showed earlier.  In other words, the listing file you now included does not contain the errors you showed, and therefore it does not provide any information at all to resolve your issue, sorry.

To be more precise, the earlier case with the errors you showed was casetrial.RUN, but the listing file in the ZIP was from cas4.RUN, a completely different case which did not include any of the errors you showed earlier.

[Edit]:
Out of curiosity, I nonetheless tried to reproduce your errors, by creating myself a RUN file and the timeslices data file for a case that just reads the base.dd file. That test case turned out to produce errors of the same kind as you showed for your original case.

The following caused the element redefined errors:

SET TOP_IRE /
'IMPEXP'.'ELC'.'REG1'.'ELC'.'IMP_IRE_NSIC'
'IMPEXP'.'ELC'.'REG1'.'ELC'.'IMP_IRE_NSIC'
'IMPEXP'.'ELC'.'REG1'.'ELC'.'IMP_SCTLND_EWIC'
'IMPEXP'.'ELC'.'REG1'.'ELC'.'IMP_SCTLND_EWIC'
'REG1'.'ELC'.'IMPEXP'.'ELC'.'EXP_IRE_NSIC'
'REG1'.'ELC'.'IMPEXP'.'ELC'.'EXP_IRE_NSIC'
'REG1'.'ELC'.'IMPEXP'.'ELC'.'EXP_SCTLND_EWIC'
'REG1'.'ELC'.'IMPEXP'.'ELC'.'EXP_SCTLND_EWIC'
/;
As you can see, you have duplicate TOP_IRE entries created in the model, which should of course not happen, but while VEDA has this issue, I am sure you can fix the problem also by checking in your Excel templates why these duplicates are created. Maybe you have mistakenly defined those processes somehow in a way that makes VEDA generate the TOP_IRE entries two times?

The domain violations were generated from the following entries:

SET NRG_TMAP /
'REG1'.'ELCH'.'ELCH2L'
/;
SET TOP /
'REG1'.'FT-ELCH2G'.'H2G'.IN
'REG1'.'FT-ELCH2L'.'H2L'.IN
/;
The first one is a typo and easy to fix.  The two other are because the commodities H2G and H2L were not defined.  So, again easy to fix.

Dear Antti,

I haven't made any changes to the file yet, but now I am getting different errors. I uninstalled Veda and installed the latest localhost from github, but still it gave the same error. Can you please have a look at it. Thank you for your kind response and help.
Thanks

Dear Iram,

Please let me know your availability for the meeting.

[font="Segoe UI", "Segoe UI Web (West European)", -apple-system, BlinkMacSystemFont, Roboto, "Helvetica Neue", sans-serif] Dear Ravinder,[/font]
[font="Segoe UI", "Segoe UI Web (West European)", -apple-system, BlinkMacSystemFont, Roboto, "Helvetica Neue", sans-serif]Thank you for your help.[/font]
[font="Segoe UI", "Segoe UI Web (West European)", -apple-system, BlinkMacSystemFont, Roboto, "Helvetica Neue", sans-serif]I tried a new VEDA2.0 version, restored the database from the recent backup, and during the case run, I didn’t use the latest GAMS source times (recommended when using the latest version). [/font]

[font="Segoe UI", "Segoe UI Web (West European)", -apple-system, BlinkMacSystemFont, Roboto, "Helvetica Neue", sans-serif]This issue was resolved after our meeting.[/font]