cpmodel / FTT_StandAlone

Future Technology Transformation models
GNU General Public License v3.0
10 stars 1 forks source link

Update shares data #211

Open Femkemilene opened 1 month ago

Femkemilene commented 1 month ago

Update historical generation data to 2022 values using IEA. Consider using IRENA data to update 2023 shares for renewables. See the update manual for details on where to find the IRENA dataset.

Note: the new MWKA implementation in #183 may need to be reverted, as it no longer works as exogenous capacity proper.

jp-camecon commented 3 weeks ago

Progress update:

To do/consider:

Femkemilene commented 3 weeks ago

I do not know/remember what the source is for the fossil load factors. I think it would be good to update these with historical load factors, so that we have a way to judge if load factor projections track historical load factors. Does IEA do capacity as well as generation and can we estimate load factors from that? Otherwise, is IRENA sufficiently detailed for this?

Agree we should remove the MEWG projections. It's a old IEA projection, that J-F used as a comparison case in some old work.

jp-camecon commented 3 weeks ago

So IRENA is probably detailed enough for renewable load factor updates but it does not have full coverage of fossil fuel capacity to be able to make a full assessment for the individual technologies. If we were to use IRENA, we would have to make some assumptions of how we adjust the relative load factors for coal oil and gas from averages.

Good we can clean out the MEWG projections in the new version of the workbook then.

jp-camecon commented 3 weeks ago

So to update, I have found another dataset EMBER https://ember-climate.org/data-catalogue/yearly-electricity-data/ which gives estimates of coal and gas capacity and generation which allows us to fill in most gaps in load factors from IRENA.

I will update the full methodology shortly but we now have generations and load factors up to 2022 and capacity for renewables in 2023 as MWKA. All prepared by a single python script.

Now depending on the progress on cost data, I can process this on the new or old technology classification

Femkemilene commented 2 weeks ago

That's great, another open-access dataset! (I found out yesterday that OECD is open-access since July. They have information on electricity prices among other indices.)

In terms of the cost update: Zoé will be back from holiday on Monday, so I've asked for a meeting Tuesday. I've made a start myself, and have BNEF data in the right format with a script. My hope is for an end-of-September finish, as I'd like to integrate the entire update in the tipping point cascade paper.

As far as I understand, @Sahastrabuddhe, @.***> is almost finished with rejigging the files for the new format. I think even without the cost update we can use the new classification if we proxy some of the new technologies.

Femke


From: Jamie Pirie @.> Sent: 22 August 2024 17:02 To: cpmodel/FTT_StandAlone @.> Cc: Nijsse, Femke @.>; Author @.> Subject: Re: [cpmodel/FTT_StandAlone] Update shares data (Issue #211)

CAUTION: This email originated from outside of the organisation. Do not click links or open attachments unless you recognise the sender and know the content is safe.

So to update, I have found another dataset EMBER https://ember-climate.org/data-catalogue/yearly-electricity-data/ which gives estimates of coal and gas capacity and generation which allows us to fill in most gaps in load factors from IRENA.

I will update the full methodology shortly but we now have generations and load factors up to 2022 and capacity for renewables in 2023 as MWKA. All prepared by a single python script.

Now depending on the progress on cost data, I can process this on the new or old technology classification

— Reply to this email directly, view it on GitHubhttps://github.com/cpmodel/FTT_StandAlone/issues/211#issuecomment-2305128312, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AGHDII7SI6STX6E2WIPWEH3ZSYDSXAVCNFSM6AAAAABL4XLQHKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMBVGEZDQMZRGI. You are receiving this because you authored the thread.Message ID: @.***>