Sample
Dorn/cuda/96
Human rating uses the original dataset scale.
Scores
| Method | Score | Scale | Dataset rank (0–100) |
|---|---|---|---|
| Posnett | 0.991 | 0–1; higher is more readable | 96.4Δ 17.3 |
| Dorn | 0.902 | 0–1; higher is more readable | 94.7Δ 15.6 |
| Mi | 0.61 | 0–1; higher is more readable | 64.3Δ 14.8 |
| LLOC | 1 | Logical lines; fewer is more readable | 97.9Δ 18.8 |
| DeepSeek V4 Pro | 8 | 0–20; mean of three runs | 29.4Δ 49.7 |
| GPT-6.1 Sol | 13 | 0–20; mean of three runs | 30.6Δ 48.5 |
| BTTF | 0.855 | 0–1; higher is more readable | 98.9Δ 19.8 |
| Human | 3.73 | 1–5; original rating | 79.1 |
Views
Select the downloaded ZIP or its extracted folder. Files stay in your browser.
Loading feature diagnosis…
Source regions
Feature contributions
Feature contributions
| Feature | Value | Contribution (log-odds) |
|---|---|---|
| Byte entropyHow varied the bytes in the source text are. Repeated bytes give a lower value; a more even mixture gives a higher value. | 3.979 | −5.969 |
| Source linesThe number of non-empty source lines. | 10 | +4 |
| Halstead volumeHow much symbolic information the code contains. It combines the total number of operators and values with the number of distinct ones. | 65.729 | −2.169 |
Intercept 8.87 + feature contributions = 4.732 (log-odds).
Score = sigmoid(4.732) = 0.991.
Feature contributions
| Feature | Value | Contribution (log-odds) |
|---|---|---|
| Identifier layout (horizontal)How rapidly the visual pattern of identifier characters changes from left to right. It measures spatial frequency, not the meaning of the names. | 23 | +2.691 |
| Comment layout (horizontal)How rapidly the visual pattern of comment characters changes from left to right. | 0 | −0.804 |
| Indentation frequencyHow rapidly indentation changes from line to line. | 1 | −0.703 |
| Comment layout frequencyHow frequently the layout switches between lines containing only comments or whitespace and lines containing code. | 11 | +0.647 |
| Number layout frequencyHow rapidly the number of numeric values per line changes through the code. | 1 | +0.398 |
| Identifier layout (vertical)How rapidly the visual pattern of identifier characters changes from top to bottom. | 8.542 | −0.29 |
| Operator visual areaThe share of the code’s visual area occupied by operators such as +, =, and *. | 0.075 | +0.21 |
Intercept 0.07 + feature contributions = 2.218 (log-odds).
Score = sigmoid(2.218) = 0.902.
| Score | 0.61 |
|---|
| Score | 1 |
|---|
Run 1
The code appears to be a fragment of a list containing directory or module names. Its structure and intent are unclear without surrounding context, making it appear as a disorganized collection of strings. There is no visible logical organization, indentation is inconsistent (first line is indented while others are not), and the trailing comma suggests an incomplete or cut-off list. It is concise due to its fragmentary nature, but lack of context, comments, or surrounding code prevents understanding its purpose. Nesting is minimal due to its flat list form, and action granularity is one item per line, but the overall readability is severely compromised by incompleteness and missing contextual information. Without the larger code block, this snippet cannot be effectively evaluated as readable code.
Run 2
The code is a simple list of string literals, likely a list of directory names or documentation sections. It is highly readable due to its flat structure, clear intent, and concise formatting. Each item is on its own line, maintaining one action per line and natural reading flow. The alphabetical ordering suggests logical organization. There is no nesting, ambiguous variable naming, or unnecessary length. The only minor drawback is the lack of surrounding context (e.g., the variable name or list assignment), but within the given snippet, the code is nearly ideal for what it represents.
Run 3
The code is a fragment of a list literal, lacking any surrounding context or indentation. It contains only string elements, with no explanation of their purpose. The structure is flat, but the absence of a variable assignment or function makes the intent entirely ambiguous. There is no action granularity or reading flow to evaluate meaningfully. Code length is minimal, but the fragment is unusable as-is, making it unreadable in its current form.
Run 1
Code Structure: The entries form a simple, logically organized list, but the missing opening bracket or assignment makes the snippet incomplete. Nesting: There is no deep nesting. Clarity of intent: The names suggest documentation sections or directories, though the list's purpose is unclear without context. Code length: Concise, with no unnecessary code. Action granularity: Each entry occupies its own line, making individual values easy to identify. Reading flow: Consistent indentation, quoting, and commas support easy scanning, but the incomplete opening disrupts interpretation.
Run 2
Code Structure: The entries are consistently formatted as a list, but the missing opening bracket and surrounding context make the snippet incomplete. Nesting: Flat, with no nested logic. Clarity of intent: The strings suggest directory or documentation names, but no variable name or usage explains their purpose. Code length: Concise, with no obvious unnecessary content. Action granularity: Each item occupies its own line, making individual entries easy to scan. Reading flow: The uniform indentation and roughly alphabetical ordering are natural, though the unmatched closing bracket interrupts comprehension.
Run 3
Code Structure: The entries form a consistently organized list, but the missing opening bracket and surrounding context make the snippet incomplete. Nesting: The code is flat and easy to scan. Clarity of intent: The strings suggest directory or documentation names, but no variable name or usage explains their purpose. Code length: The snippet is concise, with no apparent unnecessary content. Action granularity: Each list entry occupies its own line, clearly separating items. Reading flow: Uniform indentation and punctuation support smooth reading, although the unmatched closing bracket interrupts comprehension.