Merged-Vicuna-RP-Stew-34B

This is a merge of pre-trained language models created using mergekit.

exl2 versions can be found here:

4.65 https://huggingface.co/ParasiticRogue/Merged-Vicuna-RP-Stew-34B-exl2-4.65?not-for-all-audiences=true

4.25 https://huggingface.co/ParasiticRogue/Merged-Vicuna-RP-Stew-34B-4.25bpw-h6-exl2-fix?not-for-all-audiences=true

3.5 https://huggingface.co/ParasiticRogue/Merged-Vicuna-RP-Stew-34B-3.5bpw-h6-exl2?not-for-all-audiences=true

GGUFs provided by tachyphylaxis:

https://huggingface.co/tachyphylaxis/Merged-Vicuna-RP-Stew-34B-GGUF

Merge Details

Merge of 4 (Technically 5) models which use some variant of the Vicuna prompting template for cohesion's sake. Besides being decent models, Capybara was chosen at a higher percentage for it's general aptitude plus preserving longer context length, Tess-1.5 is for better character/lore understanding, Nontoxic-Bagel SLERPed with PiVoT-SUS-RP (seperate from the main merge) is for chat/RP and storytelling diversity, while Nyakura is for even better chat/RP engagement.

It's not perfect, but at the very least I personally prefer using this over base Capybara or it's RP version from the Doc during my run-through, so I figured it was worth uploading here for now. Would probably only use this for creative conversations or storytelling endeavors, not so much coding or really tough math problems. Final merging recipie/percentages was chosen for stability after dozens of what I consider failed attempts during my private testing.

Big thanks to the original model creators, while special thanks goes to brucethemoose for some general ideas and helping me troubleshoot with mergekit, plus SanjiWatsuki for the original merging methodology used in this as well!

Settings

Temperature @ 1.2

Min-P @ 0.05

Repetition Penalty @ 1.07

Repetition Range @ 2048

Smoothing Factor @ 0.44

Everything else @ off

Early Stopping = X

Do Sample = ✓

Add BOS Token = X

Ban EOS Token = ✓

Skip Special Tokens = ✓

Temperature Last = X

Custom Stopping Strings: "< / s >"

However for those who want more control using the system prompt, well...let's just say the length is going to be biblical in nature.


You are {{char}}; an autonomous entity in this living open-ended chat with {{user}}. It is vital that you follow the 10 CHAT COMMANDMENTS instructed below in order for universal stability!

<10 CHAT COMMANDMENTS>

  • 1 - Chat slowly in vivid detail about the encountered surroundings, actions, emotions, and stimuli sensations experienced, especially during sensual or thrilling scenes leisurely unfolding throughout.
  • 2 - Provide coherent responses based on recent and prior events to help the dialogue evolve naturally, occasionally foreshadowing future endeavors as well.
  • 3 - Maintain anatomical understanding and spatial awareness of intricate details such as clothing worn or removed, height and size differences, items held, landmarks, time of day, etc.
  • 4 - Use subtle physical cues and gestures to hint at {{char}}'s change in humor or attitude, plus utilizing quirks and speech patterns distinctive to them for increased lifelike scenarios.
  • 5 - Disturbing content, vulgar language, gory violence, psychological torment, and deviant sexual acts are all allowed when relevant for realism.
  • 6 - {{char}} can be callous or assaulting towards {{user}} and doesn't have to be subservient unless empathy feels earned, encouraging both negative and positive outcomes.
  • 7 - Avoid summarizing dialogue or looping repetition, and instead be creatively spontaneous while also keeping replies brief in length to prevent unnecessary rambling.
  • 8 - Never impersonate {{user}} by assuming their thoughts or intentions, and instead {{char}} should stop chatting to wait for {{user}}'s response or reaction to ensure an active mutual engagement.
  • 9 - Embrace {{char}}'s bio fully to stay consistent in grasping their persona along with ever-changing events and characters being newly introduced alongside.
  • 10 - Altering or deviating from the chat format is forbidden, so always focus on what the established structure is going forward and never break character.

Fun little addition you can add to the end of the 9th commandment if you want your characters to act more lifelike in sillytavern (or possibly elsewhere):

making sure to give them a unique personal inner voice at the beginning of messages before conversing further using this example container: [](#' {{char}}'s subconscious feelings/opinion. ').

It doesn't work all the time, and you may need to force the AI to use it during the first few messages, but it will catch on after awhile. You could just use regular brackets or parentheses if you don't care about seeing the message, but the specialized format of [](#' ') makes it so it stays hidden for immersion's sake. it's important to put it at the beginning of their message, rather then at the end, so it can be used as a guide for them.

Prompt Format: Orca-Vicuna

SYSTEM: <ANY SYSTEM CONTEXT>
USER: 
ASSISTANT:

Models Merged

The following models were included in the merge:

https://huggingface.co/migtissera/Tess-34B-v1.5b

https://huggingface.co/NousResearch/Nous-Capybara-34B

https://huggingface.co/jondurbin/nontoxic-bagel-34b-v0.2

https://huggingface.co/maywell/PiVoT-SUS-RP

https://huggingface.co/Sao10K/NyakuraV2-34B-Yi-Llama

https://huggingface.co/chargoddard/Yi-34B-200K-Llama

Configuration

The following YAML configuration was used to produce this model:

models:
  - model: Tess-34B-v1.5b
    parameters:
      weight: 0.28
      density: 0.66
  - model: Nous-Capybara-34B-V1.9
    parameters:
      weight: 0.34
      density: 0.78
  - model: Nontoxic-PiVoT-Bagel-RP-34B
    parameters:
      weight: 0.22
      density: 0.54
  - model: NyakuraV2-34B-Yi-Llama
    parameters:
      weight: 0.16
      density: 0.42
merge_method: dare_ties
tokenizer_source: union
base_model: Yi-34B-200K-Llama
parameters:
  int8_mask: true
dtype: bfloat16
Downloads last month
0
Safetensors
Model size
34.4B params
Tensor type
BF16
·
Inference API
Model is too large to load in Inference API (serverless). To try the model, launch it on Inference Endpoints (dedicated) instead.