Skip to content

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
    • Help
    • Contribute to GitLab
  • Sign in / Register
C
cooqie
  • Project
    • Project
    • Details
    • Activity
    • Cycle Analytics
  • Issues 32
    • Issues 32
    • 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
  • Cassandra Moody
  • cooqie
  • Issues
  • #15

Closed
Open
Opened Feb 27, 2025 by Cassandra Moody@cassandramoody
  • Report abuse
  • New issue
Report abuse New issue

Understanding DeepSeek R1


We have actually 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 family - from the early designs through DeepSeek V3 to the breakthrough R1. We also checked out the technical developments that make R1 so special in the world of open-source AI.

The DeepSeek Ancestral Tree: From V3 to R1

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

DeepSeek V2:

This was the structure model which leveraged a mixture-of-experts architecture, where only a subset of specialists are used at reasoning, significantly enhancing the processing time for each token. It also included multi-head latent attention to reduce memory footprint.

DeepSeek V3:

This design presented FP8 training techniques, which helped drive down training expenses by over 42.5% compared to previous models. FP8 is a less precise way to save weights inside the LLMs but can significantly improve the memory footprint. However, training using FP8 can normally be unsteady, systemcheck-wiki.de and it is tough to obtain the wanted training results. Nevertheless, DeepSeek utilizes multiple techniques and attains remarkably stable FP8 training. V3 set the stage as an extremely efficient model that was already cost-efficient (with claims of being 90% more affordable than some closed-source alternatives).

DeepSeek R1-Zero:

With V3 as the base, the team then presented R1-Zero, the first reasoning-focused version. Here, the focus was on teaching the model not just to generate answers however to "think" before addressing. Using pure support knowing, the model was encouraged to create intermediate thinking actions, for instance, taking additional time (frequently 17+ seconds) to overcome a basic problem like "1 +1."

The key innovation here was the use of group relative policy optimization (GROP). Instead of counting on a traditional process benefit model (which would have required annotating every step of the reasoning), GROP compares numerous outputs from the design. By tasting a number of prospective responses and scoring them (utilizing rule-based measures like specific match for math or verifying code outputs), the system finds out to favor thinking that leads to the proper outcome without the need for explicit guidance of every intermediate thought.

DeepSeek R1:

Recognizing that R1-Zero's without supervision method produced thinking outputs that might be difficult to check out and even mix languages, the designers went back to the drawing board. They used the raw outputs from R1-Zero to generate "cold start" information and then by hand curated these examples to filter and improve the quality of the thinking. This human post-processing was then used to tweak the original DeepSeek V3 model further-combining both reasoning-oriented reinforcement knowing and supervised fine-tuning. The outcome is DeepSeek R1: a model that now produces legible, coherent, and dependable 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 established thinking capabilities without specific guidance of the thinking procedure. It can be even more improved by utilizing cold-start data and monitored support finding out to produce legible reasoning on basic jobs. Here's what sets it apart:

Open Source & Efficiency:

R1 is open source, permitting scientists and developers to check and develop upon its innovations. Its cost efficiency is a major selling point particularly when compared to closed-source models (claimed 90% more affordable than OpenAI) that require enormous calculate budget plans.

Novel Training Approach:

Instead of relying entirely on annotated reasoning (which is both expensive and time-consuming), the design was trained using an outcome-based approach. It began with easily proven jobs, such as mathematics issues and coding exercises, where the correctness of the final response might be quickly determined.

By utilizing group relative policy optimization, the training process compares multiple created responses to determine which ones fulfill the preferred output. This relative scoring mechanism permits the design to learn "how to think" even when intermediate reasoning is created in a freestyle manner.

Overthinking?

A fascinating observation is that DeepSeek R1 sometimes "overthinks" basic issues. For example, when asked "What is 1 +1?" it might spend nearly 17 seconds evaluating various scenarios-even considering binary representations-before concluding with the proper response. This self-questioning and verification procedure, although it may appear ineffective initially look, might prove beneficial in complex tasks where much deeper reasoning is essential.

Prompt Engineering:

Traditional few-shot prompting techniques, which have worked well for lots of chat-based designs, can really deteriorate efficiency with R1. The designers recommend using direct issue declarations with a zero-shot approach that specifies the output format plainly. This guarantees that the model isn't led astray by extraneous examples or hints that may hinder its internal thinking process.

Getting Started with R1

For those aiming to experiment:

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


Larger versions (600B) require substantial compute resources


Available through significant cloud service providers


Can be deployed locally via Ollama or vLLM


Looking Ahead

We're especially captivated by numerous ramifications:

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


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


Possibilities for integrating with other supervision strategies


Implications for business AI release


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

Open Questions

How will this affect the advancement of future reasoning designs?


Can this approach be reached less verifiable domains?


What are the ramifications for multi-modal AI systems?


We'll be viewing these advancements carefully, particularly as the community begins to try out and construct upon these techniques.

Resources

Join our Slack community for ongoing discussions and updates about DeepSeek and other AI developments. We're seeing interesting 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 model in the open-source community, the choice ultimately depends upon your use case. DeepSeek R1 stresses sophisticated reasoning and a novel training approach that might be specifically important in jobs where proven reasoning is critical.

Q2: Why did major companies like OpenAI opt for monitored fine-tuning rather than support knowing (RL) like DeepSeek?

A: We need to keep in mind upfront that they do utilize RL at the extremely least in the type of RLHF. It is likely that designs from major companies that have reasoning abilities already use something comparable 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 ready availability of big annotated datasets. Reinforcement knowing, although effective, can be less foreseeable and harder to control. DeepSeek's approach innovates by using RL in a reasoning-oriented way, making it possible for the design to discover efficient internal thinking with only minimal procedure annotation - a method that has proven promising regardless of its complexity.

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

A: DeepSeek R1's design stresses performance by leveraging methods such as the mixture-of-experts method, which activates just a subset of specifications, to minimize calculate during inference. This concentrate on effectiveness is main to its expense advantages.

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

A: R1-Zero is the initial model that finds out reasoning exclusively through reinforcement learning without explicit procedure guidance. It produces intermediate thinking steps that, while in some cases raw or combined in language, act as the structure for learning. DeepSeek R1, on the other hand, refines these outputs through human post-processing and monitored fine-tuning. In essence, R1-Zero provides the without supervision "trigger," and R1 is the sleek, more meaningful version.

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

A: Remaining current involves a mix of actively engaging with the research study neighborhood (like AISC - see link to sign up with slack above), following preprint servers like arXiv, participating in appropriate conferences and webinars, and taking part in conversation groups and newsletters. Continuous engagement with online communities and collective research jobs also plays a crucial role in staying up to date with technical advancements.

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

A: The brief response is that it's too early to tell. DeepSeek R1's strength, nevertheless, lies in its robust thinking abilities and its effectiveness. It is especially well fit for jobs that require verifiable logic-such as mathematical problem resolving, code generation, and structured decision-making-where intermediate thinking can be evaluated and verified. Its open-source nature further enables 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 design of DeepSeek R1 reduces the entry barrier for releasing sophisticated language designs. and start-ups can take advantage of its sophisticated reasoning for agentic applications ranging from automated code generation and client assistance to information analysis. Its flexible release options-on consumer hardware for smaller designs or cloud platforms for larger ones-make it an attractive option to proprietary options.

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

A: While DeepSeek R1 has actually been observed to "overthink" simple issues by exploring multiple thinking courses, it includes stopping criteria and examination mechanisms to avoid limitless loops. The reinforcement finding out framework 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 worked as the structure for later versions. It is built on its own set of innovations-including the mixture-of-experts technique and FP8 training-and is not based on the Qwen architecture. Its style stresses effectiveness and cost decrease, setting the stage for the reasoning innovations seen in R1.

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

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

Q11: Can professionals in specialized fields (for instance, labs working on treatments) use these approaches to train domain-specific models?

A: Yes. The innovations behind DeepSeek R1-such as its outcome-based reasoning training and efficient architecture-can be adapted to various domains. Researchers in fields like biomedical sciences can tailor these techniques to develop designs that resolve their particular challenges while gaining from lower compute expenses and robust thinking capabilities. It is most likely that in deeply specialized fields, however, there will still be a need for monitored fine-tuning to get reputable outcomes.

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

A: The discussion suggested that the annotators mainly concentrated on domains where accuracy is easily verifiable-such as math and coding. This recommends that competence in technical fields was certainly leveraged to make sure the accuracy and clearness of the reasoning information.

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

A: While the design is designed to optimize for correct answers via support knowing, there is always a threat of errors-especially in uncertain circumstances. However, by assessing numerous candidate outputs and enhancing those that lead to verifiable outcomes, the training process minimizes the likelihood of propagating incorrect thinking.

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

A: Using rule-based, proven jobs (such as mathematics and coding) helps anchor the design's thinking. By comparing several outputs and using group relative policy optimization to reinforce only those that yield the appropriate result, the model is directed away from generating unproven 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 strategies to enable effective thinking rather than 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 valid concern?

A: Early iterations like R1-Zero did produce raw and in some cases hard-to-read thinking. However, the subsequent improvement process-where human specialists curated and improved the reasoning data-has significantly boosted the clarity and reliability of DeepSeek R1's internal idea process. While it remains an evolving system, iterative training and feedback have led to significant enhancements.

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

A: For local screening, a medium-sized model-typically in the variety of 7B to 8B parameters-is advised. Larger designs (for example, those with numerous billions of specifications) need significantly more computational resources and are better suited for cloud-based release.

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

A: DeepSeek R1 is offered with open weights, photorum.eclat-mauve.fr meaning that its design parameters are publicly available. This aligns with the general open-source viewpoint, allowing scientists and developers to more check out and build on its innovations.

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

A: The existing method allows the model to first explore and produce its own reasoning patterns through not being watched RL, and then refine these patterns with supervised approaches. Reversing the order might constrain the design's capability to find varied reasoning paths, possibly restricting its total performance in tasks that gain from autonomous idea.

Thanks for checking out Deep Random Thoughts! Subscribe for complimentary to get brand-new posts and yewiki.org 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: cassandramoody/cooqie#15