(05-08-2020, 11:37 PM)Antti-L Wrote: I think editing that section in SysSettings by yourself is not recommended. Instead, in VEDA-FE, go to Tools --> User Options and disable the dummy imports for user constraint there.
Thank you! That's helpful. I tried just disabling Create dummy for Variables for UCs, and still got the same result. But once I disabled all the options (also imports to energy and material commodities, imports for demands) for Create Dummy, it works.
If I disable these options for Create Dummy for the new scenario where I impose the CO2 emission Cap, should I also disable this options for my base case? I tried to run the base case disabling all the Create dummy options, and it seems to give me an infeasible answer. I guess that's understandable, but will there be any recommendations of how to deal with this situation if I want to keep it consistent for all the scenarios? Thanks!
it may already be clear, but remember that the settings will take effect only for the files that are synchronized after settings are changed.
so, if I understand well, the constrained case triggers dummy imports, and you cannot disable them entirely because you need them for a feasible model to begin with. Like Antti has said before, dummy imports are meant to help you debug models while setting them up. In general, they should not be tolerated on a permanent basis. In other words, I suggest you get rid of the base case dummy imports.
However, disabling the dummy imports will *solve* your problem only if there is a valid abatement option in your model that is even more expensive than the dummy import. If this is the case then you can simply make the dummy import more expensive. browse IMP*Z processes and use TFM_UPD table to increase the cost parameter.
