search

ecwood / GCAM-CDR-modeling

1 stars 0 forks source link

Learn How to Constrain Scenario by Temperature #28

Open ecwood opened 1 year ago

ecwood commented 1 year ago

This is one possible avenue for the second bullet point in this comment: https://github.com/ecwood/GCAM-CDR-modeling/issues/16#issuecomment-1198373602

ecwood commented 1 year ago

Here's the output of the temperature constrained scenario I ran on Friday. (The instance claimed to run out of space, so the XML didn't finish outputting. Therefore, I had to create a new script, bed30e3, to extract the data I could from it). debug_db_processed.log

ecwood commented 1 year ago

I reran the 2° base scenario with more space on the instance so that the run would finish the output. For the US, that resulted in these levels of DAC deployment (in MtC), using d7e2a35:

{
    "2025": 0.002744326369302,
    "2030": 0.02537442997089,
    "2035": 0.17376643928080004,
    "2040": 0.9318608219200004,
    "2045": 3.1982017382399994,
    "2050": 11.999636487989997,
    "2055": 14.591708684869996,
    "2060": 19.191945179639994,
    "2065": 23.794332040520008,
    "2070": 28.724349218460002,
    "2075": 33.1420436019,
    "2080": 37.86237672109999,
    "2085": 44.2998485903,
    "2090": 52.7065214983,
    "2095": 53.40823472503002,
    "2100": 57.12493976265998
}

Next, I need to look at renewable energy deployment and save those values so I can compare them when more DAC is in later scenarios.