Skip to content

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
    • Help
    • Support
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
K
karis
  • Project
    • Project
    • Details
    • Activity
    • Cycle Analytics
  • Issues 33
    • Issues 33
    • List
    • Boards
    • 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
  • Alejandro Gavin
  • karis
  • Issues
  • #5

Closed
Open
Opened Apr 04, 2025 by Alejandro Gavin@alejandrogavin
  • 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 current weeks. In this session, we dove deep into the advancement of the DeepSeek family - from the early models through DeepSeek V3 to the development R1. We likewise explored 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 model; it's a household of significantly advanced AI systems. The evolution goes something like this:

DeepSeek V2:

This was the structure design which leveraged a mixture-of-experts architecture, where only a subset of professionals are used at inference, significantly 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 models. FP8 is a less exact method to keep weights inside the LLMs however can significantly enhance the memory footprint. However, training utilizing FP8 can typically be unstable, and it is difficult to obtain the preferred training outcomes. Nevertheless, DeepSeek uses multiple tricks and attains extremely steady FP8 training. V3 set the stage as an extremely effective model that was currently cost-efficient (with claims of being 90% more affordable than some closed-source alternatives).

DeepSeek R1-Zero:

With V3 as the base, the group then introduced R1-Zero, the first reasoning-focused iteration. Here, the focus was on teaching the design not just to create responses however to "believe" before answering. Using pure reinforcement knowing, the design was encouraged to generate intermediate thinking actions, for instance, taking additional time (frequently 17+ seconds) to work through an easy issue like "1 +1."

The essential innovation here was the use of group relative policy optimization (GROP). Instead of relying on a standard process benefit design (which would have required annotating every step of the reasoning), GROP compares several outputs from the design. By sampling numerous potential answers and scoring them (using rule-based steps like exact match for math or verifying code outputs), the system discovers to prefer reasoning that results in the proper outcome without the requirement for specific supervision of every intermediate thought.

DeepSeek R1:

Recognizing that R1-Zero's unsupervised technique produced thinking outputs that could be difficult to read and even blend languages, the designers returned to the drawing board. They used 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 tweak the initial DeepSeek V3 model further-combining both reasoning-oriented support knowing and monitored fine-tuning. The outcome is DeepSeek R1: a model that now produces legible, coherent, and dependable reasoning while still maintaining the performance and cost-effectiveness of its predecessors.

What Makes R1 Series Special?

The most interesting aspect of R1 (absolutely no) is how it established reasoning abilities without specific supervision of the reasoning process. It can be further improved by utilizing cold-start information and supervised reinforcement discovering to produce readable reasoning on general jobs. Here's what sets it apart:

Open Source & Efficiency:

R1 is open source, allowing scientists and developers to examine and construct upon its innovations. Its expense effectiveness is a significant selling point specifically when compared to closed-source designs (claimed 90% more affordable than OpenAI) that need huge calculate budget plans.

Novel Training Approach:

Instead of relying solely on annotated thinking (which is both pricey and time-consuming), the model was trained using an outcome-based technique. It began with quickly proven tasks, such as math issues and coding workouts, where the correctness of the final response could be easily measured.

By using group relative policy optimization, the training process compares multiple produced answers to determine which ones satisfy the preferred output. This relative scoring system enables the design to find out "how to believe" even when intermediate thinking is generated in a freestyle way.

Overthinking?

A fascinating observation is that DeepSeek R1 often "overthinks" easy problems. For example, when asked "What is 1 +1?" it might invest nearly 17 seconds examining various scenarios-even considering binary representations-before concluding with the appropriate response. This self-questioning and confirmation procedure, although it might seem inefficient in the beginning glance, might show useful in complex jobs where deeper reasoning is necessary.

Prompt Engineering:

Traditional few-shot triggering methods, which have actually worked well for lots of chat-based designs, can in fact deteriorate performance with R1. The developers recommend utilizing direct problem declarations with a zero-shot technique that defines the output format plainly. This ensures that the design isn't led astray by extraneous examples or hints that might interfere with its internal thinking procedure.

Starting with R1

For those aiming to experiment:

Smaller variants (7B-8B) can operate on customer GPUs or even only CPUs


Larger versions (600B) require substantial compute resources


Available through major cloud service providers


Can be deployed locally through Ollama or vLLM


Looking Ahead

We're especially interested by numerous ramifications:

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


Impact on agent-based AI systems typically built on chat designs


Possibilities for combining with other guidance strategies


Implications for enterprise AI release


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

Open Questions

How will this affect the advancement of future thinking models?


Can this approach be reached less proven domains?


What are the implications for multi-modal AI systems?


We'll be seeing these developments carefully, particularly as the neighborhood starts to explore and build on these methods.

Resources

Join our Slack neighborhood for continuous discussions and updates about DeepSeek and other AI developments. We're seeing fascinating applications already emerging from our bootcamp participants 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 model should have more attention - DeepSeek or Qwen2.5 Max?

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

Q2: Why did significant service providers like OpenAI choose supervised fine-tuning rather than support knowing (RL) like DeepSeek?

A: We must keep in mind in advance that they do utilize RL at least in the type of RLHF. It is most likely that models from significant suppliers that have thinking capabilities currently utilize something comparable to what DeepSeek has done here, however we can't make certain. It is also 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 effective, can be less foreseeable and harder to manage. DeepSeek's technique innovates by using RL in a reasoning-oriented manner, allowing the model to learn efficient internal reasoning with only minimal procedure annotation - a technique that has proven promising in spite of its complexity.

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

A: DeepSeek R1's style stresses efficiency by leveraging strategies such as the mixture-of-experts method, which triggers only a subset of specifications, to minimize compute during inference. This concentrate on efficiency is main to its cost benefits.

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

A: R1-Zero is the initial model that finds out thinking solely through reinforcement learning without explicit procedure supervision. It generates intermediate thinking steps that, while often raw or blended in language, serve 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 offers the without supervision "trigger," and R1 is the sleek, more meaningful version.

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

A: Remaining present involves a mix of actively engaging with the research neighborhood (like AISC - see link to join slack above), following preprint servers like arXiv, participating in relevant conferences and webinars, and getting involved in discussion groups and newsletters. Continuous engagement with online neighborhoods and collaborative research projects also plays a key role in staying up to date with technical improvements.

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

A: The short answer is that it's prematurely to inform. DeepSeek R1's strength, however, lies in its robust reasoning capabilities and its performance. It is particularly well fit for tasks that need proven logic-such as mathematical issue solving, code generation, and structured decision-making-where intermediate reasoning can be evaluated and confirmed. Its open-source nature further enables for 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 releasing advanced language models. Enterprises and start-ups can utilize its sophisticated reasoning for agentic applications varying from automated code generation and customer assistance to information analysis. Its versatile release options-on consumer hardware for smaller sized designs or cloud platforms for larger ones-make it an attractive option to exclusive services.

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

A: While DeepSeek R1 has been observed to "overthink" simple problems by checking out multiple reasoning courses, it integrates stopping criteria and assessment mechanisms to avoid limitless loops. The reinforcement finding out framework encourages convergence towards a proven 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 iterations. It is constructed on its own set of innovations-including the mixture-of-experts method and FP8 training-and is not based on the Qwen architecture. Its design highlights efficiency and cost decrease, 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 incorporate vision capabilities. Its design and training focus solely on language processing and reasoning.

Q11: Can experts in specialized fields (for instance, laboratories dealing with remedies) use these techniques to train domain-specific models?

A: Yes. The developments behind DeepSeek R1-such as its outcome-based thinking training and effective architecture-can be adjusted to numerous domains. Researchers in fields like biomedical sciences can tailor these approaches to develop models that resolve their specific difficulties while gaining from lower compute expenses and robust reasoning abilities. It is most likely that in deeply specialized fields, nevertheless, there will still be a need for supervised fine-tuning to get trusted results.

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

A: The conversation showed that the annotators mainly concentrated on domains where accuracy is quickly verifiable-such as math and coding. This suggests that expertise in technical fields was certainly leveraged to guarantee the accuracy and clearness of the thinking data.

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

A: While the design is created to enhance for appropriate answers via support knowing, there is constantly a threat of errors-especially in uncertain scenarios. However, by evaluating numerous prospect outputs and reinforcing those that result in verifiable outcomes, the training procedure lessens the possibility of propagating incorrect reasoning.

Q14: How are hallucinations decreased in the design given its iterative reasoning loops?

A: The usage of rule-based, proven tasks (such as math and coding) assists anchor the model's reasoning. By comparing several outputs and using group relative policy optimization to strengthen only those that yield the appropriate result, the design is directed away from creating unfounded or .

Q15: Does the design count on complex vector mathematics?

A: Yes, advanced techniques-including complex vector math-are integral to the execution of mixture-of-experts and attention systems in DeepSeek R1. However, setiathome.berkeley.edu the main focus is on utilizing these methods to enable reliable thinking rather than showcasing mathematical complexity for its own sake.

Q16: Some fret that the model's "thinking" might not be as refined as human reasoning. Is that a valid concern?

A: Early versions like R1-Zero did produce raw and sometimes hard-to-read reasoning. However, the subsequent improvement process-where human experts curated and enhanced the thinking data-has considerably enhanced the clarity and reliability of DeepSeek R1's internal thought process. While it remains an evolving system, iterative training and feedback have actually resulted in meaningful improvements.

Q17: Which design variants are suitable for regional implementation 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 recommended. Larger designs (for instance, those with numerous billions of criteria) need significantly more computational resources and are better fit 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, implying that its model parameters are publicly available. This lines up with the overall open-source viewpoint, allowing researchers and developers to further check out and construct upon its innovations.

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

A: The present approach enables the model to first check out and produce its own reasoning patterns through not being watched RL, and then refine these patterns with monitored approaches. Reversing the order might constrain the model's ability to find varied thinking paths, possibly restricting its total efficiency in tasks that gain from autonomous idea.

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

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
0
Labels
None
Assign labels
  • View project labels
Reference: alejandrogavin/karis#5