Small follow-up: The model you attached initially solved in 3695 seconds on my computer, which is a rather long time to wait. For curiosity, I tested if I can reduce the solution time by improving the numerical stability of the model. After only a few small adjustments, the solution time was reduced to 192 seconds. The time savings were thus about 95%. So, I think that may already demonstrate that your original model might well be characterized as badly scaled (there were indeed some very high / very low coefficients and some very high marginal prices).
In case it is of interest, the adjustments I made were the following:
• I removed dummy import flows from the model (had to add some supply of DEMHYGNINDcap & DEMHYGNINDmer in 2017)
• I disabled the dummy import processes (IMPNRGZ, IMPMATZ, IMPDEMZ) altogether
• I defined OILRES, OILCOM, GASRES and GASCOM at the ANNUAL level (DAYNITE was a bad choice, because the fuel techs were ANNUAL)
• I scaled your car-kilometres to billion vkm, to get a reasonable efficiency of 1.094 vkm/MJ for H2TRACAR (instead of ACT_EFF=1094238126)
• I set all ACT_COST that were defined between 0 and 1e−3 to 1e−3
• I set all NCAP_COST and NCAP_FOM that were defined below 1e−3 to zero
• I set all NCAP_AF(UP) that were defined below 1e−3 to zero.
In case it is of interest, the adjustments I made were the following:
• I removed dummy import flows from the model (had to add some supply of DEMHYGNINDcap & DEMHYGNINDmer in 2017)
• I disabled the dummy import processes (IMPNRGZ, IMPMATZ, IMPDEMZ) altogether
• I defined OILRES, OILCOM, GASRES and GASCOM at the ANNUAL level (DAYNITE was a bad choice, because the fuel techs were ANNUAL)
• I scaled your car-kilometres to billion vkm, to get a reasonable efficiency of 1.094 vkm/MJ for H2TRACAR (instead of ACT_EFF=1094238126)
• I set all ACT_COST that were defined between 0 and 1e−3 to 1e−3
• I set all NCAP_COST and NCAP_FOM that were defined below 1e−3 to zero
• I set all NCAP_AF(UP) that were defined below 1e−3 to zero.