Sample
Dorn/python/82
Human rating uses the original dataset scale.
Scores
| Method | Score | Scale | Dataset rank (0–100) |
|---|---|---|---|
| Posnett | 0 | 0–1; higher is more readable | 18.9Δ 69.6 |
| Dorn | 0.869 | 0–1; higher is more readable | 91.4Δ 2.8 |
| Mi | 0.674 | 0–1; higher is more readable | 76.9Δ 11.7 |
| LLOC | 6 | Logical lines; fewer is more readable | 72.8Δ 15.7 |
| DeepSeek V4 Pro | 17.67 | 0–20; mean of three runs | 97.1Δ 8.5 |
| GPT-6.1 Sol | 19 | 0–20; mean of three runs | 98.9Δ 10.3 |
| BTTF | 0.626 | 0–1; higher is more readable | 80.2Δ 8.4 |
| Human | 3.93 | 1–5; original rating | 88.6 |
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) |
|---|---|---|
| Halstead volumeHow much symbolic information the code contains. It combines the total number of operators and values with the number of distinct ones. | 1722.577 | −56.845 |
| Source linesThe number of non-empty source lines. | 50 | +20 |
| Byte entropyHow varied the bytes in the source text are. Repeated bytes give a lower value; a more even mixture gives a higher value. | 4.992 | −7.487 |
Intercept 8.87 + feature contributions = -35.462 (log-odds).
Score = sigmoid(-35.462) = 0.
Feature contributions
| Feature | Value | Contribution (log-odds) |
|---|---|---|
| Comment layout frequencyHow frequently the layout switches between lines containing only comments or whitespace and lines containing code. | 51 | −0.769 |
| Indentation frequencyHow rapidly indentation changes from line to line. | 42 | +0.716 |
| Operator visual areaThe share of the code’s visual area occupied by operators such as +, =, and *. | 0.045 | +0.508 |
| 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. | 76 | +0.446 |
| 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. | 49.961 | +0.289 |
| Comment layout (horizontal)How rapidly the visual pattern of comment characters changes from left to right. | 64.176 | +0.231 |
Intercept 0.07 + feature contributions = 1.888 (log-odds).
Score = sigmoid(1.888) = 0.869.
| Score | 0.674 |
|---|
| Score | 6 |
|---|
Run 1
The code is highly readable with a clear, flat structure. It defines two dictionary mappings for Russian localization, each followed by a concise explanatory docstring. The dictionaries are organized logically with consistent indentation and one key-value pair per line. This improves scannability and reduces nesting. The intent is explicit at both the file level and per-dictionary level. While the file is somewhat long due to the necessary key-value pairs, it is not unnecessarily verbose. Each line represents a single action or data mapping, and the overall flow—from module docstring to labels to bibliographic fields—is natural and predictable.
Run 2
The code is a straightforward language mapping module with clear purpose. It uses flat, consistent dictionary structures with one entry per line, aiding readability. The introductory comments clarify context and usage, and section-level docstrings explain each mapping's role. Minor readability drawbacks include slightly unusual indentation of the closing braces and some inconsistencies in alignment/indentation width, which could be streamlined. Overall, the code is highly readable due to its simplicity, logical organization, and minimal nesting.
Run 3
The code is highly readable due to its clear, logical structure and consistent formatting. It consists of two flat dictionaries with descriptive names, followed by explanatory docstrings. Each dictionary entry is on its own line, providing excellent action granularity and scanning ease. The mapping keys and values are straightforward, making the intent immediately clear. Nesting is nonexistent, and the code length is appropriate for the data. Comments at the top provide useful context without clutter. Minor deductions include slightly inconsistent indentation (6 spaces vs 4) and a missing trailing comma on the last dictionary entry, but these do not significantly impact readability.
Run 1
Code Structure: Two clearly separated dictionaries logically organize label translations and bibliographic field mappings. Nesting: Only a single dictionary level, making the code easy to scan. Clarity of intent: The module description, descriptive variable names, and mapping explanations clearly communicate purpose and direction. Code length: Concise for the required translation data, with no unnecessary logic. Action granularity: Each mapping occupies its own line, supporting easy inspection and editing. Reading flow: Consistent formatting and mostly alphabetical canonical keys provide a natural progression. Minor readability drawbacks include unconventional indentation, closing braces attached to the final entries, and explanatory strings placed after the dictionaries rather than before them.
Run 2
Code Structure: Two clearly separated dictionaries organize labels and bibliographic fields logically. Nesting: The code is flat, with only simple dictionary literals. Clarity of intent: The module description, descriptive variable names, and mapping explanations make its purpose explicit. Code length: The length is appropriate for the translation data; there is no unnecessary logic. Action granularity: Each mapping occupies its own line, making entries easy to scan. Reading flow: Introductory documentation followed by related mappings creates a natural progression. Minor readability drawbacks include unusual six-space indentation, closing braces placed beside the final entries, and explanatory strings appearing after rather than before the dictionaries.
Run 3
Code Structure: Two clearly separated dictionaries logically group labels and bibliographic fields. Nesting: Only a single level of dictionary entries, making the code easy to scan. Clarity of intent: Descriptive variable names, a module docstring, and mapping descriptions explain the purpose and direction of each translation. Code length: Appropriately concise for explicit translation tables, with no unnecessary logic. Action granularity: Each mapping occupies its own line, avoiding crowded statements. Reading flow: Consistent formatting and mostly alphabetical English label keys support natural reading. Minor readability drawbacks include unusual six-space indentation, closing braces on the final entry lines, and explanatory strings placed after assignments rather than preceding them as comments.