Stop keywords about llama.cpp

[Bec-k]

Stop token, generative model should be stopped when generation encounters stop token. I haven't found that in the cli. I suppose you have it built-in for each supported model.

[Bec-k]

Was surprised that there is no such setting by default in the --help, is it implemented or is considered out of scope for this project?

[blackhole89]

The [end of text] output corresponds to a special token (number 2) in the LLaMa embedding. As for stopping on other token strings, the "reverse prompt" parameter does that in interactive mode now, with exactly the opening post's use case in mind. Is there a use case for something like it in non-interactive mode?

[KevinColemanInc]

[end of text] is 5 tokens.

   518 -> ' ['
   355 -> 'end'
   310 -> ' of'
  1426 -> ' text'
 29962 -> ']'

I looked in the vocab file to see if there are any uncommon long tokens that would be cheaper stop tokens and I found arquitect to be a single token that I don't expect to show up in the dialogue.

28827 -> ' arquitect'

[petergeneric]

Yeah, it would just be useful to have more control over that in cases where the model itself doesn't want to stop

[j-f1]

It could be useful for cases where you want to pull structured data out of the model (for example, asking for a city’s population, then reading tokens up until the next whitespace to get the number out).

[DavidCWGA]

It is absolutely useful in non-interactive mode. In any "conversation"-style input it prevents the model from talking to itself. To really make this useful you would need a switch that would stop the program re-printing the prompt, and only printing the new generated output.

[j-f1]

[end of text] is actually a single token (sometimes represented as </s> but llama.cpp translates it as the empty string by default) that we have special behavior for.

[KevinColemanInc]

Ah, i see. I guess this #365 doesn't work, because you can't encode the stop token as a string literal. So you have to use another set of tokens, which doesn't always work.

[jminardi]

I believe there already are stop keywords. At least some of my responses end with [end of text] before the character limit.

[DavidCWGA]

Yes, seconding this. It's sometimes very important to set a name prefix or even a newline character as the stop keyword.

[Foundation42]

These stop keywords would have to be recorded in token space, and at each token generated a check for possible match made. Seems like the right way to do that would be state machine.

there may be other uses down the line where a callback is called every time a match is made, which could be useful for implementing "actions", although may be outside of the scope here idk

[KevinColemanInc]

@j-f1 Why does my llama.cpp logs show 5 tokens (see above)? I am using the stop-keywords code.

[j-f1]

That’s because you’re trying to tokenize that literal string — if you search in the source code for "[end of text]" you’ll see where it gets printed out.

[dwillie]

Should this be considered resolved by #1032 ? The chain of closed-in-favor-of lead me there, but it doesn't actually refer back to this issue.

[ejones]

Seems reasonable to me.

[Green-Sky]

@Bec-k can you elaborate on what you think is not implemented?

[talwrii]

This is the -r option at the command line.

-r,    --reverse-prompt PROMPT  halt generation at PROMPT, return control in interactive mode`

[0wwafa]

if I do: -r "<|im_end|>" it does not work and continues.