PCG Observation and question

[Antti-L]

Thanks, yes, it now indeed seems to work as expected.   

[AKanudia]

THANKS 

[olexandr]

By any chance, has there been any changes to the logics described above?

I am looking into TIMES-NZ model (https://github.com/EECA-NZ/TIMES-NZ-Model-Files), and I am seeing, for example:

1) Demand process ADCF-IRG-Irg-ELC with one in/out commodity and no data defined for CG other than ACT getting ADCF-IRG-Irg-ELC_DEMO as PCG (instead of ADCF-IRG);
2) ELE process EWINDHIGHCF20 with one in/out commodity and no data defined for CG other than ACT getting EWINDHIGHCF20_NRGO as PCG (instead of ELC).

[AKanudia]

It has probably not been highlighted enough, if at all, but Veda expects a process to be defined only once. This model defines SubRES files by scenario, and this is probably what has resulted in the PCG being defined as a group created by Veda rather than the single output commodity. Information - Model - Manage Duplicates does list all the duplicate commodity and process declarations.

But does this create any issues in running the model?

[olexandr]

Thanks Amit! I did some selective checks and indeed it seems that this only occurs for the duplicated definitions.

No, the model seems to be running fine. I was just puzzled by the minor difference in the objective function when solving the model using the outputs from xl2times. Definition of PCGs (single commodity vs an actual group) seems to be the reason behind it; I guess it is contribution to peak, mentioned by Antti in the first post of the thread, that gets treated differently, but I still need to verify.