Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • F ffho
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 1
    • Issues 1
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Infrastructure Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Katherina Flournoy
  • ffho
  • Issues
  • #1

Closed
Open
Created Feb 07, 2025 by Katherina Flournoy@katherinaflourMaintainer

Understanding DeepSeek R1


We've been tracking the explosive rise of DeepSeek R1, which has actually taken the AI world by storm in current weeks. In this session, we dove deep into the development of the DeepSeek household - from the early designs through DeepSeek V3 to the advancement R1. We also checked out the technical innovations that make R1 so unique in the world of open-source AI.

The DeepSeek Family Tree: From V3 to R1

DeepSeek isn't simply a single model; it's a household of increasingly advanced AI systems. The advancement goes something like this:

DeepSeek V2:

This was the structure model which leveraged a mixture-of-experts architecture, wiki.myamens.com where only a subset of experts are used at reasoning, drastically improving the processing time for each token. It also included multi-head latent attention to minimize memory footprint.

DeepSeek V3:

This design introduced FP8 training strategies, which assisted drive down training costs by over 42.5% compared to previous models. FP8 is a less precise way to keep weights inside the LLMs but can significantly enhance the memory footprint. However, training utilizing FP8 can generally be unstable, and it is hard to obtain the desired training outcomes. Nevertheless, DeepSeek utilizes numerous tricks and attains extremely stable FP8 training. V3 set the phase as a highly effective design that was currently cost-efficient (with claims of being 90% cheaper than some closed-source alternatives).

DeepSeek R1-Zero:

With V3 as the base, the team then introduced R1-Zero, the very first reasoning-focused version. Here, the focus was on teaching the model not simply to produce responses but to "think" before answering. Using pure support learning, the design was motivated to generate intermediate thinking steps, for instance, taking extra time (typically 17+ seconds) to work through a simple issue like "1 +1."

The key innovation here was the use of group relative policy optimization (GROP). Instead of counting on a traditional procedure reward design (which would have required annotating every step of the reasoning), GROP compares numerous outputs from the design. By sampling a number of potential responses and scoring them (using rule-based measures like specific match for math or confirming code outputs), the system learns to prefer thinking that results in the proper result without the requirement for explicit guidance of every intermediate idea.

DeepSeek R1:

Recognizing that R1-Zero's without supervision method produced thinking outputs that might be hard to read and even mix languages, the developers went back to the drawing board. They used the raw outputs from R1-Zero to create "cold start" data and then manually curated these examples to filter and enhance the quality of the thinking. This human post-processing was then utilized to fine-tune the original DeepSeek V3 design further-combining both reasoning-oriented reinforcement knowing and monitored fine-tuning. The result is DeepSeek R1: a design that now produces readable, meaningful, and trusted thinking while still maintaining the performance and cost-effectiveness of its predecessors.

What Makes R1 Series Special?

The most interesting element of R1 (no) is how it developed thinking abilities without specific guidance of the thinking process. It can be further enhanced by utilizing cold-start data and monitored support learning to produce legible thinking on basic tasks. Here's what sets it apart:

Open Source & Efficiency:

R1 is open source, enabling researchers and designers to inspect and build on its developments. Its cost performance is a major selling point especially when compared to closed-source designs (claimed 90% cheaper than OpenAI) that need huge calculate spending plans.

Novel Training Approach:

Instead of relying exclusively on annotated reasoning (which is both pricey and time-consuming), the design was trained using an outcome-based technique. It started with easily proven tasks, such as math issues and coding workouts, where the correctness of the final response could be easily measured.

By using group relative policy optimization, the training procedure compares numerous generated answers to identify which ones fulfill the preferred output. This relative scoring system allows the model to find out "how to believe" even when intermediate reasoning is generated in a freestyle manner.

Overthinking?

An interesting observation is that DeepSeek R1 sometimes "overthinks" basic issues. For instance, when asked "What is 1 +1?" it may invest almost 17 seconds assessing various scenarios-even considering binary representations-before concluding with the correct response. This self-questioning and verification process, although it may seem inefficient at very first glimpse, might show beneficial in intricate tasks where much deeper reasoning is essential.

Prompt Engineering:

Traditional few-shot prompting methods, which have actually worked well for many chat-based models, can really deteriorate efficiency with R1. The developers recommend utilizing direct problem declarations with a zero-shot method that specifies the output format plainly. This guarantees that the design isn't led astray by extraneous examples or tips that might hinder its internal thinking procedure.

