Repository navigation
Combine instrument contributions without double-counting coverage - #61
Merged
Merged
Conversation
Remove a single-study-only limit from shared responses, drop the stale browser-explorer exclusion, include pointed cases in the eval guide, and list mixed studies in the README.
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
Closes #52. Researchers can accept one study with up to six independently configured instruments across six spacecraft, then retrieve each contribution and combined geometric access.
Preserves revisions, evidence, orbit association, per-instrument illumination and full-window applicability. Applies configuration/grid/work limits before calculation with one pool of at most four workers. Shared accounting, task construction and illumination validation replace duplicated logic. Combined envelopes are explicitly contributor hulls and retain each contributor's bounds.
Evidence
After: Public MCP regressions cover acceptance and all result scopes, known-event cell unions, half-open UTC boundaries, exact simultaneous epochs, independent area within 0.001 km², nonzero real TAT-C mixed contributions and independent daylight filtering. Horizon warnings and configuration/revision error identity persist.
git diff --checkpassed.43eede5with no blocking defects. The following documentation-only commit qualifies an unverified historical eval turn cap.Merge Danger
Door: two-way
Blast Radius: server
Legacy and single-instrument regression checks pass, but shared accounting and server instructions also affect those workflows. Merging to main rebuilds/deploys the MCP image and restarts LibreChat.
Bloat review removed duplicate headers, cell aliases, repeated revisit metrics and pagination checks, and shared repeated logic. Full accepted snapshots remain in finish to preserve source evidence and rationales: about 74 KB for finish, 72 KB for preparation, and 24 KB for the largest measured fetch. This can exhaust model context. Finish is the only full-snapshot view; a client truncating it cannot retrieve the complete snapshot elsewhere. This limitation and the provider eval gaps remain documented. No new dependencies or persistent storage.