Skip to content

  • 项目
  • 群组
  • 代码片段
  • 帮助
    • 正在加载...
    • 帮助
    • 为 GitLab 提交贡献
  • 登录/注册
N
nextreal
  • 项目
    • 项目
    • 详情
    • 活动
    • 周期分析
  • 议题 19
    • 议题 19
    • 列表
    • 看板
    • 标记
    • 里程碑
  • 合并请求 0
    • 合并请求 0
  • CI / CD
    • CI / CD
    • 流水线
    • 作业
    • 计划
  • Wiki
    • Wiki
  • 代码片段
    • 代码片段
  • 成员
    • 成员
  • 折叠边栏
  • 活动
  • 创建新议题
  • 作业
  • 议题看板
  • Allan Dumolo
  • nextreal
  • Issues
  • #3

已关闭
未关闭
在 3月 01, 2025 由 Allan Dumolo@allandumolo109
  • 违规举报
  • 新建问题
举报违规 新建问题

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 evolution of the DeepSeek family - from the early models through DeepSeek V3 to the breakthrough R1. We likewise explored the technical developments that make R1 so special worldwide of open-source AI.

The DeepSeek Family Tree: From V3 to R1

DeepSeek isn't simply a single model; it's a household 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 just a subset of professionals are used at inference, significantly enhancing the processing time for each token. It also featured multi-head latent attention to lower memory footprint.

DeepSeek V3:

This model introduced FP8 training strategies, which helped drive down training expenses by over 42.5% compared to previous iterations. FP8 is a less precise way to save weights inside the LLMs however can considerably enhance the memory footprint. However, training using FP8 can usually be unsteady, and it is difficult to obtain the desired training outcomes. Nevertheless, DeepSeek utilizes multiple tricks and attains remarkably stable FP8 training. V3 set the phase as a highly effective design that was currently economical (with claims of being 90% cheaper than some closed-source options).

DeepSeek R1-Zero:

With V3 as the base, the group then introduced R1-Zero, the very first reasoning-focused version. Here, the focus was on teaching the model not just to generate answers however to "believe" before addressing. Using pure support knowing, the model was motivated to produce intermediate reasoning actions, for instance, taking additional time (typically 17+ seconds) to work through an easy issue like "1 +1."

The crucial development here was the use of group relative policy optimization (GROP). Instead of counting on a conventional procedure benefit design (which would have needed annotating every action of the thinking), GROP compares several outputs from the model. By tasting several possible answers and scoring them (utilizing rule-based procedures like precise match for mathematics or confirming code outputs), the system learns to favor reasoning that results in the right outcome without the need for explicit guidance of every intermediate idea.

DeepSeek R1:

Recognizing that R1-Zero's unsupervised approach produced thinking outputs that might be hard to read or even mix languages, the designers went back to the drawing board. They used the raw outputs from R1-Zero to create "cold start" information and after that manually curated these examples to filter and enhance the quality of the reasoning. This human post-processing was then utilized to tweak the initial DeepSeek V3 model further-combining both reasoning-oriented support learning and monitored fine-tuning. The result is DeepSeek R1: a model that now produces legible, coherent, and reputable thinking while still maintaining the effectiveness and cost-effectiveness of its predecessors.

What Makes R1 Series Special?

The most fascinating element of R1 (zero) is how it developed thinking capabilities without specific guidance of the reasoning procedure. It can be even more improved by utilizing cold-start information and supervised reinforcement learning to produce understandable reasoning on basic jobs. Here's what sets it apart:

Open Source & Efficiency:

R1 is open source, allowing scientists and designers to inspect and develop upon its innovations. Its expense effectiveness is a major selling point specifically when compared to closed-source models (claimed 90% cheaper than OpenAI) that require huge compute spending plans.

Novel Training Approach:

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

By using group relative policy optimization, the training process compares several produced responses to figure out which ones satisfy the preferred output. This relative scoring mechanism enables the model to discover "how to think" even when intermediate reasoning is created in a freestyle way.

Overthinking?

An intriguing observation is that DeepSeek R1 often "overthinks" easy issues. For example, when asked "What is 1 +1?" it may spend nearly 17 seconds evaluating various scenarios-even thinking about binary representations-before concluding with the correct answer. This self-questioning and verification procedure, although it may seem ineffective at first glimpse, could show useful in complex jobs where much deeper reasoning is essential.

Prompt Engineering:

Traditional few-shot triggering methods, which have actually worked well for many chat-based designs, can actually degrade efficiency with R1. The developers recommend using 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 reasoning process.

Getting Going with R1

For those aiming to experiment:

Smaller versions (7B-8B) can operate on customer GPUs or perhaps only CPUs


Larger variations (600B) require significant calculate resources


Available through major cloud companies


Can be released locally through Ollama or vLLM


Looking Ahead

We're especially intrigued by numerous implications:

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


Effect on agent-based AI systems typically built on chat models


Possibilities for integrating with other supervision techniques


Implications for enterprise AI deployment


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

Open Questions

How will this impact the advancement of future reasoning models?


Can this method be reached less proven domains?


What are the implications for multi-modal AI systems?


