deepseek-ai/DeepSeek-Math
File Complexity*
The distribution of files by complexity: the sum of the McCabe indexes of their units.
File Complexity Overall
  • There are 29 files with units, with 3,051 lines of code.
    • 0 very complex files (McCabe index sum 251+; 0 lines of code)
    • 0 complex files (McCabe index sum 126-250; 0 lines of code)
    • 6 medium complex files (McCabe index sum 51-125; 1,375 lines of code)
    • 6 slightly complex files (McCabe index sum 26-50; 1,072 lines of code)
    • 17 simple files (McCabe index sum 1-25; 604 lines of code)
  • 6 main files have no units (e.g. languages without unit analysis, or files without functions) and are not classified.
system0% | 0% | 45% | 35% | 19%
Legend:
251+
126-250
51-125
26-50
1-25


explore: grouped by folders | grouped by complexity
File Complexity per Extension
251+
126-250
51-125
26-50
1-25
py0% | 0% | 45% | 35% | 19%
File Complexity per Logical Decomposition
primary
251+
126-250
51-125
26-50
1-25
evaluation0% | 0% | 47% | 36% | 15%
replicate0% | 0% | 0% | 0% | 100%
Most Complex Files (Top 29)

The McCabe index of a file grows with its size: per 100 lines tells a large but plain file from a dense one, and most complex unit whether the complexity sits in one unit or is spread over many.

File# lines# unitsMcCabe index
(sum)		per 100
lines		most complex
unit
eval_utils.py
in evaluation/eval
 262 12 112 43 51
run_tool_integrated_eval.py
in evaluation/infer
 290 5 91 31 46
answer_extraction.py
in evaluation/data_processing
 250 19 84 34 12
utils.py
in evaluation/eval
 215 6 71 33 22
eval_script.py
in evaluation/eval
 154 9 62 40 16
run_cot_eval.py
in evaluation/infer
 204 3 53 26 26
run_pal_eval.py
in evaluation/infer
 216 2 50 23 45
170 3 49 29 26
ocwcourses_eval_utils.py
in evaluation/eval
 204 11 39 19 7
100 5 32 32 17
231 12 31 13 6
python_executor.py
in evaluation/eval
 151 10 29 19 10
process_utils.py
in evaluation/data_processing
 157 11 17 11 3
pal_gsm_8_shot.py
in evaluation/few_shot_prompts
 92 11 12 13 2
utils.py
in evaluation
 27 3 9 33 4
submit_eval_jobs.py
in evaluation
 61 1 5 8 5
minif2f_isabelle.py
in evaluation/few_shot_prompts
 19 3 4 21 2
cot_mmlu_stem_4_shot.py
in evaluation/few_shot_prompts
 10 3 3 30 1
cot_gaokao_mathqa_5_shot.py
in evaluation/few_shot_prompts
 11 3 3 27 1
pal_math_4_shot.py
in evaluation/few_shot_prompts
 10 3 3 30 1
cot_ocwcourses_4_shot.py
in evaluation/few_shot_prompts
 13 3 3 23 1
cot_gaokao_mathcloze_5_shot.py
in evaluation/few_shot_prompts
 11 3 3 27 1
cot_minerva_math_4_shot.py
in evaluation/few_shot_prompts
 10 3 3 30 1
cot_math_sat_4_shot.py
in evaluation/few_shot_prompts
 11 3 3 27 1
few_shot_prompting.py
in evaluation/few_shot_prompts
 7 3 3 43 1
cot_gsm_8_shot.py
in evaluation/few_shot_prompts
 11 3 3 27 1
cot_cmath_6_shot.py
in evaluation/few_shot_prompts
 11 3 3 27 1
predict.py
in replicate
 70 2 2 3 1
73 2 2 3 1
About This Analysis
  • File complexity is the sum of the McCabe indexes (conditional complexity) of the units (methods, functions...) in a file.
  • Files are classified in five categories based on that sum: 1-25 (simple files), 26-50 (slightly complex files), 51-125 (medium complex files), 126-250 (complex files), 251+ (very complex files). The default bands are five times the unit complexity bands, as a file is a group of units.
  • Only main code files with units are classified. Files without units (languages without unit analysis, or files without functions) have no complexity to measure and are left out rather than counted as simple.
  • A very complex file holds many decisions, which often means it has too many responsibilities: a candidate to split, and a place where changes need more testing.
Learn more...