Hugging Face's logo

LoneStriker
/
bagel-8x7b-v0.2-4.0bpw-h6-exl2

Text Generation
Transformers
Safetensors
mixtral
conversational
text-generation-inference
Inference Endpoints
Model card Files Community
bagel-8x7b-v0.2-4.0bpw-h6-exl2 / README.md
LoneStriker's picture
LoneStriker
Upload folder using huggingface_hub
e760cf9
preview code
|
raw
history blame contribute delete
17.6 kB
metadata
license: apache-2.0
datasets:
  - ai2_arc
  - jondurbin/airoboros-3.2
  - codeparrot/apps
  - facebook/belebele
  - boolq
  - jondurbin/cinematika-v0.1
  - drop
  - lmsys/lmsys-chat-1m
  - TIGER-Lab/MathInstruct
  - cais/mmlu
  - Muennighoff/natural-instructions
  - openbookqa
  - piqa
  - Vezora/Tested-22k-Python-Alpaca
  - cakiki/rosetta-code
  - Open-Orca/SlimOrca
  - spider
  - squad_v2
  - migtissera/Synthia-v1.3
  - datasets/winogrande
  - nvidia/HelpSteer
  - Intel/orca_dpo_pairs
  - unalignment/toxic-dpo-v0.1
  - jondurbin/truthy-dpo-v0.1
  - allenai/ultrafeedback_binarized_cleaned
  - Squish42/bluemoon-fandom-1-1-rp-cleaned
  - LDJnr/Capybara
  - JULIELab/EmoBank
  - kingbri/PIPPA-shareGPT

A bagel, with everything (except DPO)

bagel

Overview

An experimental fine-tune of mixtral-8x7b-v0.1 using bagel

This is the model after the SFT phase, before DPO has been applied.

Hardware kindly provided by Massed Compute

Data sources

Yes, you will see benchmark names in the list, but this only uses the train splits, and a decontamination by cosine similarity is performed at the end as a sanity check

  • ai2_arc
    • Abstraction and reasoning dataset, useful in measuring "intelligence" to a certain extent.
  • airoboros
    • Variety of categories of synthetic instructions generated by gpt-4.
  • apps
    • Python coding dataset with 10k problems.
  • belebele
    • Multi-lingual reading comprehension dataset.
  • bluemoon
    • Roleplay data scraped from Bluemoon, then cleaned and formatted as ShareGPT.
  • boolq
    • Corpus of yes/no questions (which can be surprisingly difficult for AI to answer apparently?)
  • capybara
    • Multi-turn dataset used to create the capybara models.
  • cinematika (instruction and plain text)
    • RP-style data synthesized from movie scripts so the model isn't quite as boring as it otherwise would be.
  • drop
    • More reading comprehension.
  • emobank
    • Emotion annotations using the Valence-Arousal-Domninance scheme.
  • gutenberg (plain text)
    • Books/plain text, again to make the model less boring, only a handful of examples supported by chapterize
  • lmsys_chat_1m (only gpt-4 items, also used for DPO)
    • Chats collected by the lmsys chat arena, containing a wide variety of chats with various models.
  • mathinstruct
    • Composite dataset with a variety of math-related tasks and problem/question formats.
  • mmlu
    • Massive Multitask Language Understanding - a wide variety of questions about various subject matters.
  • natural_instructions
    • Millions of instructions from 1600+ task categories (sampled down substantially, stratified by task type)
  • openbookqa
    • Question answering dataset.
  • pippa
    • Deduped version of PIPPA in ShareGPT format.
  • piqa
    • Phyiscal interaction question answering.
  • python_alpaca
    • Python instruction response pairs, validated as functional.
  • rosetta_code
    • Code problems and solutions in a variety of programming languages taken from rosettacode.org.
  • slimorca
    • Collection of ~500k gpt-4 verified chats from OpenOrca.
  • spider
    • SQL-targeted dataset.
  • squad_v2
    • Contextual question answering (RAG).
  • synthia
    • GPT-4 generated data using advanced prompting from Migel Tissera.
  • winogrande
    • Fill in the blank style prompts.

Only the train splits were used (if a split was provided), and an additional pass of decontamination is performed using approximate nearest neighbor search (via faiss).

Prompt formatting

In sticking with the theme of the bagel, I didn't want to use a single prompt format, so I used 4 - vicuna, llama-2, alpaca, and chat-ml (sorta). I also didn't want to randomly select a single prompt format for each item (hoping each instruction would generalize more when used in a variety of prompt formats), so each instruction is actually converted into every prompt format.

This means each epoch of our fine-tune is really basically 4 epochs. So, for the fine-tunes, I would recommend only doing 1 epoch (or 0.75 epochs). I am testing with a single epoch using a relatively low learning rate.

Alpaca (sort of) 

Below is an instruction that describes a task.  Write a response that appropriately completes the request.

### Instruction:
{system prompt, if provided}
{instruction}

### Response:

The main difference here is that because of the dataset formatting and variety of data sources, it would have been much to tedious to add an ### Input: block, so the inputs are just in the instruction section.