Getting Started with R1

For those aiming to experiment:

Smaller variants (7B-8B) can run on customer GPUs or even only CPUs


Larger variations (600B) need significant calculate resources


Available through major cloud service providers


Can be released in your area via Ollama or vLLM


Looking Ahead

We're especially fascinated by numerous implications:

The capacity for this method to be applied to other reasoning domains


Impact on agent-based AI systems typically developed on chat designs


Possibilities for integrating with other guidance strategies


Implications for business AI release


Thanks for pediascape.science checking out Deep Random Thoughts! Subscribe totally free to receive new posts and support my work.

Open Questions

How will this impact the advancement of future reasoning designs?


Can this approach be extended to less verifiable domains?


What are the implications for multi-modal AI systems?


We'll be seeing these advancements closely, especially as the neighborhood starts to experiment with and build on these strategies.

Resources

Join our Slack community for continuous conversations and updates about DeepSeek and other AI developments. We're seeing fascinating applications already emerging from our bootcamp individuals dealing with these designs.

Chat with DeepSeek:


https://www.deepseek.com/

Papers:

DeepSeek LLM


DeepSeek-V2


DeepSeek-V3


DeepSeek-R1


Blog Posts:

The Illustrated DeepSeek-R1


DeepSeek-R1 Paper Explained


DeepSeek R1 - a brief summary


Cloud Providers:

Nvidia


Together.ai


AWS




Q&A

Q1: Which model is worthy of more attention - DeepSeek or Qwen2.5 Max?

A: While Qwen2.5 is likewise a strong design in the open-source community, the option eventually depends upon your use case. DeepSeek R1 highlights sophisticated reasoning and a novel training approach that might be particularly valuable in tasks where proven reasoning is critical.

Q2: Why did significant providers like OpenAI go with supervised fine-tuning instead of reinforcement knowing (RL) like DeepSeek?

A: We ought to keep in mind in advance that they do use RL at the minimum in the kind of RLHF. It is most likely that designs from significant companies that have thinking capabilities already utilize something similar to what DeepSeek has actually done here, however we can't make certain. It is also likely that due to access to more resources, they preferred monitored fine-tuning due to its stability and the prepared availability of big annotated datasets. Reinforcement knowing, although powerful, can be less foreseeable and harder to manage. DeepSeek's approach innovates by applying RL in a reasoning-oriented way, making it possible for the model to learn efficient internal reasoning with only very little process annotation - a strategy that has proven promising regardless of its intricacy.

Q3: Did DeepSeek use test-time compute techniques comparable to those of OpenAI?

A: DeepSeek R1's style highlights performance by leveraging techniques such as the mixture-of-experts technique, which activates only a subset of specifications, to lower compute throughout inference. This concentrate on efficiency is main to its expense advantages.

Q4: What is the difference between R1-Zero and R1?

A: R1-Zero is the preliminary model that finds out thinking entirely through support knowing without specific process supervision. It creates intermediate reasoning actions that, while in some cases raw or mixed in language, work as the foundation for knowing. DeepSeek R1, on the other hand, fine-tunes these outputs through human post-processing and monitored fine-tuning. In essence, R1-Zero offers the unsupervised "trigger," and R1 is the polished, more meaningful version.

Q5: How can one remain upgraded with in-depth, technical research study while handling a hectic schedule?

A: Remaining existing involves a combination of actively engaging with the research community (like AISC - see link to sign up with slack above), following preprint servers like arXiv, going to pertinent conferences and webinars, and taking part in discussion groups and newsletters. Continuous engagement with online communities and collaborative research study jobs likewise plays a key role in keeping up with technical advancements.

Q6: In what use-cases does DeepSeek outshine designs like O1?

A: The short response is that it's too early to tell. DeepSeek R1's strength, nevertheless, lies in its robust reasoning abilities and its effectiveness. It is particularly well matched for tasks that need proven logic-such as mathematical problem resolving, code generation, and structured decision-making-where intermediate reasoning can be examined and verified. Its open-source nature further enables tailored applications in research and enterprise settings.

Q7: What are the implications of DeepSeek R1 for business and start-ups?

A: The open-source and cost-efficient style of DeepSeek R1 decreases the entry barrier for releasing innovative language designs. Enterprises and start-ups can utilize its innovative reasoning for agentic applications varying from automated code generation and consumer assistance to information analysis. Its flexible release options-on consumer hardware for smaller sized designs or cloud platforms for larger ones-make it an attractive option to proprietary solutions.

