Repository navigation
feat: parametrize assessment year to 2020, 2022, or 2024 - #32
Merged
jeffseif merged 16 commits intoNov 11, 2026
Merged
Conversation
danohu
reviewed
Nov 10, 2026
danohu
reviewed
Nov 10, 2026
jeffseif
force-pushed
the
jeffseif/parametrize-assessment-year
branch
from
November 10, 2026 18:01
55ab004 to
561fb10
Compare
…nt year Have JD proxy adopt this same window -- allowing us to remove the awkward coupling to FAOSTAT freshness another docs update
danohu
approved these changes
Nov 11, 2026
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
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.
Background
This allows us to produce emissions factors which vary emissions, allocation, and production with assessment year. However, since
MAPSPAMandCROPGRIDShave been snapshotted at 2020, theSTATISTICALandJURISDICTIONAL_DIRECT_PROXYallocation are fixed to 2020 as well.Notes
STATISTICALuses 2020's production from MAPSPAM, and GPW livestock and CROPGRIDS stay at 2020assessment_year: inthas been added to the tabular outputs ofattributeandtraceas a new indexemit,attribute, andtracenow takeassessment_year: intas new arguments, we reset their cache versions to0Manual testing
tool.measure-driftfor (HND,STATISTICAL,2020)results shows zero drift
jdluc.tracefor2024, compared to2020drift from 2020 to 2024 is reasonable
First, generate the EF's for
HNDfor both years under both methodologies:Then, ask claude to compare them: