>>106628629
>By using the correct one for the model. Look at the contents of the config.json file in the model's repo.
What am I looking for?:
{
"_attn_implementation": "eager",
"architectures": [
"Ernie4_5_MoeForCausalLM"
],
"bos_token_id": 1,
"eos_token_id": 2,
"hidden_act": "silu",
"hidden_size": 2560,
"intermediate_size": 12288,
"max_position_embeddings": 131072,
"model_type": "ernie4_5_moe",
"moe_capacity": [
64,
64,
64
],
"moe_gate": "top2_fused",
"moe_intermediate_size": 1536,
"moe_k": 6,
"moe_layer_interval": 1,
"moe_layer_start_index": 1,
"moe_num_experts": 64,
"moe_num_shared_experts": 2,
"moe_use_aux_free": true,
"num_attention_heads": 20,
"num_hidden_layers": 28,
"num_key_value_heads": 4,
"pad_token_id": 0,
"rms_norm_eps": 1e-05,
"rope_theta": 500000,
"tie_word_embeddings": true,
"torch_dtype": "bfloat16",
"use_bias": false,
"use_cache": true,
"vocab_size": 103424
}
The context template is an ST thing, why would the upstream model know about it anyway?
>Just use the chat completion API and let the backend format the prompt with the appropriate template.
I did try this but also
>If you intend to use this feature to use a local endpoint, like TabbyAPI, Oobabooga, Aphrodite, or any like those, you might want to check out the built-in compatibility for those instead. The custom endpoint feature is mainly intended for use with other services and programs that expose an OpenAI-compatible API Chat Completion endpoint.
>Most Text Completion APIs support far greater customization options than OpenAI's standards allow for. These greater customization options, such as the Min-P sampler, may be worthwhile for SillyTavern users to check out, which can greatly improve the quality of generations.
https://docs.sillytavern.app/usage/api-connections/openai/
So it seems they discourage this