Update guidance to point to non-contiguous time#448
Draft
znichollscr wants to merge 1 commit into
Draft
Conversation
znichollscr
commented
Jun 16, 2026
Comment on lines
+288
to
+290
| 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. |
Collaborator
Author
There was a problem hiding this comment.
@jkikstra @eahoegner @mzecc can you please double check this
znichollscr
commented
Jun 16, 2026
| 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. |
Collaborator
Author
There was a problem hiding this comment.
@jkikstra @eahoegner @mzecc can you please double check this. I think we have a difference in names for NMVOCs?
znichollscr
commented
Jun 16, 2026
Comment on lines
+293
to
+302
| 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, ...))$. |
Collaborator
Author
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Closes #447
Checklist
Please confirm that this pull request has done the following:
Data released on ESGFESGF update pulled in herechangelog/