Vicuna 

{system prompt, if provided, randomly defaulting to "A chat between a user and an unbiased, uncensored assistant."}
USER: {instruction}
ASSISTANT:

ChatML (sort of)

I don't really understand the point of having special tokens for <|im_start|> and <|im_end|>, because in practice they just act as BOS and EOS tokens (but, please correct me if I'm wrong).

So, instead of:

{bos}<|im_start|>{role}
{text}
<|im_end|>{eos}

I just changed it to:

{bos}{role}
{text}
{eos}

If you really want to use <|im_start|> and <|im_end|>, just update your tokenizer_config.json to use <|im_start|> instead of <s> and <|im_end|> instead of </s> and when tokenizing. And if you still don't like what I've done to this chat-ml-ish format, feel free to cry into your pillow or fork the code and do a new fine-tune.

Llama-2 chat 

[INST] <<SYS>>
{system}
<</SYS>>

{instruction} [/INST]

Default via chat template

The model's tokenizer_config.json includes the default chat template (llama-2), so you can simply use the apply_chat_template method to build the full prompt.

import transformers
tokenizer = transformers.AutoTokenizer.from_pretrained('jondurbin/bagel-8x7b-v0.2')
chat = [
  {"role": "system", "content": "You are Bob, a friendly AI assistant."},
  {"role": "user", "content": "Hello, how are you?"},
  {"role": "assistant", "content": "I'm doing great. How can I help you today?"},
  {"role": "user", "content": "I'd like to show off how chat templating works!"},
]
print(tokenizer.apply_chat_template(chat, tokenize=False))

Contribute

If you're interested in new functionality/datasets, take a look at bagel repo and either make a PR or open an issue with details.

To help me with the fine-tuning costs (which are extremely expensive for these large combined datasets):

Guide for certain tasks

RA(G)/contextual question answering

The model was trained to ignore what it thinks it knows, and uses the context to answer the questions, when using the format below. The model was also tuned to limit the values to the provided context as much as possible to reduce hallucinations.

The format for a contextual prompt is as follows:

BEGININPUT
BEGINCONTEXT
[key0: value0]
[key1: value1]
... other metdata ...
ENDCONTEXT
[insert your text blocks here]
ENDINPUT
[add as many other blocks, in the exact same format]
BEGININSTRUCTION
[insert your instruction(s).  The model was tuned with single questions, paragraph format, lists, etc.]
ENDINSTRUCTION

I know it's a bit verbose and annoying, but after much trial and error, using these explicit delimiters helps the model understand where to find the responses and how to associate specific sources with it.

  • BEGININPUT - denotes a new input block
  • BEGINCONTEXT - denotes the block of context (metadata key/value pairs) to associate with the current input block
  • ENDCONTEXT - denotes the end of the metadata block for the current input
  • [text] - Insert whatever text you want for the input block, as many paragraphs as can fit in the context.
  • ENDINPUT - denotes the end of the current input block
  • [repeat as many input blocks in this format as you want]
  • BEGININSTRUCTION - denotes the start of the list (or one) instruction(s) to respond to for all of the input blocks above.
  • [instruction(s)]
  • ENDINSTRUCTION - denotes the end of instruction set

Use a very low temperature!

Here's a trivial, but important example to prove the point:

BEGININPUT
BEGINCONTEXT
date: 2021-01-01
url: https://web.site/123
ENDCONTEXT
In a shocking turn of events, blueberries are now green, but will be sticking with the same name.
ENDINPUT
BEGININSTRUCTION
What color are bluberries?  Source?
ENDINSTRUCTION

And the response:

Blueberries are now green.
Source:
date: 2021-01-01
url: https://web.site/123

Summarization

500 samples have been included from this dataset, using the same format as contextual question answering, for example:

BEGININPUT
{text to summarize}
ENDINPUT
BEGININSTRUCTION
Summarize the input in around 130 words.
ENDINSTRUCTION

Agent/function calling

The dataset includes many examples of function/args generation based on input criteria. This is somewhat similar to the OpenAI function calling, but the output is either JSON or YAML.

Example prompt:

As an AI assistant, please select the most suitable function and parameters from the list of available functions below, based on the user's input. Provide your response in JSON format.

Input: I want to know how many times 'Python' is mentioned in my text file.

Available functions:
file_analytics:
  description: This tool performs various operations on a text file.
  params:
    action: The operation we want to perform on the data, such as "count_occurrences", "find_line", etc.
    filters:
      keyword: The word or phrase we want to search for.

Response:

{
  "function": "file_analytics",
  "params": {
    "action": "count_occurrences",
    "filters": {
      "keyword": "Python"
    }
  }
}

reWOO style execution planning

The model now supports execution planning for complex instructions that would require making use of several tools. The output is just the plan, you must implement a mechanism to parse the output and actually call the functions!

Example prompt:

Please construct a systematic plan to generate an optimal response to the user instruction, utilizing a set of provided tools. Each plan will correspond to an evidence value, which will be the output of one of the available functions given an input string
that could be the user's question, one or more prior evidence values, or a combination of both.

