Extending the climate module beyond 2200

[james]

Hi all

So I am following the guidance in http://www.iea-etsap.org/docs/Climate-Beyond-EOH.pdf to extend the climate module equations beyond 2200. I have input data set up as:


CM_CONST   2200    EXT-EOH
CM_CONST       20    BEOHMOD
CM_MAXC    2005        2    DELTA-ATM
CM_MAXC    2300        2    DELTA-ATM
CM_MAXC    0        1    DELTA-ATM


and have $SET EOTIME 2300


Which works as expected - that is the climate module is ran to 2300.

However, when I change the DELTA-ATM constraint from 2300 to 2400 or more (I've tried a few values including 3000) I get the following error when syncing the scenario file:

VEDA-FE

13
VEDA-FE: Type mismatch

I note that if I simply sync, accept the error, write the dd file and then edit it to include:

PARAMETER
CM_MAXC ' '/
0.DELTA-ATM 1
2005.DELTA-ATM 2
2400.DELTA-ATM 2

the model runs fine (assuming I $set eotime 2400).

So my question is why does 2300 work and 2400 and above don't when trying to sync into VEDA-FE? Is there some hidden number checking going on?

Tthanks!

[Vikrant]

James, VEDA supports year up to 2300 only. and years greater than 2300 reported as an invalid year in import error logs. but in your case log entry suppressed by the error.

The error("type mismatch") you found during the SYNC processing was due to a concatenation bug which fixed and soon I will send you the updated version.

[james]

James, VEDA supports year up to 2300 only. and years greater than 2300 reported as an invalid year in import error logs. but in your case log entry suppressed by the error.

The error("type mismatch") you found during the SYNC processing was due to a concatenation bug which fixed and soon I will send you the updated version.

Hi Vikrant, thanks for this - much appreciated.

So just to be clear, will I be able to use years beyond 2300 with the new version? Or will I now get an invalid year error? And if so, does that prevent VEDA-FE from writing out years beyond 2300 to the .DD files?

Thanks again!

[Vikrant]

No James, I just fix the "type mismatch" error in the new version. years >2300 still not identify by the VEDA but you will get the invalid year message for such years.

Yes right now, VEDA-FE can't write years beyond 2300 in the dd files. I don't have much knowledge of TIMES, But I think we can change this constraint if years beyond 2300 making any sense in TIMES.

So let's see what others are thinking about this.

[Antti-L]

There is basically no limit in TIMES for the years into the future; it only requires setting EOTIME accordingly.

You could thus even analyse the energy system development into the next millennia, which I am sure would be interesting.     Or one can just use the extended horizon for the climate module.

Why is it so that 2300 has the been defined as a limit in VEDA-FE?

[james]

No James, I just fix the "type mismatch" error in the new version. years >2300 still not identify by the VEDA but you will get the invalid year message for such years.

Yes right now, VEDA-FE can't write years beyond 2300 in the dd files. I don't have much knowledge of TIMES, But I think we can change this constraint if years beyond 2300 making any sense in TIMES.

So let's see what others are thinking about this.

The use case here is primarily to extend the climate module equations out far enough so that the module can "see" the impact of having positive global net CO2 emissions in 2100.

Our current set up constrains DELTA-ATM (global temperature) to be 2 degrees in 2100 and 2 degrees in 2200. In certain cases TIAM then finds an optimal energy system with positive net CO2 emissions in 2100 which meets both constraints but would lead to DELTA-ATM greater than 2 degrees post 2200 which is not desired. This occurs because DELTA-ATM is 2 degrees in 2100 then smoothly reaches a minimum below 2 degrees between 2100-2200 and starts to increase again up to 2 degrees in 2200.

So, the work around here that I have tested is to extend the climate module equations out further (well beyond 2300). This results in much lower positive net CO2 emissions in 2100 and, as a result, an energy system that more appropriately reflections global climate policy objectives. The main problem now is that VEDA-FE can't handle years beyond 2300 even though TIMES can. I don't really want to have to edit the .DD file every time - particularly when running batch cases.

I think Antti-L's question is a good one.

[AKanudia]

OK, we will remove this limit

[james]

OK, we will remove this limit

Great to hear, thanks Amit. Do you have any idea when a version of VEDA will be available without this limit?

[Vikrant]

James, The limit(up to 2300 only) on year has been removed. So please get the updated version by using latest VedaInstaller.