Batchtopk into jumprelu #29
Closed
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.
Implements a BatchTopKToJump class which trains like a BatchTopK but switches to JumpRELU in inference time.
The thresholds for jumpRELU are taken from the minimum above zero latent activations during the last part of the training (last 10% by default). This results in having slightly more active latents at inference time (in my experiments it was around 106 with k=100).
Here is a notebook that runs the training and some simple evaluation, comparing the BatchTopKToJump ran in the batchTopK mode or JumpReLU mode to a classical JumpReLU or a classical TopK approach (probably could be done better).
https://colab.research.google.com/drive/1GuFaBmbVvM-rQoWjgMTZAHDxl76xaE1G?usp=sharing
Here are the three wandb runs (I ran more runs before when iterating but wanted to have just three cleaner for comparison).
https://wandb.ai/tomasdulka/batchtopk_jumprelu