Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Register
  • Sign in
  • D dashitech
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 54
    • Issues 54
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Terraform modules
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Vernita Gillen
  • dashitech
  • Issues
  • #52
Closed
Open
Issue created May 31, 2025 by Vernita Gillen@vernitatbq1073Owner

Understanding DeepSeek R1


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

The DeepSeek Family Tree: From V3 to R1

DeepSeek isn't just a single design; it's a family of significantly advanced AI systems. The development goes something like this:

DeepSeek V2:

This was the structure model which leveraged a mixture-of-experts architecture, where only a subset of professionals are utilized at inference, drastically enhancing the processing time for each token. It likewise featured multi-head hidden attention to reduce memory footprint.

DeepSeek V3:

This design presented FP8 training methods, which assisted drive down training expenses by over 42.5% compared to previous versions. FP8 is a less accurate method to save weights inside the LLMs however can greatly improve the memory footprint. However, training using FP8 can generally be unsteady, and it is difficult to obtain the desired training outcomes. Nevertheless, DeepSeek uses numerous tricks and attains extremely stable FP8 training. V3 set the stage as a highly effective model that was already 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 model. Here, the focus was on teaching the model not simply to produce responses however to "think" before addressing. Using pure reinforcement knowing, the model was encouraged to create intermediate reasoning actions, for instance, taking extra time (typically 17+ seconds) to work through a simple issue like "1 +1."

The crucial development here was the use of group relative policy optimization (GROP). Instead of relying on a standard procedure reward model (which would have needed annotating every action of the thinking), GROP compares several outputs from the design. By sampling a number of potential answers and scoring them (utilizing rule-based measures like precise match for math or verifying code outputs), the system learns to favor thinking that results in the correct outcome without the requirement for explicit guidance of every intermediate idea.

DeepSeek R1:

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

What Makes R1 Series Special?

The most fascinating aspect of R1 (absolutely no) is how it developed thinking abilities without explicit supervision of the reasoning process. It can be even more enhanced by using cold-start data and supervised reinforcement finding out to produce understandable thinking on general tasks. Here's what sets it apart:

Open Source & Efficiency:

R1 is open source, enabling scientists and designers to inspect and develop upon its developments. Its cost efficiency is a significant selling point particularly when compared to closed-source designs (claimed 90% less expensive than OpenAI) that require enormous calculate spending plans.

Novel Training Approach:

Instead of relying solely on annotated thinking (which is both costly and time-consuming), the model was trained utilizing an outcome-based method. It started with easily verifiable tasks, such as mathematics issues and coding exercises, where the correctness of the last response might be quickly determined.

By utilizing group relative policy optimization, the training procedure compares numerous produced answers to determine which ones meet the preferred output. This relative scoring mechanism permits the design to learn "how to think" even when intermediate thinking is produced in a freestyle manner.

Overthinking?

An interesting observation is that DeepSeek R1 sometimes "overthinks" easy problems. For hb9lc.org example, when asked "What is 1 +1?" it may invest nearly 17 seconds assessing different scenarios-even thinking about binary representations-before concluding with the proper response. This self-questioning and confirmation process, although it might seem inefficient at first glance, might show beneficial in intricate tasks where much deeper thinking is necessary.

Prompt Engineering:

Traditional few-shot prompting strategies, which have actually worked well for lots of chat-based designs, can really deteriorate efficiency with R1. The developers advise using direct problem declarations with a zero-shot technique that defines the output format plainly. This makes sure that the design isn't led astray by extraneous examples or hints that may disrupt its internal reasoning procedure.

Starting with R1

For those aiming to experiment:

Smaller variants (7B-8B) can work on customer GPUs and even only CPUs


Larger versions (600B) require significant compute resources


Available through significant cloud suppliers


Can be deployed locally by means of Ollama or vLLM


Looking Ahead

We're especially interested by numerous implications:

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


Effect on agent-based AI systems typically developed on chat models


Possibilities for combining with other guidance strategies


Implications for enterprise AI deployment


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

Open Questions

How will this affect the advancement of future thinking designs?


Can this approach be encompassed less proven domains?


What are the implications for multi-modal AI systems?


We'll be seeing these developments carefully, particularly as the community starts to experiment with and build on these methods.

Resources

Join our Slack community for ongoing conversations and updates about DeepSeek and other AI advancements. We're seeing remarkable applications already emerging from our bootcamp participants dealing with these models.

Chat with DeepSeek:


https://www.[deepseek](https://git.j4nis05.ch).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 design in the open-source neighborhood, the choice ultimately depends upon your use case. DeepSeek R1 emphasizes innovative reasoning and an unique training approach that might be especially important in jobs where proven logic is important.

Q2: Why did significant service providers like OpenAI select monitored fine-tuning rather than reinforcement knowing (RL) like DeepSeek?

A: We must note in advance that they do use RL at least in the kind of RLHF. It is extremely likely that models from significant suppliers that have thinking abilities currently utilize something similar to what DeepSeek has done here, however we can't make certain. It is also most likely that due to access to more resources, they preferred supervised fine-tuning due to its stability and the all set availability of big annotated datasets. Reinforcement knowing, although powerful, can be less foreseeable and harder to control. DeepSeek's method innovates by applying RL in a reasoning-oriented way, allowing the model to find out reliable internal thinking with only very little procedure annotation - a technique that has shown appealing regardless of its intricacy.

Q3: Did DeepSeek use test-time calculate strategies comparable to those of OpenAI?

A: DeepSeek R1's style emphasizes effectiveness by leveraging strategies such as the mixture-of-experts technique, which activates just a subset of criteria, to minimize calculate during inference. This focus on efficiency is main to its expense benefits.

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

A: R1-Zero is the preliminary design that discovers reasoning entirely through reinforcement knowing without explicit procedure supervision. It generates intermediate thinking actions that, while in some cases raw or blended in language, function as the structure for learning. DeepSeek R1, on the other hand, fine-tunes these outputs through human post-processing and monitored fine-tuning. In essence, R1-Zero supplies the not being watched "stimulate," and R1 is the sleek, more coherent variation.

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

A: Remaining present 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, going to pertinent conferences and webinars, and taking part in conversation groups and newsletters. Continuous engagement with online neighborhoods and collective research jobs likewise plays a key role in staying up to date with technical developments.

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

A: The brief answer is that it's prematurely to tell. DeepSeek R1's strength, nevertheless, lies in its robust reasoning abilities and its efficiency. It is particularly well suited for tasks that require proven logic-such as mathematical issue resolving, code generation, and structured decision-making-where intermediate reasoning can be examined and verified. Its open-source nature even more enables for tailored applications in research study and enterprise settings.

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

A: The open-source and affordable design of DeepSeek R1 reduces the entry barrier for releasing sophisticated language designs. Enterprises and start-ups can take advantage of its innovative thinking for agentic applications ranging from automated code generation and client assistance to data analysis. Its versatile release options-on customer hardware for smaller models or cloud platforms for larger ones-make it an attractive alternative to proprietary services.

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

A: While DeepSeek R1 has been observed to "overthink" easy problems by exploring several reasoning paths, it integrates stopping criteria and assessment systems to avoid infinite loops. The reinforcement learning structure motivates merging towards a proven output, even in uncertain cases.

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

A: Yes, DeepSeek V3 is open source and served as the structure for later models. It is constructed 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 stresses performance and cost reduction, setting the phase for the reasoning developments 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 capabilities. Its style and training focus entirely on language processing and thinking.

Q11: Can specialists in specialized fields (for example, labs dealing with remedies) use these methods to train domain-specific designs?

A: Yes. The developments behind R1-such as its outcome-based reasoning training and efficient architecture-can be adjusted to different domains. Researchers in fields like biomedical sciences can tailor these techniques to construct designs that resolve their particular challenges while gaining from lower calculate expenses and robust reasoning abilities. It is likely that in deeply specialized fields, however, there will still be a need for supervised fine-tuning to get reliable results.

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

A: The conversation suggested that the annotators mainly focused on domains where correctness is easily verifiable-such as mathematics and higgledy-piggledy.xyz coding. This suggests that know-how in technical fields was certainly leveraged to guarantee the accuracy and clarity of the thinking data.

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

A: While the design is designed to enhance for right responses through support learning, there is always a threat of errors-especially in uncertain scenarios. However, by assessing multiple candidate outputs and enhancing those that result in proven results, the training process minimizes the probability of propagating incorrect thinking.

Q14: How are hallucinations reduced in the model given its iterative thinking loops?

A: Making use of rule-based, proven tasks (such as mathematics and coding) helps anchor the design's thinking. By comparing multiple outputs and using group relative policy optimization to strengthen only those that yield the correct outcome, the design is guided away from producing unfounded or hallucinated details.

Q15: Does the model count 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 using these strategies 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 refined as human reasoning. Is that a legitimate concern?

A: Early models like R1-Zero did produce raw and often hard-to-read thinking. However, the subsequent refinement process-where human experts curated and enhanced the thinking data-has substantially boosted the clarity and reliability of DeepSeek R1's internal idea procedure. While it remains a progressing system, iterative training and feedback have actually caused meaningful enhancements.

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

A: For regional testing, a medium-sized model-typically in the variety of 7B to 8B parameters-is advised. Larger models (for example, those with numerous billions of criteria) need substantially more computational resources and are much better fit 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, indicating that its design parameters are openly available. This aligns with the general open-source philosophy, enabling researchers and designers to more explore and build upon its developments.

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

A: The current technique permits the design to first check out and produce its own thinking patterns through not being watched RL, and then refine these patterns with monitored methods. Reversing the order may constrain the model's ability to find varied reasoning paths, possibly limiting its general efficiency in tasks that gain from autonomous thought.

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

Assignee
Assign to
Time tracking