Skip to content

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
    • Help
    • Contribute to GitLab
  • Sign in
S
stay-22
  • 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
  • Antwan Flanagan
  • stay-22
  • Issues
  • #15

Closed
Open
Opened 1 month ago by Antwan Flanagan@antwanflanagan
  • Report abuse
  • New issue
Report abuse New issue

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 family - from the early models through DeepSeek V3 to the development R1. We also checked out the technical innovations that make R1 so special on the planet of open-source AI.

The DeepSeek Family Tree: From V3 to R1

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

DeepSeek V2:

This was the foundation model which leveraged a mixture-of-experts architecture, where only a subset of experts are used at reasoning, the processing time for each token. It likewise featured multi-head hidden attention to reduce memory footprint.

DeepSeek V3:

This design introduced FP8 training techniques, which assisted drive down training expenses by over 42.5% compared to previous iterations. FP8 is a less precise way to keep weights inside the LLMs but can significantly improve the memory footprint. However, training using FP8 can generally be unsteady, and it is hard to obtain the desired training outcomes. Nevertheless, DeepSeek utilizes several techniques and attains extremely steady FP8 training. V3 set the phase as a highly efficient design that was currently affordable (with claims of being 90% cheaper than some closed-source alternatives).

DeepSeek R1-Zero:

With V3 as the base, the group then introduced R1-Zero, the first reasoning-focused version. Here, the focus was on teaching the model not just to generate responses but to "think" before addressing. Using pure reinforcement knowing, the model was motivated to create intermediate thinking steps, for example, taking additional time (frequently 17+ seconds) to resolve a simple problem like "1 +1."

The crucial innovation here was the usage of group relative policy optimization (GROP). Instead of depending on a traditional process reward model (which would have needed annotating every step of the thinking), GROP compares several outputs from the model. By sampling numerous possible responses and scoring them (utilizing rule-based steps like exact match for math or validating code outputs), the system finds out to prefer thinking that leads to the right result without the need for explicit guidance of every intermediate thought.

DeepSeek R1:

Recognizing that R1-Zero's without supervision approach produced thinking outputs that might be difficult to read and even blend languages, the developers went back to the drawing board. They utilized the raw outputs from R1-Zero to generate "cold start" data and after that by hand curated these examples to filter and improve the quality of the thinking. This human post-processing was then utilized to fine-tune the initial DeepSeek V3 design further-combining both reasoning-oriented reinforcement knowing and supervised fine-tuning. The result is DeepSeek R1: a design that now produces readable, meaningful, and reputable reasoning while still maintaining the performance and cost-effectiveness of its predecessors.

What Makes R1 Series Special?

The most interesting aspect of R1 (no) is how it developed reasoning abilities without specific guidance of the thinking process. It can be further improved by utilizing cold-start data and monitored reinforcement discovering to produce readable thinking on basic jobs. Here's what sets it apart:

Open Source & Efficiency:

R1 is open source, permitting scientists and designers to check and build on its innovations. Its expense performance is a significant selling point specifically when compared to closed-source models (claimed 90% more affordable than OpenAI) that need massive compute budget plans.

Novel Training Approach:

Instead of relying solely on annotated reasoning (which is both expensive and lengthy), the design was trained using an outcome-based method. It began with quickly proven jobs, such as math problems and coding workouts, where the correctness of the final response could be easily determined.

By using group relative policy optimization, the training procedure compares numerous created responses to identify which ones fulfill the preferred output. This relative scoring mechanism enables the design to discover "how to believe" even when intermediate thinking is generated in a freestyle way.

Overthinking?

A fascinating observation is that DeepSeek R1 often "overthinks" simple problems. For example, when asked "What is 1 +1?" it may spend nearly 17 seconds assessing various scenarios-even considering binary representations-before concluding with the proper answer. This self-questioning and wiki.dulovic.tech verification process, although it might seem inefficient in the beginning glimpse, might prove useful in complex tasks where much deeper thinking is needed.

Prompt Engineering:

Traditional few-shot triggering strategies, which have worked well for many chat-based models, can in fact deteriorate efficiency with R1. The developers advise utilizing direct problem statements 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 hinder its internal thinking procedure.

Beginning with R1

For those aiming to experiment:

Smaller versions (7B-8B) can work on consumer GPUs or perhaps just CPUs


Larger versions (600B) require significant compute resources


Available through significant cloud service providers


Can be deployed in your area via Ollama or vLLM


Looking Ahead

We're particularly intrigued by a number of implications:

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


Influence on agent-based AI systems generally developed on chat designs


Possibilities for integrating with other supervision strategies


Implications for business AI release


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

Open Questions

How will this affect the development of future thinking designs?


Can this approach be reached less verifiable domains?


What are the ramifications for multi-modal AI systems?


We'll be seeing these advancements closely, especially as the community starts to explore and develop upon these methods.

Resources

Join our Slack community for continuous discussions 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.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 model 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 option eventually depends on your use case. DeepSeek R1 stresses sophisticated reasoning and a novel training approach that might be specifically valuable in tasks where verifiable logic is important.

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

A: We must note upfront that they do utilize RL at least in the form of RLHF. It is most likely that models from major service providers that have thinking abilities already use something comparable to what DeepSeek has done here, but we can't make certain. It is also likely that due to access to more resources, they favored monitored fine-tuning due to its stability and the all set availability of large annotated datasets. Reinforcement knowing, although effective, can be less predictable and more difficult to control. DeepSeek's approach innovates by using RL in a reasoning-oriented way, allowing the design to learn reliable internal reasoning with only minimal process annotation - a strategy that has shown appealing in spite of its intricacy.

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

A: DeepSeek R1's design stresses efficiency by leveraging strategies such as the mixture-of-experts approach, which triggers just a subset of criteria, to reduce compute throughout reasoning. This concentrate on efficiency is main to its expense advantages.

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

A: R1-Zero is the preliminary design that finds out thinking exclusively through support learning without explicit procedure supervision. It creates intermediate thinking actions that, while often raw or surgiteams.com combined in language, work as the foundation for learning. DeepSeek R1, on the other hand, refines these outputs through human post-processing and supervised fine-tuning. In essence, R1-Zero supplies the not being watched "stimulate," and R1 is the sleek, more meaningful version.

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

A: Remaining existing involves a combination of actively engaging with the research neighborhood (like AISC - see link to join 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 likewise plays a key role in keeping up with technical advancements.

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

A: The short response is that it's too early to inform. DeepSeek R1's strength, however, depends on its robust reasoning capabilities and its performance. It is especially well matched for tasks that need verifiable logic-such as mathematical problem fixing, code generation, and wiki.snooze-hotelsoftware.de structured decision-making-where intermediate thinking can be evaluated and verified. Its open-source nature further allows for tailored applications in research study and business settings.

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

A: The open-source and cost-effective style of DeepSeek R1 decreases the entry barrier for releasing innovative language models. Enterprises and start-ups can take advantage of its sophisticated reasoning for agentic applications varying from automated code generation and consumer assistance to information analysis. Its flexible deployment options-on customer hardware for smaller designs or cloud platforms for bigger ones-make it an appealing alternative to proprietary options.

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

A: While DeepSeek R1 has been observed to "overthink" easy issues by checking out multiple reasoning paths, it incorporates stopping criteria and examination systems to prevent boundless loops. The support discovering structure motivates convergence toward a verifiable 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 structure for later versions. 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 highlights efficiency and cost decrease, setting the stage for the thinking developments seen in R1.

Q10: How does DeepSeek R1 perform on vision tasks?

A: DeepSeek R1 is a text-based model and does not integrate vision capabilities. Its design and training focus solely on language processing and reasoning.

Q11: Can professionals in specialized fields (for example, laboratories working on remedies) use these techniques to train domain-specific designs?

A: Yes. The innovations behind DeepSeek R1-such as its outcome-based reasoning training and efficient architecture-can be adapted to different domains. Researchers in fields like biomedical sciences can tailor these methods to construct models that resolve their specific challenges while gaining from lower calculate costs and robust reasoning abilities. It is most likely that in deeply specialized fields, however, there will still be a need for monitored fine-tuning to get reliable outcomes.

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

A: The discussion suggested that the annotators mainly concentrated on domains where accuracy is quickly verifiable-such as mathematics and coding. This suggests that proficiency in technical fields was certainly leveraged to guarantee the precision and clearness of the reasoning data.

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

A: While the design is designed to enhance for right answers by means of reinforcement knowing, there is always a danger of errors-especially in uncertain situations. However, by examining several prospect outputs and reinforcing those that result in proven results, the training procedure lessens the likelihood of propagating inaccurate reasoning.

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

A: The use of rule-based, verifiable tasks (such as mathematics and coding) assists anchor the design's reasoning. By comparing numerous outputs and using group relative policy optimization to enhance only those that yield the correct result, the design is guided away from generating unfounded or hallucinated details.

Q15: Does the design rely on complex vector mathematics?

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

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

A: Early models like R1-Zero did produce raw and sometimes hard-to-read thinking. However, the subsequent refinement process-where human experts curated and enhanced the thinking data-has considerably enhanced the clarity and dependability of DeepSeek R1's internal idea process. While it remains a developing system, iterative training and feedback have actually led to significant improvements.

Q17: Which design versions appropriate for regional deployment 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 advised. Larger models (for example, those with hundreds of billions of criteria) require substantially more computational resources and are better suited for cloud-based implementation.

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

A: DeepSeek R1 is offered with open weights, indicating that its design parameters are publicly available. This lines up with the general open-source viewpoint, permitting scientists and designers to more explore and develop upon its developments.

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

A: The present method permits the model to first explore and create its own reasoning patterns through not being watched RL, and then refine these patterns with supervised methods. Reversing the order may constrain the model's capability to find diverse thinking paths, possibly restricting its overall performance in jobs that gain from autonomous thought.

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

Please solve the reCAPTCHA

We want to be sure it is you, please confirm you are not a robot.

    Please register or sign in to reply
    Assignee
    Assign to
    None
    Milestone
    None
    Assign milestone
    None
    Time tracking
    No estimate or time spent
    None
    Due date
    No due date
    0
    Labels
    None
    Assign labels
    • View project labels
    Confidentiality
    Not confidential
    Lock issue
    Unlocked
    participants
    Reference: antwanflanagan/stay-22#15