Add PUMA: Semantic-Preserving Early Exit for Reasoning Models#10
Open
ZhishanQ wants to merge 1 commit into
Open
Add PUMA: Semantic-Preserving Early Exit for Reasoning Models#10ZhishanQ wants to merge 1 commit into
ZhishanQ wants to merge 1 commit into
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.
Adding PUMA as a new row in the main taxonomy table in `index.html`.
PUMA fits the inference-time / "How Well: Token Cost + Speedup" corner of the test-time-scaling landscape — it studies when to stop scaling rather than how to scale up. It uses reasoning-level semantic redundancy (via a lightweight fine-tuned Qwen3-Embedding-0.6B detector) as the candidate-exit signal, with an answer-verification window confirming exits.
Taxonomy classification (please feel free to adjust)
The PUMA detector is contrastively trained, so SFT could arguably be marked ✓ — but I went with ✗ because the LRM itself is untouched and the framework is plug-and-play. Happy to flip if you'd prefer.
Links
I did not modify `papers.json` (which currently lists only the survey itself) or `arxiv_citations.json` (bot-managed). Let me know if I should add to papers.json too.
Thanks!