Simon Willison's Weblog
luthermetz5409 edited this page 4 months ago


That model was trained in part using their unreleased R1 "reasoning" model. Today they've launched R1 itself, together with an entire household of brand-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 the majority of their other releases, is under a tidy MIT license. DeepSeek caution that "DeepSeek-R1-Zero encounters obstacles such as unlimited repeating, bad readability, and language blending." ... so they likewise released:

DeepSeek-R1-which "incorporates cold-start data before RL" and "attains performance equivalent to OpenAI-o1 across math, code, and thinking jobs". That a person is also MIT licensed, and is a similar size.

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

To support the research study neighborhood, we have open-sourced DeepSeek-R1-Zero, DeepSeek-R1, and six thick models distilled from DeepSeek-R1 based on Llama and buysellammo.com Qwen.

This is an interesting flex! They have actually designs based on Qwen 2.5 (14B, 32B, Math 1.5 B and Math 7B) and annunciogratis.net Llama 3 (Llama-3.1 8B and Llama 3.3 70B Instruct).

Weirdly those Llama designs have an MIT license attached, which I'm uncertain is suitable with the underlying Llama license. Qwen designs are Apache licensed so perhaps MIT is OK?

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

Licensing aside, these distilled designs are fascinating monsters.

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

Quantized versions are currently beginning 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 really enjoyable to have fun with.

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

First I fetched and ran the design using Ollama itself:

This downloads around 8.5 GB of model information and begins an interactive chat interface.

Once the design has been fetched, LLM can speak to it too. I prefer utilizing LLM for experiments because it logs whatever to SQLite for later expedition.

I set up the plugin and raovatonline.org ran it like this:

Each action begins with a ... pseudo-XML tag containing the chain of thought used to assist create the response. For "a joke about a pelican and a walrus who run a tea room together" that started like this:

Okay, so I need to come up with a joke about a pelican and a walrus running a tea space together. Hmm, oke.zone that's an intriguing mix. Let me think about how these 2 characters might communicate in a funny scenario.

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 typically discovered in chillier environments, like icebergs or snowy areas. So, integrating these 2 into a tea room setting is currently a funny image.

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

The Joke:

A pelican and a walrus choose to open a quaint little tea space together. The walrus, with its huge size, has a hard time to find comfortable chairs, so it rests on the table by mishap, overturning the teapot. Meanwhile, the pelican, attempting to help, utilizes its beak to place dishes on the table, triggering a few spills.

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

Explanation:

- Setup: Pelican and Walrus run an unlikely tea room. Their sizes cause comical mayhem.

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

    So yeah, the joke is awful. But the process of getting there was such a fascinating insight into how these brand-new designs work.

    This was a fairly little 8B design. I'm eagerly anticipating experimenting with the Llama 70B variation, which isn't yet available in a GGUF I can run with Ollama. Given the strength of Llama 3.3 70B-currently my favourite GPT-4 class model that I have actually run on my own machine-I have high expectations.

    Update 21st January 2025: asteroidsathome.net 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 attempted my traditional Generate an SVG of a pelican riding a bike timely too. It did refrain from doing extremely well:

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

    the background ended up covering the remainder of the image

    It thought some more and offered me this:

    As with the earlier joke, the chain of believed in the transcript was far more interesting than completion result.

    Other ways to try DeepSeek-R1

    If you wish to try the model out without installing anything you can do so using chat.deepseek.com-you'll need to produce an account (indication in with Google, utilize an email address or supply a Chinese +86 contact number) and after that select the "DeepThink" option below the timely input box.

    DeepSeek provide the model via 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 keys set deepseek and paste in your API key, then utilize llm -m deepseek-reasoner 'prompt' to run prompts.

    This won't reveal you the thinking tokens, regretfully. Those are dished out by the API (example here) but LLM does not yet have a way to display them.