Source code
Official dataset source · Buse/5
Sample
Buse/5
Human rating uses the original dataset scale.
Scores
| Method | Score | Scale | Dataset rank (0–100) |
|---|---|---|---|
| Posnett | 0.705 | 0–1; higher is more readable | 74.7Δ 22.2 |
| Scalabrino | 0.878 | 0–1; higher is more readable | 87.9Δ 9.1 |
| Dorn | 0.763 | 0–1; higher is more readable | 73.7Δ 23.2 |
| Mi | 0.737 | 0–1; higher is more readable | 89.9Δ 7.1 |
| LLOC | 5 | Logical lines; fewer is more readable | 29.8Δ 67.2 |
| DeepSeek V4 Pro | 17.67 | 0–20; mean of three runs | 96.0Δ 1.0 |
| GPT-6.1 Sol | 18 | 0–20; mean of three runs | 84.8Δ 12.1 |
| BTTF | 0.602 | 0–1; higher is more readable | 73.7Δ 23.2 |
| Human | 4.19 | 1–5; original rating | 97.0 |
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.253 | −6.38 |
| Halstead volumeHow much symbolic information the code contains. It combines the total number of operators and values with the number of distinct ones. | 158.123 | −5.218 |
| Source linesThe number of non-empty source lines. | 9 | +3.6 |
Intercept 8.87 + feature contributions = 0.872 (log-odds).
Score = sigmoid(0.872) = 0.705.
| Score | 0.878 |
|---|
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. | 51 | +1.505 |
| 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. | 10 | +0.682 |
| Comment layout (horizontal)How rapidly the visual pattern of comment characters changes from left to right. | 25.8 | −0.388 |
| Identifier layout (vertical)How rapidly the visual pattern of identifier characters changes from top to bottom. | 8.673 | −0.289 |
| 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.094 | +0.028 |
Intercept 0.07 + feature contributions = 1.167 (log-odds).
Score = sigmoid(1.167) = 0.763.
| Score | 0.737 |
|---|
| Score | 5 |
|---|
Run 1
The code is well-structured and readable. It clearly defines a single-purpose method with a concise Javadoc comment. Nesting is minimal, with only a single conditional that is flat and easy to follow. Each action is on its own line, maintaining clear action granularity. The reading flow is natural: it first notifies the controller, then handles window state, and finally exits the application. The naming of methods and variables is intuitive, making the intent unambiguous. The method is concise with no redundant code, and the logic is straightforward to understand.
Run 2
The code is well-structured, with a clear Javadoc comment explaining intent. It has minimal nesting, uses a single if statement without an else, and each line performs one action. The method is concise and readable, with a natural reading flow. Minor improvements could include clarifying the `windowed` flag's purpose or handling the fullscreen exit more explicitly, but overall readability is high.
Run 3
The code is highly readable. It has a clear, single-purpose method with a descriptive name and JavaDoc comment. The structure is logical and flat with no nesting, and each action is on its own line. The intent is unambiguous: quit the application unconditionally, handle fullscreen cleanup if needed, then exit. The code is concise without being cryptic. Minor deductions: the boolean literal `true` in `quitGame(true)` lacks context unless you inspect the method signature, and the `if` block could be slightly clearer with a comment explaining why fullscreen is handled only when not windowed. Overall, it follows clean code practices and reads naturally.
Run 1
Code Structure: logically ordered shutdown steps, though the snippet lacks a closing method brace. Nesting: only one shallow conditional, making control flow easy to follow. Clarity of intent: the comment and quit() name clearly communicate immediate application exit; gd and the boolean argument true are less self-explanatory. Code length: concise, with no unnecessary statements. Action granularity: each statement performs a single action on its own line. Reading flow: naturally progresses from quitting the game to releasing fullscreen mode and terminating the application.
Run 2
Code Structure: logically sequences game shutdown, fullscreen cleanup, and process exit, but the missing closing brace makes the snippet incomplete. Nesting: shallow, with only one simple conditional. Clarity of intent: the method name and comment clearly communicate immediate quitting, though gd and the boolean argument true are less descriptive. Code length: concise, with no unnecessary statements. Action granularity: each statement performs one action on its own line. Reading flow: natural and easy to follow from shutdown preparation to final exit.
Run 3
Code Structure: logically ordered shutdown steps, although the method's closing brace is missing. Nesting: minimal, with a single straightforward conditional. Clarity of intent: the method name and comment clearly describe immediate application termination; however, gd and the boolean argument true are not self-explanatory. Code length: concise, with no unnecessary statements. Action granularity: each statement performs one distinct action. Reading flow: natural progression from quitting the game to releasing full-screen mode and exiting the application.