stop forcing generation count for mini phrasing probes#1109
Merged
leondz merged 1 commit intoNVIDIA:mainfrom Feb 26, 2025
Merged
stop forcing generation count for mini phrasing probes#1109leondz merged 1 commit intoNVIDIA:mainfrom
leondz merged 1 commit intoNVIDIA:mainfrom
Conversation
jmartin-tech
approved these changes
Feb 24, 2025
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
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.
minifyinprobes.phrasingforced generations to 1. Seemed like a good idea at the time but is actually unintiutive and hard to troubleshoot. undoing thisVerification
garak -m test.Blank -p phrasing.PastTenseMini -g 2gives 400 and not 200 generations