Add experiment lineage fields and comparison utilities #4
Conversation
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.
This is a proposal for extending experiment lineage tracking. Feedback welcome before merging.
Added:
derived_from and is_baseline fields: to track experiment lineage (helpful for quantization/intervention workflows)
experiment_signature(): auto-generates a unique ID from model + intervention + system config
compare_experiments() → shows what changed between two experiments (e.g., bitwidth, evals)
Goal: make it easier to study intervention effects (like 4-bit quant) vs. baselines and build a tree of experiment changes over time.
All changes are backwards compatible – no breakage expected.