Documentation for $SET OBLONG, and its effect on lump-sum investment cost re

[KristofferEML]

Ok, thanks.

> Is there somewhere I can see what exactly is driving this gap?

Yes.  See the file VT_OBLONG_DEM.xlsx, sheet DMDDemands, cell H4.  There you specifically define a Zero value for NCAP_ILED. Using NCAP_ILED causes the technology to be modeled according to 2.a/2.b, i.e. with interest during construction included. You can see half year's interest being added to the objective function, which is in fact consistent accounting (although reporting it with/without it may be debatable). The difference between OBLONG YES/NO is that without OBLONG, the original standard assumptions are used, where NCAP_ILED has also a thershold before being applied, and therefore it falls back to cases 1.a/1.b if zero.

For an immediate remedy, I suggest to remove the NCAP_ILED(s), either directly of by TS filtering.

That's it exactly, thank you. The devil is in the detail. For my minimal demo I'd set NCAP_ILED to 0 explicitly rather than leaving it undefined, not realizing that distinction mattered, removing it resolves the reconciliation there.

For the original model, though, the situation is slightly different: here my subres file defines NCAP_ILED>0 for most technologies, and I was overriding it with NCAP_ILED = 0 in a scenario file, assuming that would have the same effect as leaving it undefined. Do you know if there is a way to achieve "undefined" state for NCAP_ILED via a scenario-file override, or is removing NCAP_ILED from the subres file the only immediate remedy (and then define NCAP_ILED in a scenario file if needed)? 

Thanks again,
Kristoffer