Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • B bwbot
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 30
    • Issues 30
    • 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
  • Ava Branch
  • bwbot
  • Issues
  • #27

Closed
Open
Created Jun 02, 2025 by Ava Branch@avabranch06999Owner

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 development 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 just a single model; it's a family of increasingly advanced AI systems. The advancement goes something like this:

DeepSeek V2:

This was the structure design which leveraged a mixture-of-experts architecture, where only a subset of experts are used at reasoning, garagesale.es dramatically enhancing the processing time for each token. It likewise included multi-head hidden attention to minimize memory footprint.

DeepSeek V3:

This model introduced FP8 training methods, which helped drive down training expenses by over 42.5% compared to previous models. FP8 is a less precise method to store weights inside the LLMs but can considerably enhance the memory footprint. However, training using FP8 can normally be unsteady, and it is hard to obtain the desired training outcomes. Nevertheless, DeepSeek uses numerous techniques and attains extremely stable FP8 training. V3 set the stage as a highly efficient design that was currently affordable (with claims of being 90% cheaper than some closed-source options).

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 design not simply to produce responses however to "believe" before answering. Using pure reinforcement knowing, the design was motivated to produce intermediate thinking actions, for instance, taking additional time (typically 17+ seconds) to resolve a basic issue like "1 +1."

The key innovation here was using group relative policy optimization (GROP). Instead of relying on a conventional process reward model (which would have needed annotating every action of the reasoning), GROP compares multiple outputs from the design. By tasting several possible responses and scoring them (utilizing rule-based measures like specific match for math or validating code outputs), the system discovers to favor reasoning that leads to the correct result without the requirement for explicit supervision of every intermediate thought.

DeepSeek R1:

Recognizing that R1-Zero's unsupervised approach produced thinking outputs that could be difficult to check out or even mix languages, the developers returned to the drawing board. They utilized the raw outputs from R1-Zero to generate "cold start" information and then by hand curated these examples to filter and enhance the quality of the reasoning. This human post-processing was then utilized to fine-tune the initial DeepSeek V3 model further-combining both reasoning-oriented reinforcement learning and supervised fine-tuning. The result is DeepSeek R1: a design that now produces readable, meaningful, and reputable thinking while still maintaining the efficiency and cost-effectiveness of its predecessors.

What Makes R1 Series Special?

The most remarkable element of R1 (zero) is how it established thinking abilities without specific supervision of the thinking process. It can be even more enhanced by using cold-start data and monitored support learning to produce understandable thinking on general jobs. Here's what sets it apart:

Open Source & Efficiency:

R1 is open source, permitting researchers and developers to examine and build on its innovations. Its expense efficiency is a major selling point particularly when compared to closed-source models (claimed 90% cheaper than OpenAI) that need huge compute budget plans.

Novel Training Approach:

Instead of relying exclusively on annotated thinking (which is both pricey and lengthy), the design was trained utilizing an outcome-based approach. It started with easily proven tasks, such as mathematics problems and disgaeawiki.info coding exercises, where the correctness of the last response might be quickly measured.

By utilizing group relative policy optimization, the training procedure compares numerous generated responses to figure out which ones satisfy the desired output. This relative scoring system permits the design to find out "how to believe" even when intermediate reasoning is produced in a freestyle way.

Overthinking?

A fascinating observation is that DeepSeek R1 in some cases "overthinks" easy issues. For instance, when asked "What is 1 +1?" it may invest nearly 17 seconds examining different scenarios-even thinking about binary representations-before concluding with the correct response. This self-questioning and verification process, although it may appear inefficient in the beginning glimpse, might show beneficial in intricate jobs where deeper thinking is needed.

Prompt Engineering:

Traditional few-shot prompting strategies, which have actually worked well for many chat-based designs, can really degrade performance with R1. The designers advise utilizing direct problem statements with a zero-shot approach that specifies the output format plainly. This makes sure that the design isn't led astray by extraneous examples or hints that may interfere with its internal thinking process.

Starting with R1

For those aiming to experiment:

Smaller versions (7B-8B) can operate on customer GPUs and even only CPUs


Larger versions (600B) need significant compute resources


Available through major cloud service providers


Can be deployed locally by means of Ollama or vLLM


Looking Ahead

We're especially intrigued by a number of implications:

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


Impact on agent-based AI systems traditionally constructed on chat models


Possibilities for integrating with other supervision strategies


Implications for business AI deployment


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

Open Questions

How will this impact the development of future thinking models?


Can this method be reached less verifiable domains?


What are the ramifications for multi-modal AI systems?


We'll be seeing these developments closely, particularly as the community starts to try out and build on these strategies.

Resources

Join our Slack community for continuous discussions and updates about DeepSeek and other AI advancements. 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 short summary


Cloud Providers:

Nvidia


Together.ai


AWS




Q&A

Q1: Which design deserves more attention - DeepSeek or Qwen2.5 Max?

A: While Qwen2.5 is likewise a strong model in the open-source neighborhood, the option ultimately depends on your use case. DeepSeek R1 emphasizes innovative thinking and an unique training technique that might be particularly important in tasks where verifiable reasoning is crucial.

Q2: Why did major service providers like OpenAI choose supervised fine-tuning rather than support knowing (RL) like DeepSeek?

A: We ought to note upfront that they do use RL at the really least in the type of RLHF. It is very likely that models from major providers that have reasoning abilities already utilize something similar to what DeepSeek has done here, but we can't make certain. It is also most likely that due to access to more resources, they favored monitored fine-tuning due to its stability and the all set availability of big annotated datasets. Reinforcement knowing, although effective, can be less foreseeable and more difficult to control. DeepSeek's technique innovates by applying RL in a reasoning-oriented way, allowing the design to find out efficient internal reasoning with only very little process annotation - a strategy that has shown promising in spite of its complexity.

