Powered by OpenAIRE graph
Found an issue? Give us feedback
image/svg+xml art designer at PLoS, modified by Wikipedia users Nina, Beao, JakobVoss, and AnonMoos Open Access logo, converted into svg, designed by PLoS. This version with transparent background. http://commons.wikimedia.org/wiki/File:Open_Access_logo_PLoS_white.svg art designer at PLoS, modified by Wikipedia users Nina, Beao, JakobVoss, and AnonMoos http://www.plos.org/ ZENODOarrow_drop_down
image/svg+xml art designer at PLoS, modified by Wikipedia users Nina, Beao, JakobVoss, and AnonMoos Open Access logo, converted into svg, designed by PLoS. This version with transparent background. http://commons.wikimedia.org/wiki/File:Open_Access_logo_PLoS_white.svg art designer at PLoS, modified by Wikipedia users Nina, Beao, JakobVoss, and AnonMoos http://www.plos.org/
ZENODO
Report
Data sources: ZENODO
addClaim

DeepSeek R1 Memory Footprint in High- and Low-Complexity Code Vulnerability Analysis

Authors: Assignee Research;

DeepSeek R1 Memory Footprint in High- and Low-Complexity Code Vulnerability Analysis

Abstract

This report synthesises findings from 12 peer-reviewed papers addressing the following research question: How does the memory footprint of Deepseek R1 during vulnerability analysis compare between high-complexity and low-complexity code samples in standardized evaluations. 8 claims were extracted from source literature; 7 were independently verified against retrieved documents. An automated multi-reviewer quality assessment produced a score of 7.9/10. This report is a machine-generated literature synthesis and does not constitute original research.Research goal: How does the memory footprint of Deepseek R1 during vulnerability analysis compare between high-complexity and low-complexity code samples in standardized evaluations?Autonomous literature synthesis. Automated review score: 7.9/10. Full text and citation available at Assignee Research.

Powered by OpenAIRE graph
Found an issue? Give us feedback