Gemini last models: temperature, top_p, and top_k are deprecated and ignored
1–10 of 53 posts
Re: Gemini last models: temperature, top_p, and top_k are deprecated and ignored
#2temperature, top_p, and top_k are deprecated and ignored. In future model generations, supplying these parameters returns an HTTP 400 error. Remove these parameters from all requests.
Re: Gemini last models: temperature, top_p, and top_k are deprecated and ignored
#3Is this guaranteed to work any better than top_k or top_p? This just sounds like making a smaller version of a Agent.md doc.
Re: Gemini last models: temperature, top_p, and top_k are deprecated and ignored
#4Re: Gemini last models: temperature, top_p, and top_k are deprecated and ignored
#5Re: Gemini last models: temperature, top_p, and top_k are deprecated and ignored
#6My guess is that RL training being done with particular generation parameters makes models much more brittle to changes in these parameters, and that's why we're seeing changes like this across model providers. But I don't really know.
Re: Gemini last models: temperature, top_p, and top_k are deprecated and ignored
#7Re: Gemini last models: temperature, top_p, and top_k are deprecated and ignored
#8https://gist.github.com/Hellisotherpeople/71ba712f9f899adcb0...
Re: Gemini last models: temperature, top_p, and top_k are deprecated and ignored
#9My guess is that RL training being done with particular generation parameters makes models much more brittle to changes in these parameters, and that's why we're seeing changes like this across model providers. But I don't really know.
Re: Gemini last models: temperature, top_p, and top_k are deprecated and ignored
#10My guess is that RL training being done with particular generation parameters makes models much more brittle to changes in these parameters, and that's why we're seeing changes like this across model providers. But I don't really know.