VedaSupport Forum
Model infeasible regardless of CO2 limit- not sure why? - Printable Version

+- VedaSupport Forum (https://forum.kanors-emr.org)
+-- Forum: VEDA Front End (https://forum.kanors-emr.org/forumdisplay.php?fid=2)
+--- Forum: Questions and Observations (https://forum.kanors-emr.org/forumdisplay.php?fid=7)
+--- Thread: Model infeasible regardless of CO2 limit- not sure why? (/showthread.php?tid=799)



Model infeasible regardless of CO2 limit- not sure why? - ach - 09-12-2019

Hello, I am working on a model that multiple people are collaborating on. Not sure what's causing this, but simply incorporating a CO2 bound causes the model to become integer infeasible. Not sure why. When I remove the CO2 scenario file from the case manager, the model works. But as soon as I incorporate the CO2 bound, regardless of how relaxed my CO2 upper limit is, I keep getting the integer infeasible error or the dummy import process IMPDEMZ kicks in (if enabled). Could you please suggest what may be causing this? Thank you.


RE: Model infeasible regardless of CO2 limit- not sure why? - ach - 10-12-2019

Following up on my previous question (please see attached model): 1. Some timeslices (SNN - summer night nowind - wind AFA=0, SNW - summer night wind - AFA !=0) have been created to introduce a notion of variability of wind. I have been told the goal was to get wind and natural gas to deploy in a 1:1 ratio. Instead this is causing no wind to be deployed. Could this be causing the model to be infeasible? Is there a better way to approach this? 2. 2013-16 power generation figures are setup as an initial condition with power generation figures from actual data. The idea is to force a certain energy mix and a certain amount of emissions which then have to be mitigated. I can see that the supply exceeds the demand TPSELC by a significant margin, but IMPDEMZ is still being triggered for these years. Why? Thanks.


RE: Model infeasible regardless of CO2 limit- not sure why? - Antti-L - 10-12-2019

(10-12-2019, 01:07 AM)ach Wrote: 1. Some timeslices (SNN - summer night nowind - wind AFA=0, SNW - summer night wind - AFA !=0) have been created to introduce a notion of variability of wind.
1. I hope you are aware that NCAP_AFA (aka AFA in VEDA) defines an ANNUAL utilization factor. There is no timeslice index in NCAP_AFA. If you define AFA(UP)=0, the process cannot produce anything at any timeslice. If your purpose is to define timeslice-specific availabilities, please use the parameters for defining timeslice-specific availabilities: NCAP_AF, or NCAP_AFS. 2. I had a look at the attachment to see if I can help, but it included only VEDA templates, and not the model input files for TIMES (*.DD, *.RUN), nor the listing file (*.LST). So, looks like I cannot be of any help with that.