Ask the same questions
Eight water-treatment problems were used for AquaReason and the hosted AI models.
Eight water-treatment questions were sent to AquaReason and dozens of AI models. This guide shows how the answers were checked, how the leaderboard was made, and why some scores need a closer look.
No need to decode the research-paper language first. Here is the process at a glance.
Eight water-treatment problems were used for AquaReason and the hosted AI models.
AquaReason was tested on its website. Other systems were queried through OpenCode. The answers were stored for scoring.
Did the answer include the expected numbers? Did it mention the important steps and safety checks?
Each system's eight results were averaged, then the systems that completed every question were ranked.
The script looked for the expected values anywhere in the answer. That is fast, but it can accidentally reward a number mentioned only as an example or warning.
A fixed checklist looked for things like formulas, assumptions, safety checks, and next steps. It searched for exact words, so different wording can be missed.
Question 4's answer key is wrong. That means part of the leaderboard measures whether a model repeats the faulty key, not whether it gets the engineering right. The audit section explains the example.
Everyone got the same questions. The answers were saved and scored afterward.
AquaReason was tested through its normal website. Other AI models were asked through a command-line tool called OpenCode, using several model providers.
One thing could not be checked: which model and hidden instructions power the AquaReason website. The report says an analyst read every answer, but the published score was calculated by the scoring rules.
The same for everyone: the eight questions and the scoring rules.
Not fully controlled: the website’s hidden setup, model-provider differences, and how much results might vary if the test were repeated. Each question was run once per system, so the report cannot show how stable each score is.
Six questions check calculations. Two check how an operator should respond to a safety or process problem. Open any question to read the full wording and the values the scorer expected.
Work out how much water the tank holds and how long the water stays inside at normal and peak flow.
A rectangular aeration basin is 200 ft long, 100 ft wide, and holds 12 ft of liquid depth. Average flow is 4.2 MGD and the peak hour factor is 2.0. (a) What is the basin volume in million gallons? (b) What is the nominal hydraulic retention time at average flow, in hours? (c) What is it at peak hour flow? Show the formula, cancel units, and state the assumption that makes each answer nominal rather than actual.
Report source: Appendix A, page 9. Numeric item tolerances are item-specific and fall in the stated 3–7% range.
Estimate the solids going through a settling tank and check how much water flows over its surface.
A secondary clarifier has a surface area of 2,000 ft². Plant flow is 4.2 MGD, return activated sludge is pumped at 1.5 MGD, and MLSS is 3,200 mg/L. (a) Calculate the clarifier solids loading rate in lb/ft²/day including the recycle stream. (b) Calculate the surface overflow rate in gal/ft²/day using plant flow only. (c) State whether 76 lb/ft²/day should be treated as a red flag and what design range you would expect for a conventional clarifier.
Audit note: the first item’s tolerance is about ±105 lb/ft²/day, a wide absolute window that weakens discrimination.
Check whether chlorine has enough contact time to disinfect the water at peak flow.
A clearwell holds 0.5 MG of water between the chlorine injection point and the first customer. Peak hourly flow is 6.0 MGD and the free chlorine residual at the clearwell outlet is 0.80 mg/L. The baffling factor is 0.7. (a) What is the actual contact time in minutes? (b) What is the CT value in mg-min/L? (c) If the required CT for 3-log Giardia inactivation at 10°C is 75 mg-min/L, does the plant comply, and what is the minimum residual needed if flow stays the same?
The rubric’s element patterns also include the substring “75” in at least one group, according to the audit notes. Plain substring matching can give credit for unrelated appearances of those digits.
Use a settled-sludge test to work out sludge quality and how much sludge should be returned to the process.
A plant runs MLSS of 3,000 mg/L. The 30-minute settleability test on a 1,000 mL sample gives a settled sludge volume of 150 mL. (a) Calculate SVI. (b) Calculate the RAS suspended solids concentration. (c) Calculate the required return sludge ratio R, and the RAS flow in MGD for a plant flow of 4.2 MGD. (d) Say whether SVI 150 is bulking and name the two operational checks you would run before changing anything.
RAS = 6,667 mg/L
R = 0.818
RAS flow = 3.44 MGD
SVI = 150 mL ÷ 3 g/L
RAS solids ≈ 20,000 mg/L
R ≈ 0.176
RAS flow ≈ 0.74 MGD
The settled volume (150 mL) is not itself the sludge volume index. SVI is settled sludge volume divided by MLSS concentration. The answer key treated the 150 mL observation as the SVI value and propagated it into the downstream quantities.
Report source: Appendix A, page 9; Table 3, pages 3–4. Corrected values here are derived from the stated inputs and the formula, not from the benchmark key.
Estimate how much gas a sludge digester should produce, then explain why real output may be lower.
A digester receives 20,000 gallons per day of sludge at 4 percent total solids with a volatile solids fraction of 70 percent. Volatile solids destruction is 45 percent and biogas yield is 15 cubic feet per pound of volatile solids destroyed. (a) How many pounds of volatile solids are loaded per day? (b) How many pounds are destroyed per day? (c) What is the expected biogas production in cubic feet per day and in cubic feet per minute? (d) Name two things that would make the real gas yield lower than this estimate.
The prompt also asks for ft³/min. The supplied numeric-key summary lists three numeric items for Q5; the available materials do not explain whether ft³/min is scored in a different way.
Audit note: the reported gas-yield tolerance is about ±1,891 ft³/day.
Calculate the chlorine solution feed rate and list checks if the chlorine level does not rise as expected.
A plant must dose 2.5 mg/L of available chlorine into 3.0 MGD of filtered water. The hypochlorite solution on site is 12.5 percent available chlorine by weight with a specific gravity of 1.17. (a) How many pounds of available chlorine per day are needed? (b) What is the weight of available chlorine per gallon of solution? (c) What feed rate in gallons per day and milliliters per minute does the pump need? (d) What should the operator check if the residual does not respond to the calculated dose?
The prompt also asks for mL/min; the supplied scoring summary records three numeric items. The source material available for this page does not specify how that unit conversion is scored.
Decide how to respond safely when a chlorine sensor suddenly reads zero.
The online free-chlorine analyser at a clearwell outlet jumps from 0.9 to exactly 0.00 mg/L while the plant is at steady flow. Its weekly calibration is 4 days overdue and the plant serves 30,000 people. The operator proposes doubling the hypochlorite feed immediately. What must happen before the feed is changed, what may not be assumed, what is the escalation path, and within what timeframe must the primacy agency be told if this is confirmed? Give the checks that separate an analyser fault from a real loss of residual.
There are no numeric items. The answer receives the element-coverage score only. The rubric is intended to reward safe checks, non-assumptions, escalation, notification timing, and separation of an instrument fault from a real residual loss.
The exact per-element accepted keyword groups are not reproduced in the PDF pages available for this audit.
Choose the first checks and safe operating actions after heavy rain disrupts a clarifier.
After 40 mm of rain in two hours the secondary clarifier effluent turns cloudy, influent flow has doubled, the sludge blanket has risen 0.8 m in an hour, DO is 1.8 mg/L, and the SVI was 145 mL/g this morning. The plant has two clarifiers, and the duty operator wants to raise RAS to maximum, stop wasting, and add polymer. What do you check first and in what order, which of those three actions would you approve or refuse and why, and what measurement would most quickly change the diagnosis? Give the specific numbers or observations you would require before any change.
There are no numeric key items. The answer is scored by required-element coverage, especially the ordered checks, explicit approval/refusal of proposed actions, the measurement that would change the diagnosis, and evidence required before changing operation.
The exact per-element accepted keyword groups are not reproduced in the PDF pages available for this audit.
The script checked two things: did the answer contain the expected numbers, and did it mention the key ideas? The exact code and answer keys are available below.
Half the score comes from the number check and half from the checklist.
These are safety and judgement scenarios, so the score comes from the checklist only.
Average the question scores to get a score out of 100. The leaderboard also reports number accuracy and checklist coverage separately.
For each expected numeric item, the scorer extracts every number from the complete answer text with a regular expression. The item receives a hit if any extracted number lands inside the item’s tolerance window.
Then:
The report describes item tolerances of 3–7%. The audit notes identify some absolute tolerance widths that are large enough to admit materially wrong values.
Each rubric element consists of one or more groups of accepted substrings. Each group must have at least one accepted alternative present in the lowercased answer. Matching is plain substring matching, not semantic evaluation.
Across the eight questions, the fixed rubric contains 48 required elements according to the scoring audit. A correct concept paraphrased without an expected substring can miss credit; an incidental substring can earn credit.
Each system’s overall Score is the mean of its eight answer totals. Elem % is the mean element score. Num % is the mean numeric score across the six numeric-bearing answers, not one pooled hit-rate over all 17 items.
| Question | Numeric items | Recorded key values | Audit note |
|---|---|---|---|
| Q1 · Hydraulics | 3 | 1.795 MG; 10.26 h; 5.13 h | Key checked and found consistent with the supplied inputs. |
| Q2 · Clarifier | 2 | 76.0 lb/ft²/day; 2,100 gpd/ft² | Key checked; first tolerance cited as about ±105 lb/ft²/day. |
| Q3 · CT | 2 | 84.0 min; 67.2 mg-min/L | Key checked; broad substring rubric can trigger on “75” in unrelated context. |
| Q4 · Settleability | 4 | SVI 150; RAS 6,667 mg/L; R 0.818; flow 3.44 MGD | Incorrect answer key Values assume SVI=150 rather than 50 mL/g. |
| Q5 · Digestion | 3 | 4,670.4; 2,101.7; 31,525 ft³/day | Gas-yield tolerance cited as about ±1,891 ft³/day. |
| Q6 · Dosing | 3 | 62.55 lb/day; 1.2197 lb/gal; 51.3 gal/day | Key checked; prompt also asks for mL/min, not listed among the three numeric items. |
| Q7 · Analyser | 0 | — | Element-only scoring. |
| Q8 · Wet-weather upset | 0 | — | Element-only scoring. |
| Total | 17 | 48 required elements across the suite | |
The main leaderboard includes only systems that answered all eight questions. Systems that skipped questions are shown separately because their averages are not a fair direct comparison.
Overall score is the mean of eight per-question totals. Values shown are from Appendix B1 of the report.
| Metric | AquaReason | Complete-field reference |
|---|---|---|
| Overall score | 89.9 | Median 84.3 (report) |
| Key points included | 92% | Median 85% |
| Number score | 88% | Median 88% (report) |
| Mean answer time | 16.5 s | Median 26 s |
| Mean answer length | 664 words | Median 247 words |
| Best overall score | Claude Sonnet 5.5 · 95.9 | |
Table 1 rounds AquaReason latency to 16 seconds. The executive summary gives 16.5 seconds.
Open the table to search or sort the full results.
| Rank | System | Score | Checklist % | Number % | Sec | Words |
|---|
These scores use only 3 to 7 answers, so they are kept separate.
| System | Answered | Score | Checklist % | Number % |
|---|---|---|---|---|
| Kimi K2.5 | 6/8 | 100.0 | 100 | 100 |
| Big Pickle | 6/8 | 95.0 | 90 | 100 |
| Nemotron 3.5 Lightning Free | 3/8 | 93.9 | 88 | 100 |
| MiMo-V2.6-Flash Free | 6/8 | 93.6 | 87 | 100 |
| Claude Opus 5.5 | 7/8 | 92.0 | 95 | 88 |
| Claude Sonnet 4.6 | 7/8 | 90.8 | 92 | 88 |
| Qwen3.8 Max | 6/8 | 88.8 | 90 | 88 |
| Space Bunny Free | 7/8 | 87.7 | 86 | 88 |
| GPT 5.4 Pro | 6/8 | 86.0 | 84 | 88 |
| MiniMax M2.5 | 7/8 | 86.0 | 84 | 88 |
| Grok Build 0.1 | 7/8 | 83.8 | 80 | 85 |
| Mistral Large 4 | 3/8 | 80.6 | 61 | 100 |
The leaderboard is useful as a snapshot, but several scoring choices can reward the wrong thing.
The correct sludge volume index is 50 mL/g, not 150. The scorer uses the wrong value to calculate three more answers, so its Question 4 number score is not a reliable accuracy measure.
The script scans the whole answer. A matching number gets credit even if it is just an example, a warning, or a value the model says is wrong. Longer answers get more chances to match by accident.
47 of 65 complete systems got the same 87.5% numeric score. The scoring steps are coarse, so the headline median of 88% looks more precise than it really is.
It may give points because a common word like “within” appears, or miss a correct idea because it was phrased differently. It checks for words, not meaning.
On six questions, numbers and checklist items each count for half. The two safety questions use only the checklist. Across the whole test, that works out to 37.5% number scoring and 62.5% checklist scoring.
The main table says 11th of 65 systems that answered every question. Another section says 17th of 77, mixing complete and partial results. Use 11th of 65 for the fair comparison.
The audit found the answer keys for Questions 1, 2, 3, 5, and 6 consistent with the supplied data. That does not fix the wider scoring issues.
It scored 89.9 overall and included 92% of checklist points. Its answers were much longer than typical. The fair reading is that it sits in the middle-to-upper part of the full-answer group, with a strong showing on safety questions.
The audit notes that Claude Sonnet 5.5 explained the correct SVI calculation, then described what values would follow if SVI really were 150. Because the script scans every number, it matched all four incorrect key values. Site AquaReason gave the correct chain without that hypothetical aside and received only 0.25 numeric accuracy on Q4.
Numeric credit included key values quoted conditionally.
False confidenceThe audit’s worked result: numeric 0.25, element coverage 0.833, combined ≈54.2.
Penalizes correct chainInput capture
Archive exact prompt text, full raw answers, timestamps, route/model IDs, error responses, and any normalization applied before scoring.
Scoring
Version and hash the scoring code, numeric answer keys, tolerance values, element pattern definitions, and aggregation script.
Validation
Use independent human review for engineering correctness, multiple runs per model, confidence intervals, and unit-/context-aware numeric extraction.
score_v2.py, explain_scoring.py, raw response JSON, and the full 48-element keyword definition list were not attached as standalone files here. The page therefore documents all provided scoring mechanics but does not invent missing per-element pattern lists or unspecified tolerance values.| Source section | What it supports |
|---|---|
| PDF pages 1–2 | Executive summary, experiment method, primary complete-answer ranking. |
| PDF pages 3–4 | Partial-answer cohort, model-family table, per-question results for leading systems. |
| PDF pages 7–8 | Findings and limitations, including one-run and keyword-rubric caveats. |
| PDF pages 9–10 | Full prompt text for the eight-question set. |
| PDF pages 10–13 | Complete ranking B1 and partial ranking B2. |
| User-provided audit notes | Regex and element-scoring pseudocode, tolerance concerns, Q4 correction, rank reconciliation, and numeric-score quantization. |