anthropics/uplifting-biomolecular-modeling
Logical Components
An overview of source code logical components.

Logical Decomposition #1: PRIMARY

The decompositions is based on the folder structure at level 1 (relative to the source code root).

Bubble Chart | Tree Map
Component Sizes (Lines of Code)
The "primary" logical decomposition has 37 components.

common107055 LOC (14%) 448 files
openfold3_ob065523 LOC (9%) 363 files
opendde62091 LOC (8%) 190 files
openfold360367 LOC (8%) 352 files
protenix_v256811 LOC (7%) 242 files
pxdesign40117 LOC (5%) 176 files
af3_jax34714 LOC (4%) 198 files
esmfold233755 LOC (4%) 108 files
boltz226997 LOC (3%) 107 files
atlasfold26732 LOC (3%) 204 files
chai118482 LOC (2%) 152 files
caliby15650 LOC (2%) 53 files
rosettafold313346 LOC (1%) 63 files
mosaic12741 LOC (1%) 55 files
protenix_v112209 LOC (1%) 55 files
af3_torch12180 LOC (1%) 73 files
evo211219 LOC (1%) 78 files
ef2inv9442 LOC (1%) 49 files
colabfold9390 LOC (1%) 37 files
e19147 LOC (1%) 62 files
boltzgen8837 LOC (1%) 41 files
colabdesign8777 LOC (1%) 56 files
rfdiffusion17475 LOC (1%) 46 files
esmc6941 LOC (<1%) 46 files
rfdiffusion36852 LOC (<1%) 33 files
genie36792 LOC (<1%) 47 files
chrombpnet6646 LOC (<1%) 37 files
af2ig6447 LOC (<1%) 36 files
proteinmpnn4911 LOC (<1%) 26 files
progen24738 LOC (<1%) 36 files
flashzoi4677 LOC (<1%) 38 files
gpnstar3525 LOC (<1%) 19 files
enformer_deepmind2571 LOC (<1%) 19 files
complexa2515 LOC (<1%) 24 files
enformer2470 LOC (<1%) 21 files
borzoi2256 LOC (<1%) 20 files
esm_if11876 LOC (<1%) 26 files

scope details...
  • 3,636 files, 726,274 LOC (100.0% vs. main code).
About This Analysis

Logical decomposition is a representation of the organization of the main source code, where every and each file is put in exactly one logical component.

  • A software system can have one or more logical decompositions.
  • A logical decomposition can be defined in two ways in Sokrates.
  • First approach is based on the folders structure. Components are mapped to folders at defined folder depth relative to the source code root.
  • Second approach is based on explicit definition of each component. In such explicit definitions, components are explicitly named and their files are selected based on explicitly defined path and content filters.
  • A logical decomposition is considered invalid if a file is selected into two or more components. This constraint is introduced in order to facilitate measuring of dependencies among components.
  • Files not assigned to any component are put into a special "Unclassified" component.

2026-10-06 22:53