Here are the tools available to be called:
DuckDuckGo[input]: Tool that enables the user to search for information using the DuckDuckGo search engine. This tool is helpful in locating a suitable list of sites that may contain the answer to the user's query. It does not directly answer the question but finds a list of sites that might have the answer.
TextScraper[input]: Load one or more websites from the input string containing newline delimited links, where input is one or more links, and produces plain text output containing the content of the links.
HyperlinkExtractor[input]: Extract links from plain text and produces a plain text, newline delimited response of links.
KnowledgeModel[input]: Question answering language model, particularly useful in answering questions based on an input passage of text. The input must be a text question that references an :evidence[n]: variable, e.g. What color is the cat, given :evidence1:?

The output should be in format:
Plan: [first action to take based on input question]
:evidence0: = [function to call with input parameter]
Plan: [next action to take, based on result of :evidence0:]
:evidence1: = [next function to call and input parameter, which may include reference to previous evidence, e.g. "Given context :evidence0"]
...
Answer: [:evidence[n]: containing the final answer.]

Question: Who won the Nobel Prize in Literature in 2020 and what is their most famous work?

Response:

Plan: Begin by conducting a web search to find out who won the Nobel Prize in Literature in 2020.
:evidence0: = DuckDuckGo[Nobel Prize in Literature 2020 winner]
Plan: Utilize the KnowledgeModel to interpret the search results and find the name of the laureate.
:evidence1: = KnowledgeModel[Who won the Nobel Prize in Literature in 2020, given :evidence0:?]
Plan: Conduct another web search to find the most famous work of the identified laureate.
:evidence2: = DuckDuckGo[Most famous work of :evidence1:]
Plan: Extract the relevant links from the DuckDuckGo search results for a more focused search.
:evidence3: = HyperlinkExtractor[:evidence2:]
Plan: Use the TextScraper tool to extract information from the relevant links.
:evidence4: = TextScraper[:evidence3:]
Plan: Finally, utilize the KnowledgeModel to identify and summarize the most famous work of the laureate from the extracted information.
:evidence5: = KnowledgeModel[What is the most famous work of :evidence1:, given :evidence4:?]
Answer: :evidence5:

For this to be useful, you'd have to parse the output plan text, and implement/call each of the functions. This is just pseudo-code, completely untested off the top of my head, and obviously would requiring full implementation + hardening:

import re
import requests

def inject_context(input_text, **context):
    for ref in set(re.findall(r"(:evidence[0-9]+:)", input_text, re.I)):
        input_text = input_text.replace(ref, context.get(ref, ""))
    return input_text

def duckduckgo(input_text, **context):
    search_string = inject_context(input_text, **context)
    ... search via duck duck go using search_string
    ... return text content

def link_extractor(input_text, **context):
    input_text = inject_context(input_text, **context)
    return "\n".join(list(set(re.findall(r"(https?://[^\s]+?\.?)", input_text, re.I))))

def scrape(input_text, **context):
  input_text = inject_context(input_text, **context)
  text = []
  for link in input_text.splitlines():
    text.append(requests.get(link).text)
  return "\n".join(text)

def infer(input_text, **context)
  prompt = inject_context(input_text, **context)
  ... call model with prompt, return output

def parse_plan(plan):
    method_map = {
      "DuckDuckGo": duckduckgo,
      "HyperlinkExtractor": link_extractor,
      "KnowledgeModel": infer,
      "TextScraper": scrape,
    }
    context = {}
    for line in plan.strip().splitlines():
        if line.startswith("Plan:"):
            print(line)
            continue
        parts = re.match("^(:evidence[0-9]+:)\s*=\s*([^\[]+])(\[.*\])\s$", line, re.I)
        if not parts:
          if line.startswith("Answer: "):
            return context.get(line.split(" ")[-1].strip(), "Answer couldn't be generated...")
          raise RuntimeError("bad format: " + line)
        context[parts.group(1)] = method_map[parts.group(2)](parts.group(3), **context)

Fine-tuning information

You can find charts, and the full configuration used to fine-tune this model on weights and biases

The model was fine-tuned on an 8x a6000 instance, for 4 days, 15 hours, 6 minutes and 42 seconds.

Licence and usage restrictions

The base model is mixtral-8x7b-v0.1, which is licensed as apache-2.0 - no issues there.

The fine-tuning data, however, includes several datasets that have data generated at least in part by OpenAI's gpt-4.

I am not a lawyer, so I can't help determine if this is actually commercially viable, but some questions that often come up are:

  • Does the OpenAI ToS apply only to the user who created the dataset initially, and not subsequent models?
  • If the dataset was released under a permissive license, but actually includes OpenAI generated data, does that ToS supersede the license?
  • Does the dataset fall completely under fair use anyways, since the model isn't really capable of reproducing the entire training set verbatim?

Use your best judgement and seek legal advice if you are concerned about the terms. In any case, by using this model, you agree to completely indemnify me.