> Basically, the column previously named NCAP_BND I renamed to NCAP_BND~2025 and added another column named NCAP_BND~2050 with the same values. Will this change make sure that the model can't invest in more than 50 MW (as in the example) of storage through out all of the year between the start year 2025 and the end year 2050?
I am not sure what you mean by "can't invest in more than 50 MW through out all of the year between the start year 2025 and the end year 2050". But anyway, by just defining NCAP_BND(2025) = NCAP_BND(2050) = 50, you are bounding the new capacity that can be installed in (the period of) 2025 to 50, and similarly for (the period of) 2050. You then have no bounds for other years. I am not seeing any interpolation rule flag being used.
● If you want to limit the newly installed capacity in all periods to a certain amount, you can use an interpolation option. The option 5 together with the value NCAP_BND(2025) = 50 would limit the new capacity that can be installed in each period to 50 MW, starting from 2025. The total capacity in 2050 might of course then be much higher than 50, depending on how many periods you have between 2025 and 2050.
● If you want to limit the total installed capacity to 50 MW between 2025 and 2050, you should better use CAP_BND(2025,UP) = 50 and an interpolation option (e.g. 5).
> In this case I did define STG_LOSS / STG_EFF for the "conventional" storage investment options. Do you think this will not suffice? I mean can there be numerical problems with this particular formulation?
Yes, you did define STG_EFF for the STGHCE* technologies, and they are thus fine, as they have also their activity bounded by capacity. But many of the "Buildings Thermal Energy Storage (BiTES)" had neither the activity nor the flows bounded by anything. Such cases might potentially cause problems, but you explained that they are not "connected" to anything in the model, and if that is so, they shouldn't cause problems either. My remark was only meant as a word of warning of general nature: "In general, having storage processes with no capacity variable, or the same commodity IN and OUT, may cause numerical problems for the solver, unless the activity / flow levels are bounded in some way or have some impact on the OBJ.
I am not sure what you mean by "can't invest in more than 50 MW through out all of the year between the start year 2025 and the end year 2050". But anyway, by just defining NCAP_BND(2025) = NCAP_BND(2050) = 50, you are bounding the new capacity that can be installed in (the period of) 2025 to 50, and similarly for (the period of) 2050. You then have no bounds for other years. I am not seeing any interpolation rule flag being used.
● If you want to limit the newly installed capacity in all periods to a certain amount, you can use an interpolation option. The option 5 together with the value NCAP_BND(2025) = 50 would limit the new capacity that can be installed in each period to 50 MW, starting from 2025. The total capacity in 2050 might of course then be much higher than 50, depending on how many periods you have between 2025 and 2050.
● If you want to limit the total installed capacity to 50 MW between 2025 and 2050, you should better use CAP_BND(2025,UP) = 50 and an interpolation option (e.g. 5).
> In this case I did define STG_LOSS / STG_EFF for the "conventional" storage investment options. Do you think this will not suffice? I mean can there be numerical problems with this particular formulation?
Yes, you did define STG_EFF for the STGHCE* technologies, and they are thus fine, as they have also their activity bounded by capacity. But many of the "Buildings Thermal Energy Storage (BiTES)" had neither the activity nor the flows bounded by anything. Such cases might potentially cause problems, but you explained that they are not "connected" to anything in the model, and if that is so, they shouldn't cause problems either. My remark was only meant as a word of warning of general nature: "In general, having storage processes with no capacity variable, or the same commodity IN and OUT, may cause numerical problems for the solver, unless the activity / flow levels are bounded in some way or have some impact on the OBJ.
