Repository navigation
Conversation
Cache measured provider coordinate layouts across repeat cycles with version and chunk-set guards. Fetch demanded metadata pages concurrently outside HDF5 locks and record selection lineage. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Add test_fetch_incomplete_version_reuses_only_checksum_bound_product: fresh-process exact-product reuse and checksum mismatch remeasurement. Keep versioned cross-cycle cache guards. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Provider body enumeration is unordered. Sort all row-aligned values, flags and pixel times together. Keep native-coordinate gaps. Parameterize the native parity test over reversed entry order. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This branch has not been deployed
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.
FCI fetch currently reopens every BODY header over serial EUMDAC ranges for every repeat cycle. Reuse measured provider x/y grids on the same connector, guarded by collection, published product/processor versions, platform/encoding/processing identity, exact chunk set and requested channels. Later matching cycles select their bbox with zero metadata range calls. Changed/missing identity falls back to measured selection and records the reason in result, Dataset and canonical lineage.
Cold inspection requests demanded 4 KiB metadata pages through a bounded pool (default four workers). Inspection suspends on cache misses so network waits happen outside HDF5?s global lock. Range-refusing servers remain rejected. No hardcoded chunk layout is assumed.
Validation: 49 FCI tests pass, including 42 first-cycle versus 0 second-cycle metadata ranges for two channels; identical cached/measured entries, changed bbox and reversed entry order, version/processor/count/missing-version fallback, bounded concurrent ranges, and existing Range refusal. Full repository tests: 452 passed in an isolated editable-install environment (213 dependency warnings). Initial global-environment run had 451 passed and one installed-version mismatch (0.5.0 versus checkout 0.6.1); the isolated install resolves it.
Limits: real-header layout stability and the RefCal 25-cycle/30-minute budget remain unverified. The public PUG guide URL returned only the portal JavaScript shell. Reuse is explicitly documented as assuming stable coordinates within the guarded identity. No live EUMETSAT smoke, RefCal compute, merge or release was performed. RefCal must prove this commit cloud-side before adoption. Reuse the same FCIConnector across cycles; the cache is in memory only.
?? Generated with Claude Code