Sample
Buse/82
Human rating uses the original dataset scale.
Scores
| Method | Score | Scale | Dataset rank (0–100) |
|---|---|---|---|
| Posnett | 0.746 | 0–1; higher is more readable | 79.8Δ 6.1 |
| Dorn | 0.568 | 0–1; higher is more readable | 45.5Δ 40.4 |
| Mi | 0.701 | 0–1; higher is more readable | 82.8Δ 3.0 |
| LLOC | 4 | Logical lines; fewer is more readable | 59.6Δ 26.3 |
| DeepSeek V4 Pro | 14.67 | 0–20; mean of three runs | 55.1Δ 30.8 |
| GPT-6.1 Sol | 18 | 0–20; mean of three runs | 84.8Δ 1.0 |
| BTTF | 0.641 | 0–1; higher is more readable | 82.8Δ 3.0 |
| Human | 4 | 1–5; original rating | 85.9 |
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. | 4.019 | −6.029 |
| Halstead volumeHow much symbolic information the code contains. It combines the total number of operators and values with the number of distinct ones. | 138.302 | −4.564 |
| Source linesThe number of non-empty source lines. | 7 | +2.8 |
Intercept 8.87 + feature contributions = 1.077 (log-odds).
Score = sigmoid(1.077) = 0.746.
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. | 60 | +1.124 |
| Comment layout (horizontal)How rapidly the visual pattern of comment characters changes from left to right. | 0 | −0.804 |
| Comment layout frequencyHow frequently the layout switches between lines containing only comments or whitespace and lines containing code. | 8 | +0.753 |
| Indentation frequencyHow rapidly indentation changes from line to line. | 1 | −0.703 |
| Identifier layout (vertical)How rapidly the visual pattern of identifier characters changes from top to bottom. | 6.951 | −0.313 |
| Number layout frequencyHow rapidly the number of numeric values per line changes through the code. | 7 | +0.26 |
| Operator visual areaThe share of the code’s visual area occupied by operators such as +, =, and *. | 0.109 | −0.113 |
Intercept 0.07 + feature contributions = 0.275 (log-odds).
Score = sigmoid(0.275) = 0.568.
| Score | 0.701 |
|---|
| Score | 4 |
|---|
Run 1
The code is clear and readable. It uses a simple early return for comparing data service IDs, which keeps nesting flat. The intent is evident: comparing two objects' fields to determine equality. Variables have descriptive names like 'country' and 'cmpCountry'. However, the snippet is incomplete and lacks surrounding context (e.g., method signature, class definition), preventing a higher score. The action granularity is good—one comparison per line and one variable assignment per line. Reading flow is natural: compare first field, return if unequal, then compare next field. The code is concise without being overly terse. Missing context and a slight ambiguity around the relationship between dataServiceId and cmpDataServiceId keep it from being exemplary.
Run 2
The code snippet is short and clear. It compares two values and returns false if they differ, then retrieves two country strings. The structure is logical, with flat nesting and one action per line. However, without additional context—such as surrounding method logic, variable declarations, or the purpose of the comparison—the intent is only partially visible. The use of `compareTo` instead of `equals` for string comparison may be intentional but is slightly less readable for simple equality checks. Overall, the code is concise and easy to follow but lacks surrounding context.
Run 3
The code snippet is incomplete and lacks necessary context, making a full evaluation difficult. The visible portion is relatively clean with reasonable structure, minimal nesting, and clear intent within a comparison method. It uses one action per line and follows a natural reading flow. However, several issues reduce readability: the variable names are slightly cryptic ('cmpDataServiceId' instead of 'compareDataServiceId'), there is no enclosing method signature or class context to clarify the overall purpose, and the early return pattern is only partially shown. The code appears to be part of a larger equality-checking method but truncates before the remaining logic is visible. Without the complete method and its surrounding code, the true readability and structure cannot be fully assessed, resulting in a moderate score.
Run 1
Code Structure: Logically organized, with an early mismatch check followed by country retrieval. Nesting: Minimal; the guard clause avoids deeper nesting. Clarity of intent: The comparison and variable names are understandable, although the surrounding purpose is unavailable and compareTo is less direct than an equality check. Code length: Concise, with no unnecessary statements. Action granularity: Each statement performs one action on its own line. Reading flow: Natural and sequential, with whitespace separating the comparison from the retrievals; minor spacing inconsistencies slightly reduce polish.
Run 2
Code Structure: Logically organized, with an early return followed by related country retrievals. Nesting: Flat and easy to scan, with only one conditional block. Clarity of intent: The service-ID comparison is clear, although compareTo is less direct than an equality check and the snippet does not show how the country values are used. Code length: Concise, with no unnecessary statements. Action granularity: Each statement performs one action. Reading flow: Natural progression from checking service IDs to obtaining country values; minor spacing inconsistencies and abbreviated comparison names slightly reduce readability.
Run 3
Code Structure: Logically organized into a comparison guard followed by country retrieval. Nesting: Minimal; the early return keeps the flow flat. Clarity of intent: The mismatch check and country assignments are understandable, though the abbreviated 'cmp' names and incomplete surrounding context limit clarity. Code length: Concise, with no unnecessary statements. Action granularity: Each line performs a single action. Reading flow: Natural and sequential, with whitespace separating the two steps; minor spacing inconsistency around 'if' slightly reduces polish.