ufl

joined 5 days ago
[–] ufl 1 points 4 days ago* (last edited 4 days ago)

I noticed from my tries that RAGs do not affect AI output as much. When I put text into prompt AI tends to quote from it or ignore what I said completely lol. RAGs are more like telling AI: "here's a document/documents that you have to look through every time you generate output" and it just does it

[–] ufl 2 points 5 days ago

Thanks for this tip, I don't have a lot of VRAM just 64GB of regular RAM, but I don't mind waiting for output :)

But anyway, all non-Llama model weren't so good and using RAG in plug-and-play mode, probably I should've spent more time working on system prompt and jinja as well as RAG curation to squeeze all juices, but I wanted something quick and easy to setup and for this needs Llama 3.2 8B Instruct was the best. I used default setup for all models and same system prompt.

Also, new Qwen reasoning model was good, it was faster in my setup, but was too "independent" I guess, it tended to ignore instructions from system prompt and other settings, while Llama was more "obedient".

[–] ufl 3 points 5 days ago* (last edited 5 days ago) (2 children)

This is probably true, I don't have a lot of experience with RAGs from dev side, I was just a user.

From my attempts with small structured data like <1000 words all Llama family AIs were good at "consuming" it without any additional preparations, just "plug and play". If you want to feed your AI whole wikipedia you most likely will need to curate data first to get reliable results, yes. But for casual usage for ensuring that AI won't forget or ignore some rules and be aware of present context it was enough. I was running Llama 3.2 8B Instruct with Q4 and Q8 and I believe this is the family of AIs that perchance uses for text generation. I was satisfied with results. Probably they were not ideal, but noticeably better with just default RAG and just some .txt file with markdown-like structured list, .json was also good. If it were up to me, I would incorporate it as a optional feature and left it up to users to evaluate results.

In chat text generators at perchance there's a feature "reminder note", this is basically a text that goes before AI output. Could've been useful, but AIs tend to directly quote from it. There's also /mem and /lore but UX of using it as some sort of RAG and especially live (where you constantly update it based on AIs output) one is not so great and it is not rare that AI just ignore it and makes something up.

Qwen and Mistral family was not so good with default RAGs and simple structured files in my tests btw, Llama had best results.

Thanks for tip on Storm, will look into it.

3
submitted 5 days ago* (last edited 5 days ago) by ufl to c/perchance
 

Hi, I've been playing with some AI models on my machine in GPT4ALL software and it have this thing called "LocalDocs".

It looks like it is just a RAG for AI and simple structured text document is more that enough for casual usage. Document like this was more than enough for Llama 3.x to be aware of dates and current state:

{
    "Today": "12-Dec-2024",
    "Tomorrow": "13-Dec-2024",
    "Deadline": "23-Dec-2024",
    "Tasks Left": [
        {"Task Name": "Get groceries"},
        {"Task Name": "Buy presents"}
    ]
}

Can perchance have something like that or is it up to generator creator to setup RAG?

In my experience, text AIs tend to ignore or forget information very quickly. Before setting RAG up I was constantly correcting AI about everything, but after getting RAG, AI worked flawlessly.

Also, RAGs seems to not increase context size. It looks like AI just uses it during generation and then forgets, so context is increased only by AIs reply.

To sum up, I've found this thing very useful, it will be super helpful for all text generators, especially for generators like where AI must be aware of some persistent context like world rules, story characters, etc. Here's couple of examples:

But all generator authors and users will benefit from this.

Note: If decided to implement, please don't make it as a file upload. This is how RAG is implemented in LM Studio and it is really annoying to delete previous document and upload new one. Live editor is significantly better.