File Complexity Overall
  • There are 54 files with units, with 9,494 lines of code.
    • 0 very complex files (McCabe index sum 251+; 0 lines of code)
    • 1 complex files (McCabe index sum 126-250; 507 lines of code)
    • 4 medium complex files (McCabe index sum 51-125; 1,976 lines of code)
    • 8 slightly complex files (McCabe index sum 26-50; 1,842 lines of code)
    • 41 simple files (McCabe index sum 1-25; 5,169 lines of code)
  • 14 main files have no units (e.g. languages without unit analysis, or files without functions) and are not classified.
system0% | 5% | 20% | 19% | 54%
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% | 5% | 20% | 19% | 54%
File Complexity per Logical Decomposition
primary
251+
126-250
51-125
26-50
1-25
shap_e0% | 5% | 20% | 19% | 54%
Most Complex Files (Top 50)

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
blender_script.py
in shap_e/rendering/blender
507 31 133 26 18
gaussian_diffusion.py
in shap_e/diffusion
755 44 91 12 16
ops.py
in shap_e/models/nn
315 32 61 19 9
channels_encoder.py
in shap_e/models/transmitter
776 36 57 7 5
meta.py
in shap_e/models/nn
130 16 51 39 6
collections.py
in shap_e/util
94 11 40 43 9
point_cloud.py
in shap_e/rendering
141 12 39 28 11
k_diffusion.py
in shap_e/diffusion
242 22 36 15 5
configs.py
in shap_e/models
153 1 32 21 32
pointnet2_utils.py
in shap_e/models/nn
222 14 31 14 5
encoding.py
in shap_e/models/nn
398 15 30 8 8
transformer.py
in shap_e/models/generation
398 26 30 8 3
pretrained_clip.py
in shap_e/models/generation
194 19 29 15 4
bottleneck.py
in shap_e/models/transmitter
97 17 24 25 4
pc_encoder.py
in shap_e/models/transmitter
339 16 24 7 4
mesh.py
in shap_e/rendering
78 5 24 31 7
view_data.py
in shap_e/rendering
100 19 21 21 2
ray.py
in shap_e/models/nerf
233 15 20 9 3
params_proj.py
in shap_e/models/transmitter
174 13 19 11 3
base.py
in shap_e/models/transmitter
151 19 19 13 1
renderer.py
in shap_e/models/stf
421 14 19 5 4
pytorch3d_util.py
in shap_e/rendering
208 10 19 9 8
image_util.py
in shap_e/util
116 11 17 15 6
data_util.py
in shap_e/util
222 7 15 7 7
camera.py
in shap_e/models/nn
129 13 15 12 2
renderer.py
in shap_e/models
136 9 15 11 6
view_data.py
in shap_e/rendering/blender
66 5 15 23 8
checkpoint.py
in shap_e/models/nn
90 5 12 13 5
types.py
in shap_e/rendering/raycast
66 5 12 18 4
volume.py
in shap_e/models
137 11 11 8 1
perceiver.py
in shap_e/models/generation
212 10 11 5 2
render.py
in shap_e/rendering/blender
127 4 11 9 6
download.py
in shap_e/models
119 7 10 8 3
mlp.py
in shap_e/models/nerstf
151 7 9 6 2
multiview_encoder.py
in shap_e/models/transmitter
168 5 9 5 4
mlp.py
in shap_e/models/stf
160 8 8 5 1
model.py
in shap_e/models/nerf
193 7 7 4 1
pooled_mlp.py
in shap_e/models/generation
63 5 7 11 3
mc.py
in shap_e/rendering
181 3 7 4 5
io.py
in shap_e/util
28 2 6 21 4
renderer.py
in shap_e/models/nerstf
238 6 6 3 1
notebooks.py
in shap_e/util
76 4 5 7 2
query.py
in shap_e/models
23 2 5 22 4
torch_mesh.py
in shap_e/rendering
25 1 5 20 5
cast.py
in shap_e/rendering/raycast
104 4 5 5 2
renderer.py
in shap_e/models/nerf
264 4 4 2 1
utils.py
in shap_e/models/nn
16 3 4 25 2
latent_diffusion.py
in shap_e/models/generation
27 2 3 11 2
sample.py
in shap_e/diffusion
78 3 3 4 1
util.py
in shap_e/models/generation
12 1 2 17 2
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...