Repository navigation
Conversation
Plan controlled interventions on known hard examples and add a paired CPU smoke runner using the public model-editing API. [force ci]
Add meeting decisions and checks for valid controls, seeds and budgets. [force ci]
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.
Engineers can edit a model through the merged API, but need a reproducible way to inspect a recurring failure and compare an intervention against continued training from the same checkpoint.
This draft starts that workflow with an 8 October meeting handout, a detailed proposal, proposed backend/Studio contracts, and runnable scaffolding under
wl-model-editing/hard-example-diagnostics.Proposed first milestone
Use a pretrained frozen ViT-B/16 and editable head on known Waterbirds failure groups. Compare continued training, head widening, balanced sampling, and widening plus balanced sampling across three paired seeds. Record subgroup improvement, ordinary-case regressions, and the intervention history. Follow with last-block fine-tuning and a natural-variation experiment on Oxford Pets.
The handout covers today's five decisions, ownership, a workflow diagram, the four-arm comparison, acceptance criteria and implementation gates. The contracts cover cases, snapshots, layer identity, bounded diagnostic requests, interventions and comparisons, including stale UI responses after editing. The representation and API are the architectural contribution; the prototype UI will help validate them.
Implemented in this draft
add_neuronsoperation through the public API, checks dependency propagation and optimizer references, then exports predictions and corrected/regressed case IDs.Local validation, 8 October
These are targeted local checks, not a claim that the full repository CI suite passes.
Remaining work
Real dataset adapters, pretrained feature extraction, attribution, persistent replay, new RPCs and Studio screens are planned, not implemented. Synthetic smoke metrics are not evidence of real-data improvement. Frozen-backbone attention must remain unchanged after head-only edits; output-conditioned attribution is a separate measurement.
Follows #287. Related to #267; does not close it.