Sync stopped in VEDA 2.0

[JozefO]

Hello, Did someone meet with Synchronization problem ("frozen") in VEDA 2.0. Process stopped at 81 % every-time and nothing happening?
Thank you

[Ravinder]

Hi Jozef,

Kindly share the logs files.

[AKanudia]

Can you send the model files to us?

[JozefO]

Hi Jozef,

Kindly share the logs files.

Hi Ravinder, 

There is no LOGS files because its stopped at 81 % i can only close the SYNC window and start again to Synchronization. But it's happening again and again.
I m using Veda2.0_localhost_1.161.1.1.

[Ravinder]

Hi Jozef,

Kindly share the logs files.

Hi Ravinder, 

There is no LOGS files because its stopped at 81 % i can only close the SYNC window and start again to Synchronization. But it's happening again and again.
I m using Veda2.0_localhost_1.161.1.1.

Hi Jozef,

Please find the log files under this location(Veda2.0_localhost_1.167.1.1\logs).

[JozefO]

Hi Jozef,

Kindly share the logs files.

Hi Ravinder, 

There is no LOGS files because its stopped at 81 % i can only close the SYNC window and start again to Synchronization. But it's happening again and again.
I m using Veda2.0_localhost_1.161.1.1.

Hi Jozef,

Please find the log files under this location(Veda2.0_localhost_1.167.1.1\logs).

Thank you, i found it.

[Antti-L]

I tested your model, and yes I saw the same issue.

But by correcting your SysSettings it worked:

1)  In Your Timeslices you defined ANNUAL as a SEASON; that of course won't work, if the only timeslice is ANNUAL, you need to define ANNUAL as Annual (add column Annual into ~TimeSlices, and put ANNUAL below it).
2) Add a TFM_INS table into the Constants sheet and define a discount rate for SVK (a discount rate is mandatory!)

With these corrections the Sync completed well.

You also have to change all your ANNUALL timeslice levels to ANNUAL (~FI_Process), because there is no such timeslice level as ANNUALL.

[AKanudia]

thanks Antti. We will make sure that Veda doesn't hang even with this erroneous input.

[JozefO]

I tested your model, and yes I saw the same issue.

But by correcting your SysSettings it worked:

1)  In Your Timeslices you defined ANNUAL as a SEASON; that of course won't work, if the only timeslice is ANNUAL, you need to define ANNUAL as Annual (add column Annual into ~TimeSlices, and put ANNUAL below it).
2) Add a TFM_INS table into the Constants sheet and define a discount rate for SVK (a discount rate is mandatory!)

With these corrections the Sync completed well.

You also have to change all your ANNUALL timeslice levels to ANNUAL (~FI_Process), because there is no such timeslice level as ANNUALL.

Thank you, and can i ask, did you try to SOLVE it in RUN Manager if its working  ?

[Antti-L]

No, I did not try to run the model, because you had the ANNUALL error, but I did now by replacing it with ANNUAL in the DD file.  

The run terminated into a GAMS error, because you had not defined the source groups for the FLO_EMIS attribute. FLO_EMIS(r,y,p,cg,c,ts) expects not only the emission commodity c but also the source commodity/group cg (source flow for the emission). You can define the source group by using the CommGrp column. Or, if the source should be the activity, you can use ENV_ACT instead of FLO_EMIS. I don't know which sources you have intended, and so I could not test it.

[JozefO]

No, I did not try to run the model, because you had the ANNUALL error, but I did now by replacing it with ANNUAL in the DD file.  

The run terminated into a GAMS error, because you had not defined the source groups for the FLO_EMIS attribute. FLO_EMIS(r,y,p,cg,c,ts) expects not only the emission commodity c but also the source commodity/group cg (source flow for the emission). You can define the source group by using the CommGrp column. Or, if the source should be the activity, you can use ENV_ACT instead of FLO_EMIS. I don't know which sources you have intended, and so I could not test it.

