In the image gen space which is mildly better but still not great we would just assign a positive or negative weight to the item. E.g. (seaborn:-1.3). This is a bit harder in LLMs as designed because the prompting space is a back and forth conversation and not a description of itself. It would be nice if we could do both more cleanly separated.
If you ever try to read a doc into chat gpt and get it to summarize n ideas in a single prompt, remember that this is open AI’s fault. What we should be doing is caching the vector representing the doc and then passing n separate queries to extract n separate ideas about the same vector.
I think you're right, but it will require moving to more recurrent architectures.
Ah! This.-
PS. Who knows. This ("dealing with the vectors") might become analogous to open sourcing" some day ...You could A) have the LLM ingest and reprocess the same prompt every single time at needless cost
Or
B) process it one time and reuse the vector embedding of the prompt
OpenAI forces you to do A.
Besides that, in transformer models, the computation of each token’s output vector in a sequence depends on all other tokens in the sequence due to the self-attention mechanism. This interdependency means that you cannot simply "reuse"/add on to an existing processed sequence without re-processing the entire sequence, as the presence of new tokens (user input) alters the calculations of the attention mechanisms throughout the sequence.
So what you basically proposing is not possible in current architecture.
So when transformers process an input sequence, they don't just look at each token in isolation but consider the ENTIRE sequence's context through complex inter-token relationships. This makes the technique of caching outputs non-trivial and context-specific. The sequential processing does not imply independence of tokens but underscores the integral role of context and sequence in generating accurate and coherent outputs.
This should help you understand better how transformers work: https://bbycroft.net/llm
You want to reuse the embedding representation of the prefix prompt before the new user tokens are confiscated, otherwise you are recalculating the embedding over and over and over. God forbid it’s not a small prefix but a huge document.
If tokens 1:3000 are the same you are going to be doing the same work processing them over and over; and then changing the results to adapt to the user tokens at the end.
Every time a token is processed in a transformer, the model computes its attention relative to ALL other tokens in the sequence. This is a key difference from sequential, step-by-step processing where previous states are incrementally built upon (so your :n, :n-1 etc). The attention mechanism in transformers recalculates the relationships for EACH token with ALL other tokens EVERY time any part of the input sequence changes.
When new tokens are added to the sequence (for example user input after a system prompt), the attention relationships for ALL PREVIOUS tokens can change. This is because the context provided by the new tokens can alter the relevance and interpretation of the earlier tokens. As such, the attention scores and subsequently the output embeddings for all tokens are recalculated to integrate this new information. So as you can see, you are not doing the same work over and over.
I hope this helps you better understand how transformers work.
"Do we have to use matplotlib? Sounds like he wants us to but we don't have to, but we definitely shouldn't use seaborn? What does he want anyway?"
I mean they already repeated the instruction in different words, they already resorted to shouting. What is next? Swearing? Intimidation? Threat of physical harm?
Please read our peer-reviewed white-blog-paper for Proof-Of-Safety (POS) https : //trust-me-bro.org/torturing-llms--it-just-works.php
from systemprompts import prettyplease :)It was a facepalming experience but in the end the results were actually pretty good.
Biological neural networks are also still largely black boxes to us. But they and ANNs won't be forever, even if it takes a long time.
No one would have predicted a future where programming is literally yelling at an LLM in all caps and repeating yourself like you’re yelling at a Sesame Street character.
Reality is stranger than fiction.
Skyking do not answer
This kind of stuff always makes me a little sad. One thing I've loved about computers my whole life is how they are predictable and consistent. Don't get me wrong, I use and quite enjoy LLMs and understand that their variability is huge strength (and I know about `temperature`), I just wish there was a way to "talk to"/instruct the LLM and not need to do stuff like this ("I REPEAT").