Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • X xunzhishimin
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Issues 23
    • Issues 23
    • List
    • Boards
    • Service Desk
    • Milestones
  • Redmine
    • Redmine
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Infrastructure Registry
  • Analytics
    • Analytics
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Create a new issue
  • Jobs
  • Issue Boards
Collapse sidebar
  • Ashton Reda
  • xunzhishimin
  • Issues
  • #22

Closed
Open
Created May 31, 2025 by Ashton Reda@ashtonreda284Maintainer

Understanding DeepSeek R1


We've been tracking the explosive increase of DeepSeek R1, which has taken the AI world by storm in recent weeks. In this session, we dove deep into the evolution of the DeepSeek household - from the early models through DeepSeek V3 to the advancement R1. We also explored the technical innovations that make R1 so special worldwide 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 development goes something like this:

DeepSeek V2:

This was the foundation design which leveraged a mixture-of-experts architecture, where just a subset of specialists are used at inference, dramatically enhancing the processing time for each token. It likewise featured multi-head latent attention to minimize memory footprint.

DeepSeek V3:

This design introduced FP8 training techniques, which helped drive down training expenses by over 42.5% compared to previous versions. FP8 is a less exact way to store weights inside the LLMs however can significantly improve the memory footprint. However, training utilizing FP8 can usually be unsteady, and it is difficult to obtain the desired training results. Nevertheless, DeepSeek utilizes multiple techniques and attains extremely stable FP8 training. V3 set the stage as an extremely efficient design that was already (with claims of being 90% less expensive than some closed-source options).

DeepSeek R1-Zero:

With V3 as the base, the group then presented R1-Zero, the very first reasoning-focused model. Here, the focus was on teaching the model not simply to generate answers but to "think" before addressing. Using pure support knowing, the design was encouraged to produce intermediate thinking actions, for example, taking additional time (typically 17+ seconds) to resolve a basic issue like "1 +1."

The essential innovation here was the use of group relative policy optimization (GROP). Instead of relying on a conventional process benefit design (which would have required annotating every action of the thinking), GROP compares multiple outputs from the model. By tasting a number of potential responses and scoring them (using rule-based steps like precise match for math or verifying code outputs), the system finds out to favor thinking that results in the right result without the requirement for explicit guidance of every intermediate idea.

DeepSeek R1:

Recognizing that R1-Zero's without supervision technique produced reasoning outputs that could be tough to read and even blend languages, the developers returned to the drawing board. They utilized the raw outputs from R1-Zero to create "cold start" information and then manually curated these examples to filter and improve 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 result is DeepSeek R1: a design that now produces readable, coherent, and trustworthy thinking while still maintaining the efficiency and cost-effectiveness of its predecessors.

What Makes R1 Series Special?

The most fascinating aspect of R1 (zero) is how it developed reasoning capabilities without explicit guidance of the thinking process. It can be further enhanced by utilizing cold-start data and supervised support learning 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 inspect and build on its innovations. Its expense effectiveness is a major selling point specifically when compared to closed-source models (claimed 90% cheaper than OpenAI) that require huge calculate budget plans.

Novel Training Approach:

Instead of relying entirely on annotated reasoning (which is both pricey and time-consuming), the model was trained using an outcome-based method. It started with easily verifiable jobs, such as math problems and coding exercises, where the accuracy of the final response might be quickly determined.

By using group relative policy optimization, the training process compares several generated answers to figure out which ones satisfy the wanted output. This relative scoring mechanism allows the model to find out "how to believe" even when intermediate reasoning is generated in a freestyle way.

Overthinking?

An intriguing observation is that DeepSeek R1 in some cases "overthinks" easy issues. For example, when asked "What is 1 +1?" it may spend nearly 17 seconds examining different scenarios-even thinking about binary representations-before concluding with the correct answer. This self-questioning and confirmation process, although it might seem inefficient initially look, might show helpful in complicated tasks where deeper reasoning is essential.

Prompt Engineering:

Traditional few-shot triggering techniques, which have worked well for lots of chat-based designs, can really break down efficiency with R1. The developers advise utilizing direct issue 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 might disrupt its internal thinking procedure.

Getting Started with R1

For those aiming to experiment:

Smaller variations (7B-8B) can work on customer GPUs or even only CPUs


Larger versions (600B) require substantial calculate resources


Available through major cloud providers


Can be deployed in your area through Ollama or vLLM


Looking Ahead

We're particularly interested by a number of implications:

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


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


Possibilities for combining with other guidance strategies


Implications for enterprise AI release


Thanks for reading 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 designs?


Can this method be extended to less proven domains?


What are the implications for multi-modal AI systems?


We'll be watching these advancements carefully, particularly as the community begins to try out and build on these techniques.

Resources

Join our Slack community for continuous conversations and updates about DeepSeek and other AI developments. We're seeing interesting 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 design deserves more attention - DeepSeek or Qwen2.5 Max?

A: While Qwen2.5 is likewise a strong model in the open-source community, the option eventually depends on your usage case. DeepSeek R1 stresses sophisticated reasoning and a novel training technique that might be especially important in tasks where verifiable reasoning is crucial.

Q2: Why did major companies like OpenAI decide for monitored fine-tuning instead of support learning (RL) like DeepSeek?

A: We should keep in mind in advance that they do utilize RL at least in the kind of RLHF. It is likely that designs from significant providers that have thinking abilities already use something comparable to what DeepSeek has actually done here, however we can't make certain. It is likewise likely that due to access to more resources, they favored monitored fine-tuning due to its stability and the ready availability of big annotated datasets. Reinforcement knowing, although powerful, can be less predictable and harder to control. DeepSeek's approach innovates by applying RL in a reasoning-oriented manner, allowing the model to discover efficient internal reasoning with only minimal procedure annotation - a technique that has proven appealing despite its intricacy.

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

A: DeepSeek R1's design stresses performance by leveraging techniques such as the mixture-of-experts method, which triggers only a subset of parameters, to lower compute during inference. This concentrate on performance is main to its expense benefits.

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

A: R1-Zero is the initial design that finds out reasoning entirely through support learning without specific process guidance. It produces intermediate reasoning steps that, while in some cases raw or mixed in language, act 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 supplies the without supervision "stimulate," and R1 is the sleek, more coherent version.

Q5: How can one remain upgraded with extensive, technical research study while handling a busy schedule?

A: Remaining current includes a combination of actively engaging with the research community (like AISC - see link to sign up with slack above), following preprint servers like arXiv, attending relevant conferences and webinars, and taking part in conversation groups and newsletters. Continuous engagement with online neighborhoods and collaborative research projects also plays an essential role in staying up to date with technical developments.

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

A: The brief response is that it's prematurely to inform. DeepSeek R1's strength, however, lies in its robust thinking abilities and its efficiency. It is especially well matched for tasks that require proven logic-such as mathematical issue solving, code generation, and structured decision-making-where intermediate reasoning can be examined and confirmed. Its open-source nature further enables tailored applications in research study and business settings.

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

A: The open-source and cost-efficient style of DeepSeek R1 decreases the entry barrier for deploying sophisticated language designs. Enterprises and start-ups can utilize its sophisticated reasoning for agentic applications ranging from automated code generation and consumer support to data analysis. Its flexible release options-on consumer hardware for smaller sized designs or cloud platforms for bigger ones-make it an appealing option to exclusive solutions.

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

A: While DeepSeek R1 has been observed to "overthink" basic issues by exploring several thinking paths, it integrates stopping criteria and assessment systems to avoid boundless loops. The support discovering structure motivates convergence 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 functioned as the structure for later versions. It is developed on its own set of innovations-including the mixture-of-experts approach and FP8 training-and is not based upon the Qwen architecture. Its design emphasizes efficiency and expense reduction, setting the phase for the reasoning developments seen in R1.

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

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

Q11: Can professionals in specialized fields (for example, labs dealing with treatments) apply these approaches to train domain-specific models?

A: Yes. The innovations 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 methods to construct designs that resolve their specific obstacles while gaining from lower compute costs and robust reasoning capabilities. It is likely that in deeply specialized fields, nevertheless, there will still be a need 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 discussion suggested that the annotators mainly focused on domains where correctness is quickly verifiable-such as math and coding. This recommends that competence in technical fields was certainly leveraged to guarantee the accuracy and clearness of the reasoning information.

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

A: While the model is designed to enhance for correct responses by means of support knowing, there is always a threat of errors-especially in uncertain situations. However, by evaluating multiple prospect outputs and enhancing those that cause verifiable results, the training procedure decreases the likelihood of propagating incorrect reasoning.

Q14: wiki.eqoarevival.com How are hallucinations minimized in the design offered its iterative reasoning loops?

A: Using rule-based, verifiable jobs (such as math and coding) helps anchor the design's reasoning. By comparing multiple outputs and utilizing group relative policy optimization to reinforce just those that yield the appropriate outcome, the design is assisted away from creating unfounded or hallucinated details.

Q15: Does the model depend on complex vector mathematics?

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

Q16: Some worry that the design's "thinking" might not be as refined as human reasoning. Is that a valid issue?

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

Q17: Which design variations are suitable for regional implementation on a laptop computer with 32GB of RAM?

A: For local screening, a medium-sized model-typically in the variety of 7B to 8B parameters-is recommended. Larger models (for instance, wavedream.wiki those with numerous billions of specifications) need considerably more computational resources and are better suited for cloud-based implementation.

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

A: DeepSeek R1 is offered with open weights, indicating that its model parameters are publicly available. This aligns with the total open-source philosophy, enabling researchers and developers to additional check out and develop upon its innovations.

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

A: The existing technique permits the design to initially check out and create its own reasoning patterns through unsupervised RL, and after that refine these patterns with supervised techniques. Reversing the order may constrain the design's capability to discover diverse reasoning paths, potentially restricting its general efficiency in tasks that gain from autonomous idea.

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

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking

Powered by Tecnologia Edebe Brasil - 2019-2020