Veda2.0 Released!


Specifying emissions for the import process.
#1
Dear!
I am facing an issue related to constraining emission levels. Emissions (FUG-VOC) from the import process (IMPGSL1) are defined by the FLO_EMIS parameter and factored into total emissions (Y_TGHG) using the COM_AGG parameter alongside to other emission. When a constraint is applied to Y_TGHG using the COM_BNDNET parameter, the model unexpectedly increases FUG-VOC emissions (not other type emisions) from IMPGSL1 to fill the gap up to the constrained level just in periods where total emissions are below the set limit.



This behavior may be due to IMPGSL1 being an import process? I attempted to use the IRE_FLOSUM parameter (with Other_Indexes IMP~OUT~FUG-VOC) instead of FLO_EMIS, but unfortunately, this did not resolve the issue.


What am I doing wrong?
Thanks!
Reply
#2
Could you show the process topology specification?
It looks like you may have defined the emission flow as a trade flow?
Reply
#3
In case it might help, see also:  https://forum.kanors-emr.org/showthread.php?tid=1310
Reply
#4
(25-02-2025, 08:25 PM)Antti-L Wrote: Could you show the process topology specification? 
It looks like you may have defined the emission flow as a trade flow?

Sorry, but I can't get in that fast! Smile How can I see if the emission flow is defined as a trade flow?

Reply
#5
Well, I think in the latest versions of VEDA2 all the non-trade links should be shown as auxiliary flows in the RES diagram.  In your case the emission flow is not shown as such, and therefore it looks like it is a trade flow.  Try removing it from the Comm-OUT column, and just define the emissions with FLO_EMIS / IRE_FLOSUM, or add a Comm-OUT-A column for it. But if your VEDA version is old, you might still be hitting by the VEDA bug...

You can always check it ultimately from the DD files.  Blush

Anyway, just to confirm, your topology specification does indeed imply that it is trade flow. Auxiliary flows of IRE processes should not be included in the main topology (Comm-IN / Comm-OUT).
Reply
#6
Ok! VEDA v is 4000. Removing it from the tables ~FI_T column Comm-OUT and leaving it with FLO_EMIS solves the issue!!!

>>>>"Anyway, just to confirm, your topology specification does indeed imply that it is trade flow. Auxiliary flows of IRE processes should not be included in the main topology (Comm-IN / Comm-OUT)."

It's means that I should clean ~FI_T table from ENV comm just for IRE proc!?

Thanks you!!!
Reply


Possibly Related Threads…
Thread Author Replies Views Last Post
  One question of EU-TIMES: CO2 emissions for gas/oil production/transmission process [email protected] 1 609 30-05-2024, 02:58 PM
Last Post: Antti-L
  Technology emissions (upstream emissions) Burcu U. 0 429 08-02-2024, 10:05 PM
Last Post: Burcu U.
  Import/export process flows Antti-L 16 5,106 11-10-2023, 07:57 PM
Last Post: AKanudia
  Setting lower bound on sectoral emissions UKTM User 14 4,691 15-09-2023, 02:40 PM
Last Post: UKTM User
Shocked Process creates output but has no capacity nor activity Lukas Novak 3 1,555 13-07-2023, 05:26 PM
Last Post: Lukas Novak
  Process type for trade links Antti-L 6 2,281 22-06-2023, 10:56 PM
Last Post: AKanudia
  Negative dummy import variable Hesam 6 1,996 15-06-2023, 08:30 PM
Last Post: Hesam
  How to show process activity level and commodity quantity in results siyuan 1 1,101 24-05-2023, 07:09 PM
Last Post: Antti-L
  Unexpected emissions ejin 6 3,144 13-04-2023, 03:56 AM
Last Post: ejin
  Growth on CO2 emissions LucasD 1 1,054 21-11-2022, 06:06 PM
Last Post: Antti-L

Forum Jump:


Users browsing this thread: 1 Guest(s)