Repository navigation
feat: last updates before v202611 release - #37
Merged
Merged
Conversation
danohu
approved these changes
Nov 17, 2026
danohu
left a comment
Contributor
There was a problem hiding this comment.
all looks excellent; my only quibble is that it's no longer really about 'docs'.
blallen
approved these changes
Nov 17, 2026
Member
Author
yes, the changes I added on expanded the scope beyond docs -- I changed the prefix from |
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.
Summary
Now that the
v202611global backfill has finished, we can update on compute timings and apply a bunch of QOL and performance changes. Only the last commit changes the output (adding a column totrace) -- so only that cache version needed to be bumped and refreshed.The changes
jdluc.harmonize.Stackso it is easier to backfill those from CLI in the futureharmonizeandemitwithout suffering noop long download timesjdluc.geo.clip_dsetclip allDataArray's in aDatasetat once. This showed savings of 2-3 seconds per jurisdiction/tile during attribute, bringing an expected 6h of savings for a global refresh (!)jdluc.geo.downscale_dsetdownscale allDataArray's in aDatasetat once. This showed savings of 2 minute per tile during the two statistical attribute algorithms, bringing an expected 10+h of savings for a gloabl refresh (!)DROPPEDandUNATTRIBUTEDappear in all outputs, even for jurisdictions with null resultsland_occupation_m2_year_per_kgcolumn in the trace output. Since this changed the schema, I bumped the version and refreshed thev202611results