Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add optional aggregation with ssp population masks #36

Open
NiklasSchwind opened this issue Oct 22, 2024 · 4 comments
Open

Add optional aggregation with ssp population masks #36

NiklasSchwind opened this issue Oct 22, 2024 · 4 comments
Assignees
Labels
enhancement New feature or request preprocessing Processing data to feed into rime(X) rimeX

Comments

@NiklasSchwind
Copy link
Collaborator

We considered adding SSP population projections to the emulator. They exist as masks in 10-year steps for 2020 to 2100 and I already processed them into population weight masks and population number masks. You can find them here:

/mnt/PROVIDE/climate_impact_explorer/data/rime_masks/{iso}/masks/{iso}360x720lat89p75to-89p75lon-179p75to179p75{ssp}_{year}popWeight.nc4
/mnt/PROVIDE/climate_impact_explorer/data/rime_masks/{iso}/masks/{iso}360x720lat89p75to-89p75lon-179p75to179p75{ssp}
{year}_populationFull.nc4

The population weight masks could be used for population-weighted averages in line with the SSP population projections and the population numbers could be used to derive actual impact indicators like "population exposed to XY" in line with SSP population projections.

Implementing this additional functionality would require optionally using the masks for aggregation in the preprocessing (I think this is already possible when adding the masks to the configurations) and then correctly applying them in the emulator function. When considering the SSP population projections the emulator function would have to emulate quantile time series in a 10-year time resolution from 2020 to 2100, using the data aggregated for the correct SSP and year at every year of the time series instead of using a constant aggregation at every year of the time series as done at the moment.

I am not sure what would be the best strategy to add this to the code without complicating it too much. Ideas would be to add it as an option to the current emulator function or to write a distinct function to handle this specific case (which would then be bad for maintainability). What do you think @perrette ? And would this be an interesting direction for development @cschleussner ?

@NiklasSchwind NiklasSchwind added enhancement New feature or request rimeX preprocessing Processing data to feed into rime(X) labels Oct 22, 2024
@cschleussner
Copy link

cschleussner commented Oct 29, 2024 via email

@perrette
Copy link
Collaborator

Hi Niklas, Carl. The coding part is manageable I guess. It does increase complexity but if useful then benefit outweighs costs. In fact, it is already partly implemented in the emulator itself when dealing with Wernings et al datasets (see https://github.com/iiasa/rime/tree/rimeX?tab=readme-ov-file#match-years). Storage might be more challenging though, as it means adding another dimensions (years) in a factorial manner, i.e. this leads to 10x more storage need if we keep one population grid per decade, starting in 2010 (we must be able to use any temperature with any year).

What about the input datasets? I see an ISIMIP dataset that would do just that but it is "not available for download anymore".

@perrette
Copy link
Collaborator

perrette commented Nov 11, 2024

@perrette
Copy link
Collaborator

And of course IIASA https://iiasa.ac.at/models-tools-data/ssp
Seems an update to the SSPs is being completed (due in 2024), and links are provided to "legacy" SSP scenarios. However, I doubt the new scenarios are in a gridded format. From the few lines I could read on the outdated ISIMIP webpage linked above, and the UCAR dataset, it seems the scenarios are made for each country, and then making the grid is some kind of postprocessing step done by different groups or people. Anyway, it seems a choice between using the legacy SSP scenarios with existing gridded option (not sure which is best), or wait for some future release (that could take long).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request preprocessing Processing data to feed into rime(X) rimeX
Projects
None yet
Development

No branches or pull requests

3 participants