-
Notifications
You must be signed in to change notification settings - Fork 5.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Top_P,Top_K and Min_P arguments for ollama models #3873
Comments
Please read the documentation on Ollama usage: https://microsoft.github.io/autogen/0.2/docs/topics/non-openai-models/local-ollama#api-parameters
|
@ekzhu Actually it is not working ..
I think there is an implementation error:
Even though document mentions this is possible. |
@marklysze is this something you can take a look at? |
@ekzhu @marklysze One fix could be adding the temperature,top_k etcg in the options dictionary.
This does not create any issues but I am not sure if ollama is honoring these options or simple ignoring. |
@athmanar, would you be able to provide a simple code example with agents and messages and I'll test it |
The simple code snippet would be like this:
So basically this gives the error : |
Thanks, let me try it out (though can't run 70b so will run a smaller model ;) ) |
Okay, yes, Ollama has recently changed the handling of a few parameters and moved them to the options dictionary. I'll put through a PR to update this repository. The repo for package |
@athmanar, please see PR 3952, you can try replacing your ollama.py file and see if it fixes it for you. It worked for me with your code. |
Okay, so it looks I already corrected it 3 weeks ago #3593. So it's probably a version thing. So in this repo, this file is the latest one: If you're using the Can you try to update your package or replace your |
@marklysze I can confirm that this now works. I replaced only the ollama file. |
Hello,
I don't understand how to set the parameters for ollama models.
This is my configuration:
It seems only top_p is supported? Am i missing something?
The text was updated successfully, but these errors were encountered: