Skip to content
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

Maybe n_keep is missing for llama.cpp #73

Open
leucome opened this issue Jan 4, 2024 · 3 comments
Open

Maybe n_keep is missing for llama.cpp #73

leucome opened this issue Jan 4, 2024 · 3 comments
Labels

Comments

@leucome
Copy link

leucome commented Jan 4, 2024

I felt like the chat bot was losing memory when I went over the context size. I done a search of n_keep in amica project files to specify the amount of initial token I want llama.cpp to keep. Then I could not find any mention of n_keep in the code.

I would like to make sure it keep all the initial prompt. I dont want the chat bot to lose track of who it is the middle of a conversation.

Until then I will try changing llama.cpp server default.

@kasumi-1
Copy link
Contributor

kasumi-1 commented Jan 4, 2024

Hi!

Yes, I think it would be nice if all of these sorts of options could be specified (maybe in advanced setting) for different backends.

@leucome
Copy link
Author

leucome commented Jan 6, 2024

Yes, I think it would be nice if all of these sorts of options could be specified (maybe in advanced setting) for different backends.

While setting up a character, I though that it would be convenient if the backends/advanced setting could also be attached to the character cards.

@slowsynapse
Copy link
Collaborator

Arbius has a $200 AIUS bounty for this issue!

Brief: Add advanced settings to include n_keep , context size, and also ability to save these in a user built list (e.g. for a particular model)

Please read carefully:

To begin work on a bounty, reply by saying “I claim this bounty” - you will have 48 hours to submit your PR before someone else may attempt to claim this bounty.

To complete the bounty, within 48 hours of claiming, reply with a link to your PR referencing this issue and an Ethereum address. You must comply with reviewers comments and have the PR merged to receive the bounty reward. Please be sure to focus on quality submissions to minimize the amount of time reviewers must take.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants