Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • Y youtoonetwork
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 10
    • Issues 10
    • 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
  • Aleida Barkly
  • youtoonetwork
  • Issues
  • #10

Closed
Open
Created Jun 03, 2025 by Aleida Barkly@aleidabarkly21Maintainer

Understanding DeepSeek R1


We have actually been tracking the explosive increase of DeepSeek R1, which has actually taken the AI world by storm in recent weeks. In this session, we dove deep into the advancement of the DeepSeek family - from the early designs through DeepSeek V3 to the development R1. We likewise explored 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 just a single design; it's a household of progressively advanced AI systems. The development goes something like this:

DeepSeek V2:

This was the structure design which leveraged a mixture-of-experts architecture, where just a subset of professionals are used at inference, dramatically enhancing the processing time for each token. It also featured multi-head latent attention to minimize 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 precise way to store weights inside the LLMs but can greatly improve the memory footprint. However, training using FP8 can normally be unsteady, and it is difficult to obtain the preferred training results. Nevertheless, DeepSeek uses numerous tricks and attains extremely steady FP8 training. V3 set the stage as an extremely efficient model that was currently affordable (with claims of being 90% less expensive than some closed-source alternatives).

DeepSeek R1-Zero:

With V3 as the base, the group then presented R1-Zero, the first reasoning-focused model. Here, the focus was on teaching the model not just to create responses but to "think" before addressing. Using pure reinforcement knowing, the design was encouraged to create intermediate thinking actions, for instance, 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 relying on a standard procedure benefit model (which would have needed annotating every action of the thinking), GROP compares multiple outputs from the design. By sampling a number of potential responses and scoring them (utilizing rule-based measures like exact match for mathematics or verifying code outputs), the system discovers to favor thinking that causes the appropriate outcome without the requirement for specific supervision of every intermediate thought.

DeepSeek R1:

Recognizing that R1-Zero's without supervision approach produced reasoning outputs that might be tough to read or perhaps blend languages, the developers went back to the drawing board. They utilized the raw outputs from R1-Zero to generate "cold start" information and after that by hand curated these examples to filter and enhance the quality of the thinking. This human post-processing was then utilized to fine-tune the original DeepSeek V3 design further-combining both reasoning-oriented support knowing and supervised fine-tuning. The outcome is DeepSeek R1: a model that now produces readable, coherent, and trusted thinking while still maintaining the performance and cost-effectiveness of its predecessors.

What Makes R1 Series Special?

The most remarkable aspect of R1 (no) is how it developed reasoning capabilities without specific supervision of the reasoning procedure. It can be even more improved by utilizing cold-start information and supervised support learning to produce understandable thinking on general tasks. Here's what sets it apart:

Open Source & Efficiency:

R1 is open source, allowing researchers and developers to examine and construct upon its developments. Its expense efficiency is a major selling point particularly when compared to closed-source models (claimed 90% more affordable than OpenAI) that require massive compute budgets.

Novel Training Approach:

Instead of relying entirely on annotated thinking (which is both expensive and lengthy), the model was trained using an outcome-based technique. It began with easily verifiable jobs, such as mathematics problems and coding workouts, where the accuracy of the last response might be quickly measured.

By utilizing group relative policy optimization, the training process compares numerous produced responses to figure out which ones satisfy the desired output. This relative scoring system allows the model to discover "how to think" even when intermediate reasoning is produced in a freestyle way.

Overthinking?

An intriguing observation is that DeepSeek R1 sometimes "overthinks" easy issues. For instance, when asked "What is 1 +1?" it might invest nearly 17 seconds assessing different scenarios-even considering binary representations-before with the appropriate response. This self-questioning and confirmation process, although it may seem inefficient in the beginning look, could prove beneficial in intricate jobs where much deeper reasoning is essential.

Prompt Engineering:

Traditional few-shot prompting strategies, which have worked well for lots of chat-based designs, can really deteriorate efficiency with R1. The designers advise utilizing direct issue 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 may interfere with its internal reasoning process.

Getting Started with R1

For those aiming to experiment:

Smaller variants (7B-8B) can operate on consumer GPUs or perhaps only CPUs


Larger variations (600B) need substantial compute resources


Available through major cloud suppliers


Can be released in your area through Ollama or vLLM


Looking Ahead

We're particularly captivated by several ramifications:

The capacity for this method to be used to other reasoning domains


Influence on agent-based AI systems traditionally built on chat designs


Possibilities for combining with other guidance strategies


Implications for enterprise AI implementation


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

Open Questions

How will this affect the development of future thinking models?


Can this method be reached less verifiable domains?


What are the ramifications for multi-modal AI systems?


We'll be viewing these developments closely, especially as the neighborhood begins to explore and build on these strategies.

Resources

Join our Slack community for ongoing discussions 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 short summary


Cloud Providers:

Nvidia


Together.ai


AWS




Q&A

Q1: Which model deserves more attention - DeepSeek or Qwen2.5 Max?

