1 Simon Willison's Weblog
Ada Koehler edited this page 2025-02-11 14:46:00 +08:00


That model was trained in part using their unreleased R1 "reasoning" design. Today they have actually launched R1 itself, wiki.eqoarevival.com in addition to a whole household of new models obtained from that base.

There's a lot of things in the brand-new release.

DeepSeek-R1-Zero seems the base model. It's over 650GB in size and, like most of their other releases, is under a tidy MIT license. DeepSeek caution that "DeepSeek-R1-Zero experiences obstacles such as endless repetition, poor readability, and language blending." ... so they likewise released:

DeepSeek-R1-which "includes cold-start data before RL" and "attains efficiency comparable to OpenAI-o1 throughout mathematics, code, and thinking tasks". That a person is likewise MIT certified, and is a similar size.

I don't have the capability to run models bigger than about 50GB (I have an M2 with 64GB of RAM), so neither of these two designs are something I can easily have fun with myself. That's where the brand-new distilled models are available in.

To support the research study community, we have open-sourced DeepSeek-R1-Zero, DeepSeek-R1, and 6 dense designs distilled from DeepSeek-R1 based upon Llama and Qwen.

This is a fascinating flex! They have actually models based upon Qwen 2.5 (14B, 32B, gratisafhalen.be Math 1.5 B and Math 7B) and Llama 3 (Llama-3.1 8B and Llama 3.3 70B Instruct).

Weirdly those Llama models have an MIT license connected, which I'm uncertain works with the underlying Llama license. Qwen models are Apache accredited so perhaps MIT is OK?

(I also just noticed the MIT license files state "Copyright (c) 2023 DeepSeek" so they may need to pay a little bit more attention to how they copied those in.)

Licensing aside, these distilled designs are fascinating monsters.

Running DeepSeek-R1-Distill-Llama-8B-GGUF

are already starting to appear. Up until now I've attempted just among those- unsloth/DeepSeek-R 1-Distill-Llama-8B-GGUF launched by Unsloth AI-and it's actually enjoyable to have fun with.

I'm running it using the combination of Ollama, LLM and the llm-ollama plugin.

First I brought and ran the design using Ollama itself:

This downloads around 8.5 GB of model data and starts an interactive chat user interface.

Once the design has been fetched, LLM can talk with it also. I prefer using LLM for experiments due to the fact that it logs everything to SQLite for later expedition.

I installed the plugin and ran it like this:

Each reaction begins with a ... pseudo-XML tag containing the chain of thought used to help generate the reaction. For "a joke about a pelican and a walrus who run a tea room together" that began like this:

Okay, so I require to come up with a joke about a pelican and a walrus running a tea room together. Hmm, that's an intriguing mix. Let me think of how these two characters might communicate in a funny circumstance.

First, let's consider their characteristics. Pelicans are known for their long beaks and Webbed feet, frequently seen near the beach or water. Walruses have big teeth, thick fur, and they're usually discovered in chillier environments, like icebergs or snowy areas. So, combining these two into a tea room setting is already an amusing image.

[...]
It then believed for 20 paragraphs before outputting the joke! Here's the complete transcript and here's the output at the end, after the tag:

The Joke:

A pelican and a walrus decide to open a quaint little tea room together. The walrus, with its big size, struggles to find comfy chairs, so it sits on the table by mishap, knocking over the teapot. Meanwhile, the pelican, attempting to help, utilizes its beak to position dishes on the table, triggering a couple of spills.

After a series of funny mishaps, the walrus looks up and says with a grin, "This isn't so fishy anymore." The pelican smirks and says, "Maybe not, however we do have a lot of krill in our tea!"

Explanation:

- Setup: Pelican and Walrus run a not likely tea space. Their sizes cause comical mayhem.

  • Punchline: "This isn't so fishy any longer" is a pun on the situation becoming less unreasonable. The follow-up joke presents "krill," a play on words that connects into both marine life ("fish") and tea, making it amusing while fitting the theme.

    So yeah, the joke is terrible. But the procedure of getting there was such an intriguing insight into how these new designs work.

    This was a fairly small 8B design. I'm looking forward to experimenting with the Llama 70B version, which isn't yet available in a GGUF I can keep up Ollama. Given the strength of Llama 3.3 70B-currently my preferred GPT-4 class design that I've run on my own machine-I have high expectations.

    Update 21st January 2025: I got this quantized version of that Llama 3.3 70B R1 distilled model working like this-a 34GB download:

    Can it draw a pelican?

    I tried my classic Generate an SVG of a pelican riding a bicycle timely too. It did refrain from doing really well:

    It aimed to me like it got the order of the aspects incorrect, so I followed up with:

    the background wound up covering the remainder of the image

    It thought some more and provided me this:

    Similar to the earlier joke, the chain of thought in the transcript was far more intriguing than the end outcome.

    Other ways to try DeepSeek-R1

    If you wish to attempt the design out without installing anything you can do so utilizing chat.deepseek.com-you'll require to develop an account (check in with Google, use an email address or offer a Chinese +86 phone number) and library.kemu.ac.ke then select the "DeepThink" option listed below the timely input box.

    DeepSeek use the design by means of their API, utilizing an OpenAI-imitating endpoint. You can access that by means of LLM by dropping this into your extra-openai-models. yaml setup file:

    Then run llm secrets set deepseek and paste in your API secret, then utilize llm -m deepseek-reasoner 'timely' to run triggers.

    This will not reveal you the thinking tokens, unfortunately. Those are served up by the API (example here) but LLM does not yet have a method to display them.