remind issueshttps://gitlab.pik-potsdam.de/hilaire/remind/-/issues2020-02-11T16:00:01+01:00https://gitlab.pik-potsdam.de/hilaire/remind/-/issues/41Weired special case in q_emiTeDetail2020-02-11T16:00:01+01:00Michaja PehlWeired special case in q_emiTeDetailhttps://github.com/remindmodel/remind/blob/08e58efe626352b7963575d3c6e13436e3322dd4/core/equations.gms#L478-L502
I don't see any point in (and am confused by) the `OR (pe2se(enty,enty2,te) AND sameas(enty3,"cco2"))` part. This would ...https://github.com/remindmodel/remind/blob/08e58efe626352b7963575d3c6e13436e3322dd4/core/equations.gms#L478-L502
I don't see any point in (and am confused by) the `OR (pe2se(enty,enty2,te) AND sameas(enty3,"cco2"))` part. This would come into play for combinations of `(pety,sety,te,"cco2")` that are not present in `emi2te` yet have non-zero data in `pm_emifac`. This might happen if new data is included in `./core/input/generisdata_emi.put`, but is not the case at the moment.
However, these entries would be excluded from the equation in any case, since it sums over `emi2te`, of which they are not a part. (Incidentally, this sum does nothing productive besides excluding the non-existent cases that were manually included.)
Do you have any idea what was the reasoning behind this? I will delete it, unless there's some foreseeable edge-case where this is necessary.