A: While Qwen2.5 is likewise a strong design in the open-source community, the option ultimately depends upon your use case. DeepSeek R1 highlights sophisticated thinking and a novel training method that might be particularly valuable in jobs where verifiable logic is vital.

Q2: Why did major suppliers like OpenAI go with supervised fine-tuning rather than support knowing (RL) like DeepSeek?

A: We need to keep in mind in advance that they do use RL at the minimum in the form of RLHF. It is likely that designs from major suppliers that have thinking capabilities currently 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 preferred supervised fine-tuning due to its stability and the ready availability of large annotated datasets. Reinforcement learning, although effective, can be less foreseeable and more difficult to control. DeepSeek's approach innovates by applying RL in a reasoning-oriented way, making it possible for the design to discover efficient internal thinking with only minimal procedure annotation - a strategy that has shown appealing despite its intricacy.

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

A: DeepSeek R1's design emphasizes efficiency by leveraging strategies such as the mixture-of-experts technique, which activates only a subset of specifications, to minimize compute throughout reasoning. This concentrate on efficiency is main to its expense benefits.

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

A: R1-Zero is the initial design that finds out reasoning exclusively through support knowing without explicit procedure guidance. It generates intermediate thinking steps that, while often raw or blended in language, work as the foundation for knowing. DeepSeek R1, on the other hand, refines these outputs through human post-processing and monitored fine-tuning. In essence, R1-Zero provides the unsupervised "spark," and R1 is the polished, more coherent variation.

Q5: How can one remain updated with extensive, technical research study while managing a hectic schedule?

A: Remaining present includes a combination of actively engaging with the research community (like AISC - see link to join slack above), following preprint servers like arXiv, going to pertinent conferences and webinars, and getting involved in discussion groups and newsletters. Continuous engagement with online communities and collaborative research projects likewise plays a key function in staying up to date with technical advancements.

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

A: The short answer is that it's prematurely to inform. DeepSeek R1's strength, however, depends on its robust reasoning abilities and its efficiency. It is particularly well suited for jobs that need proven logic-such as mathematical problem solving, code generation, and structured decision-making-where intermediate reasoning can be reviewed and confirmed. Its open-source nature further permits tailored applications in research and business settings.

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

A: The open-source and affordable style of DeepSeek R1 lowers the entry barrier for releasing innovative language designs. Enterprises and start-ups can leverage its sophisticated reasoning for agentic applications varying from automated code generation and client assistance to information analysis. Its flexible deployment options-on consumer hardware for smaller designs or cloud platforms for larger ones-make it an appealing alternative to exclusive options.

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

A: While DeepSeek R1 has actually been observed to "overthink" simple issues by exploring numerous thinking courses, it incorporates stopping criteria and assessment systems to avoid limitless loops. The reinforcement finding out structure motivates convergence 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 method and FP8 training-and is not based upon the Qwen architecture. Its design stresses effectiveness and expense decrease, setting the phase for the reasoning innovations seen in R1.

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

A: DeepSeek R1 is a text-based model and does not include vision abilities. Its style and training focus entirely on language processing and reasoning.

Q11: Can experts in specialized fields (for example, laboratories dealing with treatments) use these methods 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 build models that address their particular obstacles while gaining from lower calculate expenses and robust reasoning abilities. It is most likely that in deeply specialized fields, however, there will still be a requirement for monitored fine-tuning to get trustworthy outcomes.

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

A: The discussion suggested that the annotators mainly concentrated on domains where correctness is quickly verifiable-such as math and coding. This recommends that know-how in technical fields was certainly leveraged to ensure the precision and clarity of the reasoning data.

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

A: While the model is developed to optimize for appropriate answers via reinforcement knowing, there is constantly a threat of errors-especially in uncertain situations. However, by examining several prospect outputs and reinforcing those that cause verifiable outcomes, the training process decreases the probability of propagating incorrect reasoning.

Q14: How are hallucinations lessened in the model given its iterative thinking loops?

A: Using rule-based, proven tasks (such as mathematics and coding) assists anchor the model's thinking. By comparing numerous outputs and using group relative policy optimization to enhance only those that yield the right result, the model is guided away from generating unproven or hallucinated details.

Q15: Does the design depend on complex vector mathematics?

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

Q16: Some stress that the model's "thinking" might not be as refined as human thinking. Is that a legitimate issue?

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

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

A: For local screening, a medium-sized model-typically in the series of 7B to 8B parameters-is advised. Larger designs (for example, those with hundreds of billions of criteria) require substantially 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: mediawiki.hcah.in DeepSeek R1 is offered with open weights, suggesting that its model criteria are openly available. This aligns with the overall open-source viewpoint, enabling scientists and designers to further explore and develop upon its innovations.

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

A: The current method permits the design to first explore and produce its own reasoning patterns through not being watched RL, and then fine-tune these patterns with monitored approaches. Reversing the order might constrain the model's ability to discover diverse reasoning courses, possibly restricting its overall performance in tasks that gain from autonomous thought.

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

Assignee
Assign to
Time tracking