Sample
JetBrains/e37
Human rating uses the original dataset scale.
Scores
| Method | Score | Scale | Dataset rank (0–100) |
|---|---|---|---|
| Posnett | 0.013 | 0–1; higher is more readable | 89.8Δ 4.2 |
| Scalabrino | 0.603 | 0–1; higher is more readable | 44.1Δ 41.5 |
| Dorn | 0.343 | 0–1; higher is more readable | 23.7Δ 61.9 |
| Mi | 0.264 | 0–1; higher is more readable | 18.6Δ 66.9 |
| LLOC | 3 | Logical lines; fewer is more readable | 98.3Δ 12.7 |
| DeepSeek V4 Pro | 17.67 | 0–20; mean of three runs | 88.6Δ 3.0 |
| GPT-6.1 Sol | 19 | 0–20; mean of three runs | 96.2Δ 10.6 |
| BTTF | 0.596 | 0–1; higher is more readable | 88.1Δ 2.5 |
| Human | 0.93 | 0–1; original rating | 85.6 |
Views
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. | 285 | −9.405 |
| 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.669 | −7.003 |
| Source linesThe number of non-empty source lines. | 8 | +3.2 |
Intercept 8.87 + feature contributions = -4.338 (log-odds).
Score = sigmoid(-4.338) = 0.013.
| Score | 0.603 |
|---|
Feature contributions
| Feature | Value | Contribution (log-odds) |
|---|---|---|
| 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. | 8 | −0.46 |
| Identifier layout (vertical)How rapidly the visual pattern of identifier characters changes from top to bottom. | 6.86 | −0.314 |
| Number layout frequencyHow rapidly the number of numeric values per line changes through the code. | 8 | +0.237 |
| Operator visual areaThe share of the code’s visual area occupied by operators such as +, =, and *. | 0.119 | −0.213 |
| 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. | 84.625 | +0.081 |
Intercept 0.07 + feature contributions = -0.65 (log-odds).
Score = sigmoid(-0.65) = 0.343.
| Score | 0.264 |
|---|
| Score | 3 |
|---|
Run 1
The code is highly readable due to its clear structure, minimal nesting, and concise intent. It imports only the necessary class, defines a single-purpose class, and computes tau as 2*pi using straightforward BigDecimal operations. The use of printf with a high precision format string directly supports the intended output, and the action granularity is appropriate—each logical step occupies its own line. The main drawback is the hardcoded precision value (1000) and the reliance on computing tau rather than using a predefined constant, but these do not significantly impact readability.
Run 2
The code is mostly clear and concise with a straightforward purpose: calculating and printing Tau to 1000 decimal places. The structure is minimal and logically organized, with no nesting or excessive length. However, readability suffers slightly due to the use of `BigDecimal.valueOf(Math.PI)`, which relies on the `double` approximation of π rather than a more precise constant, potentially misleading the intent of high precision. Action granularity is reasonably one action per line, but the print formatting could be clearer if separated into a variable. Overall, the code is readable but leaves room for improvement in precision intent and separation of concerns.
Run 3
The code is extremely concise and clear with a single, well-defined purpose: computing and printing tau (2π) to 1000 decimal places. Structure is simple and logical, with no unnecessary classes or methods. Nesting is flat. Action granularity is excellent — one meaningful operation per line. Reading flow is natural: import, class declaration, main method, computation, output. The only minor readability concern is the hardcoded 1000-digit formatting, which reduces flexibility, but this is negligible given the task's specific requirements. Overall, the code is nearly ideal for its intended purpose.
Run 1
Code Structure: The import, class, and main method are logically organized. Nesting: Only the standard class and method nesting is present. Clarity of intent: The class and variable names clearly communicate that the code calculates and prints tau, though printing 1,000 decimal places implies precision not provided by Math.PI. Code length: The implementation is concise without unnecessary code. Action granularity: Calculation and output occupy separate statements; the chained calculation remains easy to understand. Reading flow: Execution proceeds naturally from computing tau to printing it.
Run 2
Code Structure: The import, class, and main method are logically organized. Nesting: Only the necessary class and method levels are present. Clarity of intent: The class and variable names clearly indicate calculating and printing tau, although printing 1,000 decimal places misleadingly suggests precision not provided by Math.PI. Code length: The implementation is concise without unnecessary code. Action granularity: Calculation and output are separated into distinct statements; the chained calculation remains easy to follow. Reading flow: The code progresses naturally from calculation to output, with consistent formatting.
Run 3
Code Structure: The import, class, and main method are logically organized. Nesting: Only the standard class and method nesting is present. Clarity of intent: The class and variable names clearly indicate computing and printing tau, although requesting 1,000 decimal places from a value based on Math.PI may misleadingly suggest higher precision. Code length: The implementation is concise without unnecessary statements. Action granularity: Computation and output are separated; the chained expression remains easy to follow. Reading flow: Execution proceeds naturally from calculating tau to printing it.