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 25
    • Issues 25
    • 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
  • #20

Closed
Open
Created May 28, 2025 by Ava Branch@avabranch06999Owner

Understanding DeepSeek R1


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

The DeepSeek Family Tree: From V3 to R1

DeepSeek isn't just a single model; it's a household of significantly advanced AI systems. The evolution goes something like this:

DeepSeek V2:

This was the foundation model which leveraged a mixture-of-experts architecture, where just a subset of specialists are utilized at reasoning, significantly enhancing the processing time for each token. It likewise featured multi-head hidden attention to lower memory footprint.

DeepSeek V3:

This design presented FP8 training methods, which assisted drive down training costs by over 42.5% compared to previous models. FP8 is a less precise method to keep weights inside the LLMs however can significantly improve the memory footprint. However, training utilizing FP8 can usually be unstable, and it is tough to obtain the preferred training results. Nevertheless, DeepSeek uses numerous techniques and attains incredibly stable FP8 training. V3 set the stage as an extremely effective model that was currently cost-effective (with claims of being 90% cheaper than some closed-source options).

DeepSeek R1-Zero:

With V3 as the base, the group then introduced R1-Zero, the very first reasoning-focused iteration. Here, the focus was on teaching the model not simply to generate answers however to "think" before answering. Using pure support knowing, the design was encouraged to create intermediate thinking steps, for example, taking additional time (often 17+ seconds) to overcome an easy issue like "1 +1."

The crucial development here was the usage of group relative policy optimization (GROP). Instead of counting on a standard procedure benefit model (which would have required annotating every action of the thinking), GROP compares several outputs from the model. By tasting several potential responses and scoring them (utilizing rule-based measures like precise match for math or validating code outputs), the system to prefer reasoning that results in the right outcome without the requirement for specific guidance of every intermediate idea.

DeepSeek R1:

Recognizing that R1-Zero's unsupervised approach produced reasoning outputs that might be hard to check out and even mix languages, the designers went back to the drawing board. They used the raw outputs from R1-Zero to produce "cold start" information and after that by hand curated these examples to filter and improve the quality of the reasoning. This human post-processing was then used 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 understandable, meaningful, and reputable reasoning while still maintaining the effectiveness and cost-effectiveness of its predecessors.

What Makes R1 Series Special?

The most interesting aspect of R1 (no) is how it established thinking abilities without specific supervision of the thinking process. It can be even more enhanced by using cold-start information and supervised reinforcement finding out to produce readable reasoning on basic jobs. Here's what sets it apart:

Open Source & Efficiency:

R1 is open source, enabling scientists and developers to check and build on its innovations. Its expense effectiveness is a significant selling point particularly when compared to closed-source designs (claimed 90% less expensive than OpenAI) that require massive calculate budgets.

Novel Training Approach:

Instead of relying entirely on annotated reasoning (which is both costly and time-consuming), the model was trained utilizing an outcome-based method. It began with quickly verifiable tasks, such as math issues and coding exercises, where the accuracy of the last answer could be easily determined.

By utilizing group relative policy optimization, the training process compares multiple generated responses to identify which ones fulfill the desired output. This relative scoring system allows the model to learn "how to think" even when intermediate reasoning is produced in a freestyle way.

Overthinking?

An intriguing observation is that DeepSeek R1 sometimes "overthinks" simple issues. For example, when asked "What is 1 +1?" it might spend almost 17 seconds examining various scenarios-even considering binary representations-before concluding with the appropriate response. This self-questioning and verification process, although it might appear ineffective in the beginning look, might prove beneficial in complex jobs where much deeper reasoning is required.

Prompt Engineering:

Traditional few-shot prompting techniques, which have actually worked well for numerous chat-based designs, can really deteriorate performance with R1. The designers suggest using direct problem statements with a zero-shot technique that defines the output format plainly. This ensures that the model isn't led astray by extraneous examples or hints that might hinder its internal thinking process.

Getting Going with R1

For those aiming to experiment:

Smaller variations (7B-8B) can run on consumer GPUs or even just CPUs


Larger versions (600B) need significant compute resources


Available through major cloud service providers


Can be deployed in your area via Ollama or vLLM


Looking Ahead

We're particularly fascinated by several ramifications:

The capacity for this technique to be used to other reasoning domains


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


Possibilities for combining with other supervision methods


Implications for business AI release


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

Open Questions

How will this affect the development of future thinking models?


Can this method be encompassed less proven domains?


What are the ramifications for multi-modal AI systems?


We'll be seeing these advancements carefully, especially as the community starts to explore and construct upon these strategies.

Resources

Join our Slack neighborhood for continuous discussions and updates about DeepSeek and yewiki.org other AI advancements. We're seeing remarkable applications currently emerging from our bootcamp individuals working 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 is worthy of more attention - DeepSeek or Qwen2.5 Max?

A: While Qwen2.5 is also a strong design in the open-source community, the choice ultimately depends upon your usage case. DeepSeek R1 stresses advanced reasoning and a novel training technique that may be especially valuable in tasks where proven reasoning is vital.

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

A: We must keep in mind upfront that they do use RL at least in the type of RLHF. It is highly likely that models from major companies that have reasoning abilities currently use 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 preferred monitored fine-tuning due to its stability and the prepared availability of large annotated datasets. Reinforcement learning, although powerful, can be less predictable and harder to control. DeepSeek's method innovates by applying RL in a reasoning-oriented way, making it possible for the design to find out efficient internal thinking with only very little procedure annotation - a method that has actually proven promising regardless of its intricacy.

Q3: Did DeepSeek use test-time calculate techniques similar to those of OpenAI?

A: DeepSeek R1's style stresses efficiency by leveraging methods such as the mixture-of-experts approach, which activates only a subset of criteria, to minimize calculate throughout inference. This focus on effectiveness is main to its expense benefits.

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

A: R1-Zero is the preliminary design that finds out thinking exclusively through reinforcement knowing without specific process supervision. It produces intermediate thinking actions that, while often raw or mixed in language, work as the foundation for learning. DeepSeek R1, on the other hand, refines these outputs through human post-processing and monitored fine-tuning. In essence, R1-Zero offers the without supervision "stimulate," and R1 is the sleek, more meaningful variation.

Q5: How can one remain upgraded with extensive, technical research while managing a hectic schedule?

A: Remaining existing includes a combination of actively engaging with the research study community (like AISC - see link to sign up with slack above), following preprint servers like arXiv, attending appropriate conferences and webinars, and taking part in conversation groups and newsletters. Continuous engagement with online communities and collaborative research study tasks also plays a key function in keeping up with technical advancements.

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

A: The brief response is that it's prematurely to inform. DeepSeek R1's strength, however, depends on its robust reasoning abilities and its efficiency. It is particularly well fit for tasks that need verifiable logic-such as mathematical problem solving, code generation, and structured decision-making-where intermediate thinking can be examined and confirmed. Its open-source nature further permits tailored applications in research and business settings.

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

A: The open-source and affordable style of DeepSeek R1 lowers the entry barrier for releasing innovative language models. Enterprises and start-ups can take advantage of its advanced reasoning for agentic applications ranging from automated code generation and client support to data analysis. Its versatile release options-on customer hardware for smaller designs or cloud platforms for bigger ones-make it an appealing alternative to exclusive solutions.

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

A: While DeepSeek R1 has actually been observed to "overthink" basic problems by exploring several reasoning paths, it includes stopping requirements and evaluation mechanisms to prevent limitless loops. The support discovering structure encourages merging towards a proven output, even in uncertain cases.

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

A: Yes, DeepSeek V3 is open source and acted as the foundation 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 upon the Qwen architecture. Its design stresses efficiency and expense reduction, setting the stage for the reasoning innovations seen in R1.

Q10: How does DeepSeek R1 perform on vision jobs?

A: DeepSeek R1 is a text-based design and does not include vision abilities. Its design and training focus exclusively on language processing and reasoning.

Q11: Can specialists in specialized fields (for example, labs dealing with cures) apply these methods to train domain-specific models?

A: Yes. The developments behind DeepSeek R1-such as its outcome-based thinking training and effective architecture-can be adapted to different domains. Researchers in fields like biomedical sciences can tailor these approaches to construct designs that resolve their particular challenges while gaining from lower calculate expenses and robust reasoning capabilities. It is most likely that in deeply specialized fields, nevertheless, there will still be a requirement for monitored fine-tuning to get reliable results.

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

A: The conversation indicated that the annotators mainly focused on domains where correctness is quickly verifiable-such as mathematics and coding. This recommends that knowledge in technical fields was certainly leveraged to guarantee the accuracy and clarity of the thinking information.

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

A: While the model is developed to optimize for appropriate responses by means of support learning, there is constantly a danger of errors-especially in uncertain situations. However, by evaluating numerous candidate outputs and strengthening those that lead to verifiable results, the training procedure minimizes the probability of propagating incorrect reasoning.

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

A: Using rule-based, proven tasks (such as math and coding) helps anchor the model's thinking. By comparing numerous outputs and utilizing group relative policy optimization to reinforce just those that yield the appropriate result, the model is guided away from creating unproven or hallucinated details.

Q15: Does the model depend on complex vector mathematics?

A: Yes, advanced techniques-including complex vector math-are essential to the application of mixture-of-experts and attention systems in DeepSeek R1. However, the main focus is on utilizing these methods to make it possible for effective reasoning rather than showcasing mathematical complexity for its own sake.

Q16: Some stress that the design's "thinking" may not be as fine-tuned as human thinking. Is that a valid issue?

A: Early versions like R1-Zero did produce raw and often hard-to-read thinking. However, the subsequent refinement process-where human experts curated and improved the thinking data-has considerably boosted the clarity and dependability of DeepSeek R1's internal thought process. While it remains an evolving system, iterative training and feedback have actually caused significant enhancements.

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

A: For local screening, a medium-sized model-typically in the range of 7B to 8B parameters-is advised. Larger designs (for instance, those with numerous billions of specifications) need considerably more computational resources and are much better matched for cloud-based deployment.

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

A: DeepSeek R1 is provided with open weights, meaning that its design criteria are openly available. This aligns with the general open-source approach, allowing researchers and developers to additional explore and construct upon its innovations.

Q19: What would happen if the order of training were reversed-starting with supervised fine-tuning before without supervision support learning?

A: The current technique permits the design to first check out and produce its own thinking patterns through without supervision RL, and then fine-tune these patterns with monitored techniques. Reversing the order may constrain the model's capability to discover varied reasoning paths, potentially limiting its total performance in jobs that gain from self-governing idea.

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

Assignee
Assign to
Time tracking