Simon Willison's Weblog
bettiemccurdy editou esta página há 2 meses atrás


That design was trained in part utilizing their unreleased R1 "thinking" design. Today they have actually released R1 itself, along with an entire family of brand-new designs obtained from that base.

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

DeepSeek-R1-Zero seems the base design. It's over 650GB in size and, like the majority of their other releases, is under a tidy MIT license. DeepSeek warn that "DeepSeek-R1-Zero experiences challenges such as unlimited repetition, poor readability, and language mixing." ... so they also launched:

DeepSeek-R1-which "includes cold-start data before RL" and "attains performance comparable to OpenAI-o1 across mathematics, code, and reasoning tasks". That a person is also MIT certified, and is a comparable size.

I do not have the capability to run models bigger than about 50GB (I have an M2 with 64GB of RAM), so neither of these 2 designs are something I can easily play with myself. That's where the brand-new distilled designs 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 on Llama and Qwen.

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

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

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

aside, these distilled designs are interesting monsters.

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

Quantized variations are currently beginning to reveal up. Up until now I've attempted just among those- unsloth/DeepSeek-R 1-Distill-Llama-8B-GGUF released by Unsloth AI-and it's actually enjoyable to play with.

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

First I fetched and ran the model utilizing Ollama itself:

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

Once the model has been brought, LLM can speak to it too. I choose utilizing LLM for experiments due to the fact that it logs everything to SQLite for later expedition.

I set up the plugin and ran it like this:

Each action starts with a ... pseudo-XML tag containing the chain of thought used to help create the response. 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 interesting combination. Let me think about how these 2 characters might engage in a humorous situation.

First, let's consider their qualities. Pelicans are understood for their long beaks and Webbed feet, typically seen near the beach or water. Walruses have big teeth, thick fur, and they're generally discovered in chillier environments, like icebergs or snowy locations. So, integrating these two into a tea space setting is currently a funny 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 space together. The walrus, with its big size, has a hard time to discover comfy chairs, so it sits on the table by accident, overturning the teapot. Meanwhile, the pelican, attempting to assist, uses its beak to put saucers on the table, triggering a couple of spills.

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

Explanation:

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

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

    So yeah, wiki.vst.hs-furtwangen.de the joke is awful. But the procedure of getting there was such an intriguing insight into how these new models work.

    This was a fairly little 8B design. I'm eagerly anticipating trying the Llama 70B variation, which isn't yet available in a GGUF I can keep up Ollama. Given the strength of Llama 3.3 70B-currently my favourite GPT-4 class design that I have actually 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 attempted my classic 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 aspects wrong, so I followed up with:

    the background ended up covering the remainder of the image

    It thought some more and provided me this:

    As with the earlier joke, the chain of thought in the transcript was much more intriguing than the end outcome.

    Other methods to try DeepSeek-R1

    If you want to attempt the design out without setting up anything at all you can do so utilizing chat.deepseek.com-you'll need to develop an account (indication in with Google, utilize an email address or supply a Chinese +86 contact number) and after that pick the "DeepThink" alternative below the timely input box.

    DeepSeek provide the model by means of their API, using an OpenAI-imitating endpoint. You can access that by means of LLM by dropping this into your extra-openai-models. yaml configuration file:

    Then run llm secrets set deepseek and paste in your API key, then utilize llm -m deepseek-reasoner 'prompt' to run prompts.

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