06-08-2020, 12:15 PM
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.
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.