Skip to content

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Sign in / Register
M
myafritube
  • Project
    • Project
    • Details
    • Activity
    • Cycle Analytics
  • Issues 20
    • Issues 20
    • List
    • Board
    • Labels
    • Milestones
  • Merge Requests 0
    • Merge Requests 0
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Create a new issue
  • Jobs
  • Issue Boards
  • Agueda Krimper
  • myafritube
  • Issues
  • #19

Closed
Open
Opened Jun 02, 2025 by Agueda Krimper@aguedakrimper
  • Report abuse
  • New issue
Report abuse New issue

Understanding DeepSeek R1


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

The DeepSeek Ancestral Tree: From V3 to R1

DeepSeek isn't simply a single design; it's a family of progressively sophisticated AI systems. The advancement goes something like this:

DeepSeek V2:

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

DeepSeek V3:

This design presented FP8 training methods, which helped drive down training costs by over 42.5% compared to previous versions. FP8 is a less exact method to keep weights inside the LLMs however can greatly improve the memory footprint. However, training utilizing FP8 can typically be unsteady, and it is hard to obtain the preferred training results. Nevertheless, DeepSeek uses numerous tricks and attains extremely stable FP8 training. V3 set the stage as a highly efficient model that was currently economical (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 design not simply to produce responses but to "think" before responding to. Using pure support knowing, the design was encouraged to produce intermediate thinking actions, for example, taking additional time (frequently 17+ seconds) to work through a basic problem like "1 +1."

The essential development here was using group relative policy optimization (GROP). Instead of counting on a conventional procedure reward model (which would have needed annotating every action of the reasoning), GROP compares multiple outputs from the model. By tasting several potential responses and scoring them (utilizing rule-based measures like for mathematics or verifying code outputs), the system learns to prefer thinking that causes the right result without the requirement for specific supervision of every intermediate idea.

DeepSeek R1:

Recognizing that R1-Zero's not being watched method produced thinking outputs that might be difficult to read or even mix languages, the developers went back to the drawing board. They used the raw outputs from R1-Zero to generate "cold start" information and then manually curated these examples to filter and improve the quality of the reasoning. This human post-processing was then used to fine-tune the initial DeepSeek V3 model further-combining both reasoning-oriented support learning and monitored fine-tuning. The outcome is DeepSeek R1: a model that now produces readable, meaningful, and trusted reasoning while still maintaining the effectiveness and cost-effectiveness of its predecessors.

What Makes R1 Series Special?

The most fascinating aspect of R1 (zero) is how it developed reasoning abilities without explicit guidance of the reasoning procedure. It can be further improved by using cold-start information and supervised support discovering to produce readable reasoning on general jobs. Here's what sets it apart:

Open Source & Efficiency:

R1 is open source, permitting scientists and designers to examine and construct upon its innovations. Its expense effectiveness is a significant selling point particularly when compared to closed-source designs (claimed 90% cheaper than OpenAI) that need enormous compute budget plans.

Novel Training Approach:

Instead of relying entirely on annotated thinking (which is both pricey and lengthy), the design was trained using an outcome-based approach. It began with easily verifiable jobs, such as mathematics issues and coding workouts, where the accuracy of the last answer could be easily measured.

By utilizing group relative policy optimization, the training process compares numerous produced answers to identify which ones meet the preferred output. This relative scoring mechanism allows the model to find out "how to believe" even when intermediate thinking is created in a freestyle way.

Overthinking?

An interesting observation is that DeepSeek R1 in some cases "overthinks" basic issues. For example, when asked "What is 1 +1?" it might spend almost 17 seconds evaluating different scenarios-even considering binary representations-before concluding with the right answer. This self-questioning and confirmation procedure, although it may seem ineffective in the beginning glimpse, could show beneficial in complex jobs where much deeper reasoning is essential.

Prompt Engineering:

Traditional few-shot prompting strategies, which have worked well for many chat-based designs, can in fact deteriorate efficiency with R1. The developers suggest utilizing direct problem declarations with a zero-shot approach that specifies the output format plainly. This ensures that the model isn't led astray by extraneous examples or tips that may interfere with its internal reasoning process.

Getting Going with R1

For those aiming to experiment:

Smaller versions (7B-8B) can run on customer GPUs or even just CPUs


Larger variations (600B) need substantial compute resources


Available through major cloud companies


Can be released locally through Ollama or vLLM


Looking Ahead

We're especially captivated by several implications:

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


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


Possibilities for integrating with other supervision strategies


Implications for business AI release


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

Open Questions

How will this impact the development of future thinking models?


Can this approach be extended to less proven domains?


What are the implications for multi-modal AI systems?


We'll be seeing these developments closely, especially as the community begins to explore and build on these techniques.

Resources

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

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 design deserves more attention - DeepSeek or Qwen2.5 Max?

A: While Qwen2.5 is also a strong design in the open-source community, the option eventually depends on your usage case. DeepSeek R1 stresses innovative thinking and an unique training method that may be specifically important in tasks where proven logic is critical.

Q2: Why did significant service providers like OpenAI select monitored fine-tuning instead of reinforcement learning (RL) like DeepSeek?

A: We must note in advance that they do utilize RL at the minimum in the type of RLHF. It is most likely that designs from significant service providers that have thinking abilities currently use something similar to what DeepSeek has actually done here, but 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 prepared availability of large annotated datasets. Reinforcement learning, although powerful, can be less foreseeable and harder to manage. DeepSeek's method innovates by using RL in a reasoning-oriented way, allowing the model to find out reliable internal reasoning with only minimal process annotation - a technique that has shown promising in spite of its intricacy.

Q3: Did DeepSeek utilize test-time compute strategies similar to those of OpenAI?

A: DeepSeek R1's style stresses performance by leveraging strategies such as the mixture-of-experts approach, which triggers just a subset of parameters, to reduce calculate during 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 learns thinking exclusively through support knowing without specific procedure guidance. It creates intermediate reasoning actions that, while sometimes raw or blended 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 not being watched "spark," and R1 is the polished, more coherent variation.

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

A: Remaining current involves a combination of actively engaging with the research study community (like AISC - see link to join slack above), following preprint servers like arXiv, going to relevant conferences and webinars, and taking part in discussion groups and newsletters. Continuous engagement with online neighborhoods and collective research study projects likewise plays a key role in staying up to date with technical improvements.

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

A: The short response is that it's too early to inform. DeepSeek R1's strength, however, lies in its robust thinking capabilities and its effectiveness. It is particularly well fit for tasks that need proven logic-such as mathematical problem resolving, code generation, and structured decision-making-where intermediate thinking can be reviewed and verified. 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-efficient design of DeepSeek R1 lowers the entry barrier for deploying innovative language designs. Enterprises and start-ups can leverage its advanced reasoning for agentic applications varying from automated code generation and client assistance to information analysis. Its flexible implementation options-on consumer hardware for smaller sized designs or cloud platforms for bigger ones-make it an attractive option to proprietary options.

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

A: While DeepSeek R1 has actually been observed to "overthink" simple problems by checking out numerous reasoning paths, it incorporates stopping criteria and evaluation mechanisms to prevent unlimited loops. The support learning framework encourages convergence toward 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 functioned as the structure for later iterations. It is built on its own set of innovations-including the mixture-of-experts technique and FP8 training-and is not based upon the Qwen architecture. Its design stresses effectiveness and cost reduction, setting the stage for the reasoning developments seen in R1.

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

A: DeepSeek R1 is a text-based model 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 approaches to train domain-specific designs?

A: Yes. The developments behind DeepSeek R1-such as its outcome-based reasoning training and effective architecture-can be adapted to different domains. Researchers in fields like biomedical sciences can tailor these methods to develop models that address their specific difficulties while gaining from lower compute costs and robust thinking abilities. It is most likely that in deeply specialized fields, nevertheless, there will still be a requirement for wiki.snooze-hotelsoftware.de monitored 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 discussion showed that the annotators mainly focused on domains where accuracy is quickly verifiable-such as mathematics and coding. This recommends that expertise in technical fields was certainly leveraged to guarantee the accuracy and clarity of the thinking information.

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

A: While the model is designed to enhance for correct responses via support knowing, there is constantly a threat of errors-especially in uncertain scenarios. However, by evaluating multiple prospect outputs and reinforcing those that cause verifiable results, the training procedure minimizes the likelihood of propagating inaccurate thinking.

Q14: How are hallucinations lessened in the design given its iterative thinking loops?

A: The usage of rule-based, verifiable jobs (such as math and coding) helps anchor the design's reasoning. By comparing several outputs and using group relative policy optimization to enhance just those that yield the proper outcome, the design is directed away from creating unfounded or hallucinated details.

Q15: Does the model count on complex vector mathematics?

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

Q16: Some worry that the model's "thinking" may not be as refined as human reasoning. Is that a legitimate issue?

A: Early versions like R1-Zero did produce raw and often hard-to-read reasoning. However, the subsequent refinement process-where human specialists curated and improved the reasoning data-has considerably boosted the clarity and reliability of DeepSeek R1's internal idea process. While it remains an evolving system, iterative training and feedback have resulted in meaningful enhancements.

Q17: Which design variations are ideal for regional release on a laptop with 32GB of RAM?

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

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

A: DeepSeek R1 is provided with open weights, indicating that its design specifications are openly available. This lines up with the general open-source approach, allowing scientists and developers to additional explore and build on its developments.

Q19: What would take place if the order of training were reversed-starting with supervised fine-tuning before unsupervised support learning?

A: The existing approach enables the design to initially check out and produce its own reasoning patterns through not being watched RL, and after that improve these patterns with supervised approaches. Reversing the order might constrain the design's capability to discover diverse thinking paths, potentially restricting its overall efficiency in jobs that gain from autonomous idea.

Thanks for reading Deep Random Thoughts! Subscribe for free to receive new posts and support my work.

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
No due date
0
Labels
None
Assign labels
  • View project labels
Reference: aguedakrimper/myafritube#19