Add Function Vectors reproduction example notebook - #667
Open
Devansh-Ruia wants to merge 5 commits into
Open
Conversation
…d Python files feat: add new py_mount CPython extension for Windows 64-bit feat: add new py_mount CPython extension for Windows 32-bit chore: add uv.lock file for dependency management
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.
Adds examples/function_vectors_reproduction.ipynb, which reproduces the function vector extraction from Todd et al. (ICLR 2024) using nnsight's tracing API.
What this does
Why
The repo has no published example linking a paper's specific result to nnsight idioms. This notebook closes that gap for Function Vectors and gives new users a reference for the trace-and-intervene pattern on real interpretability work.
How it was tested
Happy to revise based on review feedback. First contribution to the repo.