We'll be watching these advancements carefully, particularly as the neighborhood starts to experiment with and build on these techniques.

Resources

Join our Slack neighborhood for continuous discussions and updates about DeepSeek and other AI advancements. 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 short 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 model in the open-source community, the choice eventually depends on your use case. DeepSeek R1 emphasizes innovative reasoning and an unique training method that may be especially valuable in jobs where verifiable logic is vital.

Q2: Why did significant providers like OpenAI choose for monitored fine-tuning rather than reinforcement learning (RL) like DeepSeek?

A: We should keep in mind upfront that they do use RL at least in the type of RLHF. It is most likely that designs from major suppliers that have thinking abilities currently use something similar to what DeepSeek has done here, however 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 large annotated datasets. Reinforcement learning, although effective, can be less foreseeable and more difficult to manage. DeepSeek's technique innovates by using RL in a reasoning-oriented manner, allowing the design to discover efficient internal reasoning with only minimal process annotation - a technique that has shown promising in spite of its intricacy.

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

A: DeepSeek R1's style stresses effectiveness by leveraging strategies such as the mixture-of-experts technique, which activates only a subset of specifications, to decrease compute throughout reasoning. This focus on performance is main to its expense benefits.

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

A: R1-Zero is the initial design that discovers reasoning entirely through reinforcement knowing without specific procedure guidance. It produces intermediate thinking actions that, while in some cases raw or mixed in language, act as the foundation for learning. DeepSeek R1, on the other hand, fine-tunes these outputs through human post-processing and supervised fine-tuning. In essence, R1-Zero offers the without supervision "spark," and R1 is the refined, more coherent variation.

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

A: Remaining current includes 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 pertinent conferences and webinars, and taking part in discussion groups and newsletters. Continuous engagement with online communities and collaborative research study jobs likewise plays an essential function in staying up to date with technical developments.

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

A: The short answer is that it's prematurely to inform. R1's strength, however, lies in its robust thinking abilities and its efficiency. It is especially well fit for tasks that require verifiable logic-such as mathematical problem solving, code generation, and structured decision-making-where intermediate thinking can be evaluated and confirmed. Its open-source nature even more 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 cost-efficient design of DeepSeek R1 lowers the entry barrier for releasing innovative language designs. Enterprises and start-ups can leverage its advanced thinking for agentic applications ranging from automated code generation and client assistance to data analysis. Its flexible release options-on consumer hardware for smaller sized models or cloud platforms for bigger ones-make it an attractive option to exclusive services.

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

A: While DeepSeek R1 has actually been observed to "overthink" easy issues by checking out several thinking courses, it integrates stopping requirements and examination systems to avoid boundless loops. The reinforcement learning structure motivates merging toward a verifiable output, even in uncertain cases.

Q9: Is DeepSeek V3 completely open source, and is it based on the Qwen architecture?

A: Yes, DeepSeek V3 is open source and functioned as the foundation for later versions. It is developed on its own set of innovations-including the mixture-of-experts method and FP8 training-and is not based on the Qwen architecture. Its style emphasizes effectiveness and expense decrease, setting the phase 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 include vision capabilities. Its design and training focus entirely on language processing and reasoning.

Q11: Can experts in specialized fields (for example, gratisafhalen.be labs dealing with cures) use these methods to train domain-specific models?

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

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 recommends that proficiency in technical fields was certainly leveraged to ensure the precision and clarity of the reasoning information.

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

A: While the model is developed to optimize for correct answers via reinforcement learning, there is always a danger of errors-especially in uncertain circumstances. However, by assessing numerous prospect outputs and reinforcing those that cause proven results, the training process reduces the probability of propagating incorrect thinking.

Q14: How are hallucinations minimized in the design given its iterative reasoning 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 correct outcome, the design is assisted far from producing unproven or hallucinated details.

Q15: Does the design rely on complex vector mathematics?

A: Yes, advanced techniques-including complex vector math-are integral to the application of mixture-of-experts and attention systems in DeepSeek R1. However, the main focus is on using these strategies to allow effective thinking rather than showcasing mathematical intricacy for its own sake.

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

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 improved the reasoning data-has considerably enhanced the clarity and reliability of DeepSeek R1's internal thought procedure. While it remains a developing system, iterative training and feedback have actually caused significant improvements.

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

A: pipewiki.org For regional testing, a medium-sized model-typically in the variety of 7B to 8B parameters-is advised. Larger designs (for instance, those with numerous billions of criteria) need significantly more computational resources and are much better matched for cloud-based implementation.

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

A: DeepSeek R1 is provided with open weights, meaning that its model specifications are openly available. This aligns with the total open-source approach, permitting scientists and designers to additional explore and build upon its innovations.

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

A: The current method allows the design to initially explore and create its own reasoning patterns through without supervision RL, and after that refine these patterns with supervised methods. Reversing the order may constrain the design's capability to discover diverse reasoning courses, possibly restricting its general performance in jobs that gain from autonomous thought.

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

指派人
分配到
无
里程碑
无
分配里程碑
工时统计
无
截止日期
无截止日期
0
标记
无
指派标记
  • 查看项目标记
引用: allandumolo109/nextreal#3