Skip to content

Update guidance to point to non-contiguous time #448

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.

Sign up for GitHub

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

Draft
znichollscr wants to merge 1 commit into
base: main
Choose a base branch
from
Draft

Update guidance to point to non-contiguous time #448

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
17 changes: 15 additions & 2 deletions docs/dataset-overviews/anthropogenic-slcf-co2-emissions.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -285,8 +285,21 @@ Note there is a variable naming inconsistency for these file - described in the

The data for ScenarioMIP comes from a range of IAMs,
rather than the CEDS consortium.
[TODO: any information about how ScenarioMIP files differ from the DECK files.
There shouldn't be any major differences]
The file naming and general format is the same as the historical.
The key difference is that the data is not contiguous in time,
but instead is provided as monthly data for specific years.
Comment on lines +288 to +290

@znichollscr znichollscr Jun 16, 2026

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@jkikstra @eahoegner @mzecc can you please double check this

Your code will have to handle this,
and you will have to interpolate between these timesteps yourself.
If you do not have any existing interpolation methods,
our suggestion is to linearly interpolate based on the monthly data
i.e. $E(y, m, ...) = E(y_0, m, ...) + \frac{y - y_0}{y_1 - y_0} \cdot (E(y_1, m, ...) - E(y_0, m, ...))$,
where $y$ is the year and $m$ is the month for which your are generating interpolated data,
$...$ represents non-time (i.e. spatial) dimensions,
$y_0$ is the previous year for which there is data in the forcings dataset
and $y_1$ is the next year for which there is data in the forcings dataset.
For example, assuming the data is reported for 2030 and 2035 in the forcings dataset,
values for a given month in 2032 would be given by
$E(2032, m, ...) = E(2030, m, ...) + \frac{2032 - 2030}{2035 - 2030} \cdot (E(2035, m, ...) - E(2035, m, ...))$.
Comment on lines +293 to +302

@znichollscr znichollscr Jun 16, 2026

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@jkikstra @vnaik60 are you happy with this guidance? Or is there something smarter that we can write here?

@penguian penguian Jun 19, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just make it clear that months need to be interpolated separately to preserve the monthly variation within each interpolated year.


<!--- begin-revision-history -->
<!--- Do not edit this section, it is automatically updated when the docs are built -->
Expand Down
17 changes: 15 additions & 2 deletions docs/dataset-overviews/open-biomass-burning-emissions.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -315,8 +315,21 @@ Apply the 1850 values on repeat.

The data for ScenarioMIP comes from a range of IAMs,
rather than the CEDS consortium.
[TODO: any information about how ScenarioMIP files differ from the DECK files
There shouldn't be any major differences except maybe naming of VOCs.]
The file naming and general format is the same as the historical.

@znichollscr znichollscr Jun 16, 2026

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@jkikstra @eahoegner @mzecc can you please double check this. I think we have a difference in names for NMVOCs?

@penguian penguian Jun 19, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The CEDS and IIASA-IAMC datasets differ in their definition of sector. Also the CEDS datasets include separate percentage files and the IIASA-IAMC datasets do not.

See ACCESS-NRI/CMIP7-Input#134

The key difference is that the data is not contiguous in time,
but instead is provided as monthly data for specific years.
Your code will have to handle this,
and you will have to interpolate between these timesteps yourself.
If you do not have any existing interpolation methods,
our suggestion is to linearly interpolate based on the monthly data
i.e. $E(y, m, ...) = E(y_0, m, ...) + \frac{y - y_0}{y_1 - y_0} \cdot (E(y_1, m, ...) - E(y_0, m, ...))$,
where $y$ is the year and $m$ is the month for which your are generating interpolated data,
$...$ represents non-time (i.e. spatial) dimensions,
$y_0$ is the previous year for which there is data in the forcings dataset
and $y_1$ is the next year for which there is data in the forcings dataset.
For example, assuming the data is reported for 2030 and 2035 in the forcings dataset,
values for a given month in 2032 would be given by
$E(2032, m, ...) = E(2030, m, ...) + \frac{2032 - 2030}{2035 - 2030} \cdot (E(2035, m, ...) - E(2035, m, ...))$.

<!--- begin-revision-history -->
<!--- Do not edit this section, it is automatically updated when the docs are built -->
Expand Down
Loading