Mikael110 commited on
Commit
80d11b9
·
verified ·
1 Parent(s): 4549330

Fix display of special tokens like <think> in readme

Browse files

When using tags like `<think>` you have to escape them using `\<think>` otherwise HuggingFace's markdown renderer will try to interpret them, and since they are not valid markdown code they will just become invsible. Which is currently the case with the readme. This change properly escape the tokens used so that they display properly.

Files changed (1) hide show
  1. README.md +4 -4
README.md CHANGED
@@ -61,9 +61,9 @@ QwQ-32B-ArliAI-RpR-v1 is the first release in the RpR series. It is a 32-billion
61
 
62
  For any reasoning models in general, you need to make sure to set:
63
 
64
- * Prefix is set to ONLY <think> and the suffix is set to ONLY </think> without any spaces or newlines (enter)
65
 
66
- * Reply starts with <think>
67
 
68
  * Always add character names is unchecked
69
 
@@ -71,13 +71,13 @@ For any reasoning models in general, you need to make sure to set:
71
 
72
  * As always the chat template should also conform to the model being used
73
 
74
- Note: Reasoning models work properly only if include names is set to never, since they always expect the eos token of the user turn followed by the <think> token in order to start reasoning before outputting their response. If you set include names to enabled, then it will always append the character name at the end like "Seraphina:<eos_token>" which confuses the model on whether it should respond or reason first.
75
 
76
  The rest of your sampler parameters can be set as you wish as usual.
77
 
78
  If you don't see the reasoning wrapped inside the thinking block, then either your settings is still wrong and doesn't follow my example or that your ST version is too old without reasoning block auto parsing.
79
 
80
- If you see the whole response is in the reasoning block, then your <think> and </think> reasoning token suffix and prefix might have an extra space or newline. Or the model just isn't a reasoning model that is smart enough to always put reasoning in between those tokens.
81
 
82
  ### If you set everything up correctly, it should look like this:
83
 
 
61
 
62
  For any reasoning models in general, you need to make sure to set:
63
 
64
+ * Prefix is set to ONLY \<think> and the suffix is set to ONLY \</think> without any spaces or newlines (enter)
65
 
66
+ * Reply starts with \<think>
67
 
68
  * Always add character names is unchecked
69
 
 
71
 
72
  * As always the chat template should also conform to the model being used
73
 
74
+ Note: Reasoning models work properly only if include names is set to never, since they always expect the eos token of the user turn followed by the \<think> token in order to start reasoning before outputting their response. If you set include names to enabled, then it will always append the character name at the end like "Seraphina:\<eos_token>" which confuses the model on whether it should respond or reason first.
75
 
76
  The rest of your sampler parameters can be set as you wish as usual.
77
 
78
  If you don't see the reasoning wrapped inside the thinking block, then either your settings is still wrong and doesn't follow my example or that your ST version is too old without reasoning block auto parsing.
79
 
80
+ If you see the whole response is in the reasoning block, then your \<think> and \</think> reasoning token suffix and prefix might have an extra space or newline. Or the model just isn't a reasoning model that is smart enough to always put reasoning in between those tokens.
81
 
82
  ### If you set everything up correctly, it should look like this:
83