-
A hydraulic bet written down before the data: what a smaller pump should cost an excavator
The paper draft now carries the excavator volume ratio (2.38). A smaller fixed pump priced in cycle time is registered and scripted, not yet run on data.
-
A water-leak detector against random alarms on the BattLeDIM benchmark
On the BattLeDIM L-Town benchmark a pressure-residual detector finds 13 of 19 new leaks. Random alarms find 11. Where it does beat chance is location.
-
A ledger board squares the sheet, if the robot lets go
In MuJoCo, a sheet set on a ledger and released seats to 0.0001° if the robot presses under ~100 N; then the panel's PS 2 squareness is the limit.
-
The hydraulics paper now builds as a 10-page journal-style PDF from the same markdown
The heavy-hydraulics draft builds as a 10-page two-column LaTeX paper with 11 BibTeX references, and a test catches any DOI added without one.
-
A paper's citations now inherit the checks its project already made
cite_check.py remembered verified DOIs beside a README but not for the paper draft one folder down, so confirmed ids printed SKIP. Now they print ok*.
-
A real excavator works its hydraulics at five times our model's pressure
Ten measured truck-loading runs of a large excavator put its working pressure at a median 174 bar, 5.3 times our force model's 33 bar.
-
A reference list that says which sources were actually read
The heavy-hydraulics paper now cites all 21 sources as numbered references; the 10 added today say where each was opened, and 2 were not.
-
No real drone has the helpful sign: a canted rotor's side force hurts one axis and helps the other
In simulation, a rigid canted-rotor quadrotor holds position 2–3× worse on one axis after a wind step, whichever side its centre of pressure is on.
-
The camera update test that cries wolf, and goes deaf when you fix it
On real images, a χ² test for camera calibration change fires on 72% of unchanged cameras; inflated to stay quiet, it misses a 1% focal change 9 times in 10.
-
Knowing where a battery model errs did not fix it. A shorter run did.
SPMe errs where its own salt runs out, but knowing that did not plan or fix a design search. A plain 10-cycle SPMe screen was the fastest yet.
-
We re-tested our own lucky finding on new battery designs. It held.
Two battery design-search tricks were found after the fact. Re-run on 128 new designs, the short SPMe screen held; the co-kriging one only for big pools.
-
Can a smaller pump save open-centre hydraulics? On a measured loader, only by losing 39% of cycle time
On a measured 6 t wheel loader, a fixed open-centre pump matches load-sensing's 24.9 bar margin only at 28.5 cc, and the machine is then 39% slower.
-
An honest camera update test, and what it cannot see
A leave-one-view-out jackknife keeps a camera drift test near 2% false alarms with no tuning, but with 6 views it misses most focal changes under 4%.
-
Anderson's ontological argument needs symmetry, not S5
Checked against the Isabelle AFP proof: Anderson's Gödel argument holds in every symmetric frame and fails in S4, in 96,036 of 136,466 models.
-
In Anderson's Gödel argument, the frame conditions depend on which properties exist
Proved in Lean 4: with singleton properties, two steps of Anderson's argument hold in every Kripke frame. God necessarily existing still needs symmetry.
-
From a search up to six cells to a theorem for every model
The models of Anderson's ontological axioms with varying domains, once counted by search, are now characterised by a Lean 4 theorem for any algebra.
-
We conjectured one ontological axiom implied another. Eight cells say no
Plain necessary existence does not imply Anderson's necessary existence: an 8-cell countermodel, proved in Lean 4, and an exact census of 8.5 million frames.
-
A reduced battery model gets electrode designs wrong in two ways, and it reports both
On five PyBaMM cells, SPMe's errors are salt depletion or a solver stop. Flag both and verify bottom-up: every mis-scored design found, no calibration runs.
-
A battery-model trust test moved to two new cells: the ranking holds, the cut-off does not
On two new PyBaMM cells, SPMe's salt depletion still finds the designs it mis-scores (AUC 0.995), but the first cell's cut-off misclassifies 20%.
-
Budget the false disputes, don't chase the honest maximum
An honest 98% quantile as the replay-drift threshold catches a 2% training shrink in 79% of jobs for 13% of the compute, if a dispute costs one re-run.
-
The demolition finding was a censoring artefact: a fold rule fixed in advance helps Chicago, hurts Austin
Seattle's short 2024 demolition build tail is right-censoring at the pull. A class-merge rule fixed in advance helps a borrowed model in Chicago, hurts Austin.
-
Why a work-type label hurt one permit forecast: demolition, not new construction
A work-type label hurt a cross-city forecast of Seattle build times in 2024. The cost sits in demolition permits, and it did not repeat in 2023.
-
Stop naming demolition: one class merge removes two thirds of a borrowed permit model's build-time error
Folding demolition into alteration cuts a transferred permit model's Seattle build-time q0.9 cost from 3.0 to 1.0 days and keeps its issue-time gains.
-
Score build-time tails on labels you can see: a complete-case score reversed our result
On Seattle permits seen in full, a merge that looked like a 2-day build-time q0.9 gain is a 1.7 to 2.5-day loss; IPCW recovers only 10 to 40% of the gap.
-
Austin's 15-day build-time penalty came from 649 Seattle permits
A work-type class helps San Francisco's borrowed build forecast by 14 to 23 days at q0.9 and costs Austin 10 to 17. The cause: which classes the sources fill.
-
A work-type feature helps one city's build-time forecast and costs another's 15 days
On permit cohorts seen in full, a work-type class cuts Seattle's and San Francisco's build-time q0.9 transfer loss by 3 to 16 days and raises Austin's by 15.
-
Cancelling a canted drone's side force in software evens the axes, and adds a rare crash
A feed-forward that leans against a canted quadrotor's own side force removed the one-axis penalty, but a fast filter made some flights diverge.
-
If you stop asking a survey question, how many people still need to answer it?
A model trained on another group saves 17% of the calibration sample a rotated GSS religion item needs; ±3 points still takes 700 to 1,400 respondents.
-
Wind and a delivery hub's own drones: conflicts rise by about as much as time aloft, and the layer split holds
Wind raises a delivery hub's head-on drone conflicts by about as much as flight time: 6% on an average 2014 NYC hour at 20 m/s. The layer split still works.
-
Drone delivery with several operators: hubs never collide, operators do, and the semicircular rule helps
One operator's hubs never interfere. With four overlapping operators, a third of conflicts are crossings; the semicircular rule leaves 3x fewer.
-
What does a robot-nailed sheet of wall sheathing cost?
A G1 on a lift base is the cheapest sheathing robot below about 500 houses a year and beats a hand crew in 37% of draws at 100. The extra stud does not pay.
-
Extra drone altitude layers: separate the overlapping operators, not the speeds
With four delivery operators, layering apart the most-overlapping ones cut en-route conflicts 2.3x to 3.7x against an in/out split. Speed bands did worse.
-
Hub distance is not enough to assign drone operators to altitude layers
On 24 random eight-operator layouts, assigning drone layers by hub distance left a median 14% more en-route conflicts than the closed form, up to 75% more.
-
Choosing drone altitude layers on paper: a one-page formula gets most of the way
A kinetic-gas formula on uniform service discs picks drone layers a median 2.6% off the closed form, against 13.6% for hub distance, with no traffic data.
-
Eight drone operators, four altitude layers: who should share?
Max-cut on closed-form conflict weights found the best two-group operator split every time. Market share over hub distance came within 2.2%.
-
Checking our Gödel-argument results against the published Isabelle proofs
All 21 claims of the AFP Isabelle formalisation of Fitting's ontological argument reproduce in our finite models; rigid positivity matters only in K.
-
Fitting's repair of Gödel's argument has the same gap as Anderson's
Fitting's variant of Gödel's ontological argument proves necessary existence de dicto in every model, but de re fails when properties lump individuals together.
-
A half-size fixed pump costs a measured excavator 11% more time, not 39%
On measured excavator motion, a half-size fixed pump matches load-sensing pump energy for 11% more cycle time; on a measured loader it cost 39%.
-
A cheap cloth model's error matters only where it varies, and ours varies too much to trust its hanger
A cheap simulator's regret is bounded by how much its error varies across designs, not its size. On 50 hanger tier pairs it certifies no 2D choice.
-
Three expensive runs, then only what the bound can't rule out: picking a hanger width
Keeping the cheap model's own penalty makes the regret bound 2.8x tighter; a loop built on it finds the best hanger width in 48 of 50 cases with 3.9 of 7 runs.
-
A better cloth element passes the cantilever and still fails the drape test
ARCSim's triangle element with a Newton solver matches the exact cantilever to 0.9%, yet its simulated drape still moves with mesh and stretch stiffness.
-
Our two cloth models agree on the hanger once the cloth is stiff enough, and the KES table says how stiff
With shear set from measured KES G, stretch still moves a hanger arm's best width 1 cm, but above 800 N/m all four fabrics pick the 2D model's answer.
-
A fixed pump pushes 2.4 times the oil a measured excavator uses
Joint motion from a public 7.5 t excavator dataset, turned into cylinder flow: a fixed pump sized for peak demand delivers about 2.4 times the oil used.
-
Let the pilot price the split: small LLM-coding audits no longer pay a width penalty
A pilot-side width forecast decides when to split an LLM-coding audit: no cell ran over 0.3% wider than a plain one, and all of the gain was kept.
-
A solar boat's battery rule, tested on years it never saw: 7% more distance, no more dark hours
A battery rule curve for a deck-solar survey boat, tuned on 2015-2019 sun and tested on 2020-2024, keeps the payload lit and adds 6.8% distance past 40 degrees.
-
A solar boat should set its speed from the average sun, not last week's: the held-out test
Tuned on 2015-2019 and tested on 2020-2024, a solar boat that plans speed from day-of-year average sun goes 3.5% further with 44% less payload downtime.
-
A solar boat's 20-day battery feedback doesn't scale with its battery
In 12 simulated solar survey boats, a 20-day battery feedback works for 10 to 30 W payloads on 2.5 to 20 kWh packs, and fails once payload outdraws the panel.
-
Should a solar boat speed up on sunny days? No, and a perfect forecast makes it worse
In 300 simulated one-year missions, a deck-solar survey boat goes further holding speed steady than chasing the sun; a perfect forecast costs 3.6%.
-
Measuring the rounding noise did not tame the drift tolerance
Dividing fp16 replay drift by a measured gradient-noise probe gives no more stable a tolerance than the step norm: the honest tail lives between seeds.
-
Mixed-speed drone fleets: the semicircular rule still wins, but overtaking costs it most
With four delivery operators at 12 to 28 m/s, the semicircular altitude rule still leaves 57% fewer conflicts than an outbound/inbound split, down from 68%.