Hello Antti, I'm not sure if i understand it correctly. Can you check my SysSetting, Commodity Group if find some free time ? Or, are you able to send me some example ?

Thank you kindly.

(i m sending my SysSett.)

[Antti-L]

Hello Jozef, I'm not sure if i understand you correctly. I looked at your SysSettings, and I don't understand why you have now defined user-defined groups for the emission commodities.  Can you explain?

@Amit:  It seems there is a VEDA problem after all, with having only the ANNUAL timeslice:  Even though I defined ANNUAL in ~TimeSlices (under Annual), the ANNUAL timeslice does not get written into the *_ts.dd file.  And because that file is missing $ONEMPTY, I am now getting a GAMS error from that file.  Amit: Can you confirm/comment on this problem?  Of course, using just ANNUAL should be well supported.

[JozefO]

Hello Jozef, I'm not sure if i understand you correctly. I looked at your SysSettings, and I don't understand why you have now defined user-defined groups for the emission commodities.  Can you explain?

@Amit:  It seems there is a VEDA problem after all, with having only the ANNUAL timeslice:  Even though I defined ANNUAL in ~TimeSlices (under Annual), the ANNUAL timeslice does not get written into the *_ts.dd file.  And because that file is missing $ONEMPTY, I am now getting a GAMS error from that file.  Amit: Can you confirm/comment on this problem?  Of course, using just ANNUAL should be well supported.

Hi, i understood it this way what you wrote. My bad.
Ok so its wrong what i did in SysSett. But where i should defined Comm Grp ? FLO_EMIS~2018~CSxy is correct? what else is missing ? 

My intention is to model emissions based on combustion of (fuel mix). Each fuel mix has a different fuel input. I determined the emission commodity (CSxy) factor for a specific fuel mix and STOCK (installed resid. Capacity) is the total amount of fuel consumed in PJ-Yr.

[Antti-L]

In your SysSettings, you had defined groups for the emissions. If you mean that the emission factor is based on the whole group of input commodities, then you may want to define groups for those inputs instead. But if you want to define emission factors for a single flows or the activity, then no groups need to be defined.

For example, FLO_EMIS~2018~C1A2a is indeed correct for defining an emission factor for emission commodity C1A2a.  However, FLO_EMIS(r,y,p,cg,c,ts) expects not only the emission commodity c but also the source commodity/group cg (the source flow for the emission).  So, here c=C1A2a, but you had no cg defined in the FI_T tables.  Please just define the cg under the CommGrp (or Other_indexes) column, as follows:  

1) Add a new column with the header CommGrp (or Other_indexes).
2) Put the name of the source commodity (or a group of them) in that column under that header.

[JozefO]

In your SysSettings, you had defined groups for the emissions. If you mean that the emission factor is based on the whole group of input commodities, then you may want to define groups for those inputs instead. But if you want to define emission factors for a single flows or the activity, then no groups need to be defined.

For example, FLO_EMIS~2018~C1A2a is indeed correct for defining an emission factor for emission commodity C1A2a.  However, FLO_EMIS(r,y,p,cg,c,ts) expects not only the emission commodity c but also the source commodity/group cg (the source flow for the emission).  So, here c=C1A2a, but you had no cg defined in the FI_T tables.  Please just define the cg under the CommGrp (or Other_indexes) column, as follows:  

1) Add a new column with the header CommGrp (or Other_indexes).
2) Put the name of the source commodity (or a group of them) in that column under that header.

Emission factor is defined for one (FUEL MIX) let say IISFMIX163.   Input fuels are HFO-Heavy fuel oil and NG- Natural gas. And then 61.017 ktCO2/PJ is emission factor of ENV commodity CS163. The total emissions are = STOCK (1.50 PJyr) x CS163 (61.017ktco2/PJ) = 92.02 kt/Yr.  Soo is possible to have Input and Output like i send you ? Then CommGrp need to be on the left-hand side ? I must admit i m lost