Q8: Will the model get stuck in a loop of "overthinking" if no appropriate answer is discovered?

A: While DeepSeek R1 has been observed to "overthink" easy issues by checking out numerous thinking paths, it includes stopping requirements and examination systems to prevent infinite loops. The reinforcement finding out structure motivates merging towards a proven output, even in uncertain cases.

Q9: Is DeepSeek V3 completely open source, and is it based upon the Qwen architecture?

A: Yes, DeepSeek V3 is open source and worked as the structure for later versions. It is built on its own set of innovations-including the mixture-of-experts approach and FP8 training-and is not based on the Qwen architecture. Its design highlights efficiency and expense reduction, setting the phase for the reasoning innovations seen in R1.

Q10: How does DeepSeek R1 carry out on vision jobs?

A: DeepSeek R1 is a text-based design and does not include vision capabilities. Its design and training focus entirely on language processing and thinking.

Q11: Can professionals in specialized fields (for instance, laboratories dealing with cures) use these techniques to train domain-specific designs?

A: Yes. The innovations behind DeepSeek R1-such as its outcome-based thinking training and efficient architecture-can be adjusted to numerous domains. Researchers in fields like biomedical sciences can tailor these methods to develop models that resolve their particular challenges while gaining from lower calculate costs and robust reasoning abilities. It is most likely that in deeply specialized fields, nevertheless, there will still be a need for supervised fine-tuning to get reputable outcomes.

Q12: Were the annotators for the human post-processing experts in technical fields like computer science or mathematics?

A: The discussion showed that the annotators mainly concentrated on domains where correctness is quickly verifiable-such as mathematics and coding. This recommends that competence in technical fields was certainly leveraged to make sure the accuracy and clarity of the thinking data.

Q13: Could the design get things incorrect if it relies on its own outputs for learning?

A: disgaeawiki.info While the design is developed to enhance for appropriate answers via knowing, there is always a danger of errors-especially in uncertain scenarios. However, by assessing numerous prospect outputs and enhancing those that cause proven outcomes, the training process decreases the likelihood of propagating incorrect reasoning.

Q14: How are hallucinations decreased in the design offered its iterative reasoning loops?

A: Making use of rule-based, verifiable tasks (such as math and coding) helps anchor the design's reasoning. By comparing several outputs and utilizing group relative policy optimization to reinforce just those that yield the correct result, the design is directed far from producing unproven or hallucinated details.

Q15: Does the model depend on complex vector mathematics?

A: Yes, advanced techniques-including complex vector math-are important to the application of mixture-of-experts and attention mechanisms in DeepSeek R1. However, the main focus is on utilizing these techniques to enable reliable reasoning rather than showcasing mathematical complexity for its own sake.

Q16: Some stress that the model's "thinking" might not be as improved as human reasoning. Is that a legitimate issue?

A: Early iterations like R1-Zero did produce raw and in some cases hard-to-read reasoning. However, the subsequent refinement process-where human experts curated and enhanced the reasoning data-has considerably enhanced the clarity and reliability of DeepSeek R1's internal idea process. While it remains a developing system, iterative training and feedback have resulted in meaningful enhancements.

Q17: Which model variants are appropriate for local release on a laptop with 32GB of RAM?

A: For regional screening, a medium-sized model-typically in the variety of 7B to 8B parameters-is advised. Larger models (for example, those with numerous billions of specifications) require significantly more computational resources and are better suited for cloud-based implementation.

Q18: Is DeepSeek R1 "open source" or does it provide just open weights?

A: DeepSeek R1 is offered with open weights, suggesting that its model specifications are publicly available. This aligns with the total open-source philosophy, permitting scientists and developers to further explore and construct upon its developments.

Q19: What would occur if the order of training were reversed-starting with monitored fine-tuning before unsupervised reinforcement learning?

A: The present technique permits the design to first explore and produce its own reasoning patterns through not being watched RL, and after that refine these patterns with monitored approaches. Reversing the order may constrain the model's ability to discover diverse thinking paths, possibly limiting its general efficiency in tasks that gain from autonomous thought.

Thanks for reading Deep Random Thoughts! Subscribe totally free to get brand-new posts and support my work.

Assignee
Assign to
Time tracking