You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
The frequency_penalty parameter in the model.yml file only functions correctly when its value is set to 1. The model generates gibberish responses when the value is set to 0 or 0.5.
To Reproduce
Steps to reproduce the behavior:
Go to the model.yml file.
Set the frequency_penalty parameter to 0.
Run the model and observe the responses.
Repeat steps 2 and 3 with frequency_penalty set to 0.5.
Set the frequency_penalty parameter to 1 and observe the responses.
Expected behavior
The model should produce coherent and contextually appropriate responses regardless of the frequency_penalty value, whether set to 0, 0.5, or 1.
Screenshots
Additional context
This issue affects the consistency and reliability of the model's output, impacting its usability in applications that rely on varied frequency_penalty settings for diverse response generation.
The text was updated successfully, but these errors were encountered:
dan-menlo
changed the title
bug: frequency_penalty Parameter in model.yml Only Functions Correctly with Value 1, Produces Gibberish for other values
bug: TensorRT-LLM frequency_penalty Parameter in model.yml Only Functions Correctly with Value 1, Produces Gibberish for other values
Oct 31, 2024
Describe the bug
The
frequency_penalty
parameter in themodel.yml
file only functions correctly when its value is set to 1. The model generates gibberish responses when the value is set to 0 or 0.5.To Reproduce
Steps to reproduce the behavior:
model.yml
file.frequency_penalty
parameter to 0.frequency_penalty
set to 0.5.frequency_penalty
parameter to 1 and observe the responses.Expected behavior
The model should produce coherent and contextually appropriate responses regardless of the
frequency_penalty
value, whether set to 0, 0.5, or 1.Screenshots


Additional context
This issue affects the consistency and reliability of the model's output, impacting its usability in applications that rely on varied
frequency_penalty
settings for diverse response generation.The text was updated successfully, but these errors were encountered: