Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • M messengerkivu
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 14
    • Issues 14
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Infrastructure Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Christine Crabtree
  • messengerkivu
  • Issues
  • #8

Closed
Open
Created Feb 16, 2025 by Christine Crabtree@christinecrabtMaintainer

Understanding DeepSeek R1


We have actually been tracking the explosive increase of DeepSeek R1, which has taken the AI world by storm in current weeks. In this session, we dove deep into the advancement of the DeepSeek household - from the early designs through DeepSeek V3 to the advancement R1. We also checked out the technical innovations that make R1 so unique in the world of open-source AI.

The DeepSeek Family Tree: From V3 to R1

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

DeepSeek V2:

This was the foundation design which leveraged a mixture-of-experts architecture, where only a subset of experts are utilized at inference, drastically improving the processing time for each token. It also included multi-head latent attention to minimize memory footprint.

DeepSeek V3:

This model presented FP8 training methods, which assisted drive down training costs by over 42.5% compared to previous versions. FP8 is a less accurate method to store weights inside the LLMs however can significantly enhance the memory footprint. However, training using FP8 can normally be unstable, and it is hard to obtain the wanted training results. Nevertheless, DeepSeek utilizes multiple tricks and attains remarkably steady FP8 training. V3 set the phase as a highly effective model that was already cost-effective (with claims of being 90% more affordable than some closed-source alternatives).

DeepSeek R1-Zero:

With V3 as the base, the team then introduced R1-Zero, the very first reasoning-focused version. Here, the focus was on teaching the model not just to produce answers but to "think" before responding to. Using pure support learning, the model was encouraged to generate intermediate thinking steps, for example, taking additional time (frequently 17+ seconds) to overcome a basic issue like "1 +1."

The crucial development here was the use of group relative policy optimization (GROP). Instead of counting on a conventional process benefit design (which would have required annotating every step of the reasoning), GROP compares numerous outputs from the design. By tasting a number of possible answers and scoring them (using rule-based steps like exact match for math or validating code outputs), the system finds out to prefer thinking that results in the appropriate result without the requirement for specific guidance of every intermediate thought.

DeepSeek R1:

Recognizing that R1-Zero's not being watched approach produced thinking outputs that might be difficult to check out or perhaps blend languages, the developers went back to the drawing board. They used the raw outputs from R1-Zero to generate "cold start" data and then manually curated these examples to filter and improve the quality of the reasoning. This human post-processing was then used to tweak 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 understandable, meaningful, and trustworthy reasoning while still maintaining the effectiveness and cost-effectiveness of its predecessors.

What Makes R1 Series Special?

The most fascinating element of R1 (absolutely no) is how it developed reasoning abilities without specific supervision of the thinking procedure. It can be further enhanced by utilizing cold-start data and monitored reinforcement finding out to produce legible thinking on basic tasks. Here's what sets it apart:

Open Source & Efficiency:

R1 is open source, allowing scientists and developers to check and develop upon its innovations. Its expense efficiency is a major selling point particularly when compared to closed-source designs (claimed 90% less expensive than OpenAI) that require enormous compute budget plans.

Novel Training Approach:

Instead of relying entirely on annotated reasoning (which is both costly and time-consuming), the design was trained using an outcome-based method. It began with quickly verifiable jobs, such as mathematics problems and coding exercises, where the correctness of the last answer might be easily measured.

By utilizing group relative policy optimization, the training process compares multiple produced answers to figure out which ones satisfy the preferred output. This relative scoring mechanism enables the model to learn "how to think" even when intermediate reasoning is generated in a freestyle way.

Overthinking?

A fascinating observation is that DeepSeek R1 sometimes "overthinks" simple problems. For example, when asked "What is 1 +1?" it may spend nearly 17 seconds evaluating different scenarios-even thinking about binary representations-before concluding with the appropriate answer. This self-questioning and confirmation process, although it may seem inefficient initially glimpse, could prove advantageous in complicated jobs where deeper thinking is needed.

Prompt Engineering:

Traditional few-shot triggering techniques, which have worked well for many chat-based models, can actually break down performance with R1. The designers suggest using direct issue declarations with a zero-shot technique that defines the output format plainly. This makes sure that the design isn't led astray by extraneous examples or tips that might hinder its internal reasoning procedure.

Starting with R1

For those aiming to experiment:

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


Larger variations (600B) require considerable calculate resources


Available through major cloud providers


Can be deployed in your area by means of Ollama or vLLM


Looking Ahead

We're especially intrigued by numerous implications:

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


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


Possibilities for combining with other supervision strategies


Implications for business AI implementation


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

Open Questions

How will this impact the advancement 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 seeing these developments closely, particularly as the neighborhood begins to experiment with and build on these strategies.

Resources

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

A: While Qwen2.5 is also a strong design in the open-source neighborhood, the option eventually depends on your use case. DeepSeek R1 highlights sophisticated thinking and an unique training method that might be particularly important in jobs where proven logic is critical.

Q2: Why did major suppliers like OpenAI choose supervised fine-tuning instead of support knowing (RL) like DeepSeek?

A: We need to keep in mind upfront that they do utilize RL at least in the type of RLHF. It is highly likely that designs from significant companies that have reasoning capabilities currently utilize 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, trademarketclassifieds.com they favored monitored fine-tuning due to its stability and the all set availability of big annotated datasets. Reinforcement knowing, although powerful, can be less foreseeable and more difficult to control. DeepSeek's approach innovates by applying RL in a reasoning-oriented way, allowing the design to learn effective internal thinking with only very little process annotation - a technique that has actually proven appealing despite its complexity.

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

A: DeepSeek R1's design emphasizes performance by leveraging methods such as the mixture-of-experts approach, which triggers only a subset of criteria, to decrease compute throughout reasoning. This concentrate on efficiency is main to its cost advantages.

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

A: R1-Zero is the initial model that discovers thinking solely through reinforcement knowing without explicit procedure guidance. It creates intermediate reasoning steps that, while often raw or mixed 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 unsupervised "trigger," and R1 is the sleek, more coherent version.

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

A: Remaining existing includes a mix of actively engaging with the research study community (like AISC - see link to join slack above), following preprint servers like arXiv, participating in relevant conferences and webinars, and taking part in conversation groups and newsletters. Continuous engagement with online neighborhoods and collaborative research study tasks likewise plays a crucial function in keeping up with technical developments.

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, nevertheless, lies in its robust thinking capabilities and its performance. It is particularly well matched for tasks that require verifiable logic-such as mathematical issue solving, code generation, and structured decision-making-where intermediate reasoning can be reviewed and validated. Its open-source nature further enables tailored applications in research and enterprise settings.

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

A: The open-source and cost-effective design of DeepSeek R1 decreases the entry barrier for deploying innovative language designs. Enterprises and start-ups can utilize its innovative thinking for agentic applications varying from automated code generation and customer support to data analysis. Its versatile release options-on customer hardware for smaller models 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 appropriate answer is found?

A: While DeepSeek R1 has been observed to "overthink" simple problems by exploring several reasoning courses, it incorporates stopping criteria and examination systems to avoid boundless loops. The reinforcement finding out structure encourages convergence toward 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 served as the structure for later models. It is developed on its own set of innovations-including the mixture-of-experts approach and FP8 training-and is not based on the Qwen architecture. Its style stresses efficiency and expense reduction, setting the stage for the thinking innovations seen in R1.

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

A: DeepSeek R1 is a text-based model and does not incorporate vision abilities. Its design and training focus entirely on language processing and thinking.

Q11: Can specialists in specialized fields (for example, laboratories working on cures) use these techniques to train domain-specific models?

A: Yes. The innovations behind DeepSeek R1-such as its outcome-based reasoning training and effective architecture-can be adjusted to different domains. Researchers in fields like biomedical sciences can tailor these methods to build designs that address their specific difficulties while gaining from lower calculate expenses and robust reasoning capabilities. It is likely that in deeply specialized fields, nevertheless, there will still be a need for supervised fine-tuning to get trustworthy outcomes.

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

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

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

A: While the design is developed to optimize for proper responses via reinforcement learning, there is constantly a threat of errors-especially in uncertain circumstances. However, by examining several and reinforcing those that cause verifiable outcomes, the training procedure reduces the likelihood of propagating inaccurate thinking.

Q14: How are hallucinations decreased in the model provided its iterative reasoning loops?

A: Making use of rule-based, proven jobs (such as mathematics and coding) helps anchor the model's thinking. By comparing multiple outputs and using group relative policy optimization to enhance just those that yield the correct result, the model is guided away from producing unproven or hallucinated details.

Q15: Does the design count on complex vector mathematics?

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

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

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 improved the reasoning data-has considerably boosted the clarity and reliability of DeepSeek R1's internal idea process. While it remains a developing system, iterative training and feedback have actually led to meaningful enhancements.

Q17: Which model versions are ideal for regional deployment on a laptop computer 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 instance, those with hundreds of billions of criteria) need substantially more computational resources and are much better matched for cloud-based deployment.

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

A: DeepSeek R1 is provided with open weights, indicating that its model criteria are openly available. This aligns with the overall open-source philosophy, allowing researchers and developers to further check out and develop upon its developments.

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

A: The existing method enables the design to initially check out and produce its own thinking patterns through without supervision RL, and after that fine-tune these patterns with supervised techniques. Reversing the order might constrain the model's ability to find diverse reasoning courses, potentially limiting its overall performance in tasks that gain from autonomous thought.

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

Assignee
Assign to
Time tracking