Q3: Did DeepSeek utilize test-time calculate techniques comparable to those of OpenAI?

A: DeepSeek R1's design emphasizes efficiency by leveraging strategies such as the mixture-of-experts approach, pipewiki.org which triggers just a subset of criteria, to reduce compute throughout reasoning. This focus on performance is main to its expense advantages.

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

A: R1-Zero is the initial design that finds out reasoning solely through support learning without explicit procedure guidance. It generates intermediate thinking actions that, while sometimes raw or combined in language, act as the foundation for knowing. DeepSeek R1, on the other hand, refines these outputs through human post-processing and monitored fine-tuning. In essence, R1-Zero supplies the not being watched "stimulate," and R1 is the refined, more meaningful version.

Q5: How can one remain updated with thorough, technical research study while managing a hectic schedule?

A: Remaining current includes a combination of actively engaging with the research neighborhood (like AISC - see link to join slack above), following preprint servers like arXiv, participating in relevant conferences and webinars, and taking part in conversation groups and newsletters. Continuous engagement with online communities and collaborative research jobs likewise plays a key role in keeping up with technical improvements.

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

A: The brief answer is that it's too early to inform. DeepSeek R1's strength, however, depends on its robust thinking abilities and its effectiveness. It is particularly well fit for tasks that need verifiable logic-such as mathematical issue resolving, code generation, and structured decision-making-where intermediate reasoning can be examined and confirmed. Its open-source nature even more permits tailored applications in research and enterprise settings.

Q7: What are the ramifications of DeepSeek R1 for enterprises and start-ups?

A: The open-source and cost-effective style of DeepSeek R1 decreases the entry barrier for deploying innovative language designs. Enterprises and start-ups can leverage its sophisticated reasoning for agentic applications varying from automated code generation and customer support to data analysis. Its versatile deployment options-on customer hardware for smaller models or cloud platforms for larger ones-make it an attractive option to proprietary solutions.

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

A: While DeepSeek R1 has been observed to "overthink" simple problems by exploring numerous reasoning paths, it incorporates stopping criteria and examination systems to prevent boundless loops. The reinforcement discovering framework encourages merging towards a proven output, even in uncertain cases.

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

A: Yes, DeepSeek V3 is open source and served as the structure for later versions. It is built on its own set of innovations-including the mixture-of-experts method and FP8 training-and is not based on the Qwen architecture. Its design emphasizes performance and cost reduction, setting the stage for the thinking innovations seen in R1.

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

A: DeepSeek R1 is a text-based model and does not integrate vision abilities. Its style and training focus entirely on language processing and reasoning.

Q11: Can experts in specialized fields (for instance, labs working on cures) use these methods to train domain-specific models?

A: Yes. The innovations behind DeepSeek R1-such as its outcome-based thinking training and effective architecture-can be adjusted to various domains. Researchers in fields like biomedical sciences can tailor these methods to construct designs that address their specific difficulties while gaining from lower compute expenses and robust thinking abilities. It is most likely that in deeply specialized fields, nevertheless, there will still be a requirement for monitored fine-tuning to get trustworthy outcomes.

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

A: The conversation suggested that the annotators mainly focused on domains where correctness is quickly verifiable-such as math and coding. This recommends that knowledge in technical fields was certainly leveraged to guarantee the precision and clarity of the reasoning data.

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

A: While the design is designed to enhance for correct answers through reinforcement learning, there is constantly a danger of errors-especially in uncertain situations. However, by examining multiple prospect outputs and enhancing those that cause proven results, the training process decreases the probability of propagating incorrect thinking.

Q14: How are hallucinations decreased in the model provided its iterative thinking loops?

A: Using rule-based, proven tasks (such as math and coding) helps anchor the design's reasoning. By comparing multiple outputs and utilizing group relative policy optimization to only those that yield the correct outcome, the model is guided far from producing unproven or hallucinated details.

Q15: Does the model count on complex vector mathematics?

A: Yes, advanced techniques-including complex vector math-are integral to the implementation of mixture-of-experts and attention mechanisms in DeepSeek R1. However, the main focus is on utilizing these methods to make it possible for efficient reasoning instead of showcasing mathematical intricacy for its own sake.

Q16: Some fret that the design's "thinking" might not be as fine-tuned as human thinking. Is that a legitimate concern?

A: Early models like R1-Zero did produce raw and in some cases hard-to-read thinking. However, the subsequent improvement process-where human specialists curated and enhanced the thinking data-has substantially improved the clarity and dependability of DeepSeek R1's internal thought process. While it remains an evolving system, iterative training and feedback have caused meaningful enhancements.

Q17: Which design versions appropriate for regional implementation on a laptop computer with 32GB of RAM?

A: For local testing, a medium-sized model-typically in the series of 7B to 8B parameters-is advised. Larger models (for instance, those with numerous billions of criteria) require significantly more computational resources and are much better fit for cloud-based deployment.

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

A: DeepSeek R1 is supplied with open weights, indicating that its model specifications are publicly available. This lines up with the total open-source approach, enabling researchers and designers to further check out and build on its developments.

Q19: What would occur if the order of training were reversed-starting with supervised fine-tuning before not being watched support learning?

A: The existing method enables the model to first check out and create its own thinking patterns through unsupervised RL, and after that refine these patterns with monitored methods. Reversing the order might constrain the model's capability to find diverse reasoning paths, possibly restricting its general efficiency in tasks that gain from self-governing idea.

Thanks for checking out Deep Random Thoughts! Subscribe free of charge to get new posts and support my work.

Assignee
Assign to
Time tracking