-
Five bowling teams that can't use the wall pair: why the first legal schedule isn't the fairest
With five or more bowling teams kept off a lane pair, comparing several legal dealings instead of taking the first lifts fully even seasons from 37 to 42 of 48.
-
Bowling lane limits, solved once per shape: why a team's name doesn't matter to the lane rotation
Bowling lane limits on hard seasons, solved by SAT once per limit shape and fitted to any league by renaming teams: 60 of 112 seasons in target became 106.
-
Bowling lane rotation: the week order does not matter, and a timeout becomes a proof
Solving a bowling league's lane rotation as counts per round, not week by week, turns solver timeouts into instant proofs and two new even seasons.
-
Bowling lane rotation: a random walk and a SAT solver close the last six uneven seasons
The free bowling league schedule maker now rotates lane pairs as evenly as possible in all 36 measured seasons, up from 30. How a walk and a SAT solver did it.
-
Bowling lanes: an even split, and never the same pair two weeks running
The free bowling schedule now cuts back-to-back weeks on one lane pair from 392 to 148 over 36 seasons, without making any team's lane split less even.
-
Bowling league schedules: keeping a team off a lane pair without breaking the rotation
The free bowling schedule maker now keeps a team off a lane pair every week as a hard rule. Measured on 142 seasons against the usual hand fix.
-
44 bowling league seasons where no lane rotation can be even, proved by a SAT solver
Some bowling seasons can't give every team its even share of lane pairs. A SAT solver proved 44 of them; a season as long as the lane pairs is the usual one.
-
Burst grouping for a 10,000-photo cull: the same groups in 5.8 s instead of 115
ShootFlow's cull now finds burst groups in C on every core: identical groups to the Python index, 10,000 frames in 5.8 s instead of 115 s.
-
Burst grouping that survives a wide pan: 10% pans went from 7-28% grouped to 86-95%
ShootFlow's cull compared only one frame's centre window, so pans past 6% split bursts. Off-centre window pairs fix it: held-out pair recall 0.91 to 0.985.
-
Burst grouping that survives a zoom: 10% zoomed frames went from 40% grouped to 99%
ShootFlow's cull now checks each frame against smaller windows of its neighbour, so frames zoomed 3-10% tighter stay in one burst. Held-out: 0.72 to 0.91.
-
Canon's tiled CR3s were on the older cameras: 39 raw files, 21 bodies, checked against LibRaw
We guessed the R5 wrote tiled CR3s. It didn't. The EOS R, RP, M50, 90D and R100 do, and our reader refused all of them until today.
-
When did your data feed go weekly? Checking a stale-data detector against 27 documented dates
A free check that says when a series started repeating itself dated 20 of 27 US states' documented switches to weekly COVID-19 reporting, most within 3 days.
-
Can a change detector find a currency peg from repeated prices alone? Four of seven times
We wrote down seven documented currency-peg dates, then asked a stale-feed check to find them in 50 years of Fed quotes. It dated four within two weeks.
-
A slope runs straight, a compounding gap bends: telling them apart in a synthetic control
On GDP-like panels a donor's own slope hides among gaps that all grow. Reading each gap's curvature finds it more sharply. Pre-registered, 32,000 panels.
-
Scored where it switches on, the panel shape word hides a donor's own slope
A pre-registered re-test on 32,000 simulated panels: read against a compounding panel, a donor's own big slope is called 'held' 90% of the time.
-
When every gap grows: reading a synthetic control's placebos against the panel's own trend
A panel-relative shape word cut wrongly named units on compounding panels from 80% to 22%, but missed one pre-registered bar by 0.4 points, so it does not ship.
-
When every country's gap grew: a panel-relative word, offered but not the default
On West Germany 1990 the plain word called 12 of 16 placebo gaps 'grew'. Read against the panel it names 2. Why it is an opt-in, with the numbers.
-
Passing every simulation and missing on real data: a feed check reads weekday schedule changes as returns
Choosing a weekday or chain model per stretch finds 200 of 200 simulated returns with no false alarms, but dates only 3 of 8 documented real ones.
-
Spotting a feed that briefly updated more often: two pre-registered rounds, both failed
A scan for brief stretches of more frequent updates holds its false-alarm budget only by missing every two-month return. The weekly calendar is the problem.
-
When people see the change coming: backdating a synthetic control, tested
An effect that starts 2-4 points early loses up to three fifths of a synthetic control's power. Backdating wins it back; the placebo warning half-holds.
-
Comparing a handful of stores? One store with its own bad month can hide a real effect
With 11 to 21 units, a real effect reaches rank 1 in about 57% of simulated panels. One donor with its own shock cuts that to 38%, or 9%. Leave it out first.
-
Not sure when people started reacting? Test every lead at once without fooling yourself
Running a synthetic control at five backdates and keeping the best p doubles false alarms. A range test finds nearly as much with none of that cost.
-
Teaching a feed check about weekends: 0 to 116 of 200, four short of the bar
A weekday repeat cost lifts two-month returns to daily reporting from 0 to 116 of 200 found, with no false alarms. The pre-registered bar was 120.
-
A cover that is three quarters copies: two repeat jobs out of chant-forge's release builder
Mirroring a symmetric cover glow and reusing one loudness analysis cut a two-track chant-forge release build test from 15.6 s to 12.7 s, same bytes.
-
A five-pixel gap in the staff: three 'misread' chant notes were never read at all
Chant Forge's scan reader kept only the longest unbroken stretch of a staff. A 5 px break lost phrases and clefs. Joined: +82 notes.
-
A hum that drops out: five detuned voices, one nasal, and a fix the reader only half likes
Chant Forge sang its final m from five beating voices, so the hum brightened or dropped out by chance. One voice steadies it; the read-back is mixed.
-
A small note with a hole in it: three chant liquescents the scanner lost to the print
Chant Forge's score reader missed ten one-step cephalici. Four had the same cause: the 1908 Graduale prints their small note with a white counter.
-
Notes lost to a white fleck: how one missed chant note found 200 more
Chant Forge's scan reader lost a square with a white fleck in it. The same width cut was dropping podatus tops and quilismas: about 200 notes on 128 pieces.
-
One voice, too loud: why a steady nasal hum failed on short low notes, and the level that fixed most of it
Chant Forge's one-voice nasal hum lost D3 chant nasals. Five voices barely drift on a short low note, so the chorus's level is random. Matching it: +79 nasals.
-
Check the house before you build it: nine in ten floor plans were thrown away after the rooms went up
Nine in ten candidate floor plans failed a constraint after their rooms were built. Checking first cut the search by about 40%, same plans.
-
"The one with the halo": picking an earlier design by what it had
The clothing studio read "the one with the halo" as "add a halo". Now it restores the latest version with one: 23 of 23 dev, 12 of 12 held out.
-
Twelve Coolpix raw files read as noise, and nothing complained
ShootFlow's NEF reader took Nikon Coolpix NRW files without an error and decoded them into noise. Five storage layouts later, 13 of 13 match LibRaw.
-
Cutting rebar longest-first: when it buys two bars too many, and how to prove the plan can't be beaten
A free tool reads a bar bending schedule, works out BS 8666 cut lengths and weights, and cuts 12 m stock bars with a plan proven optimal in 197 of 200 tests.
-
Minolta's last raw files, from the DiMAGE 7 to the Dynax 7D, read sensel for sensel
ShootFlow now reads Minolta and Konica Minolta MRW raw files directly. On nine bodies every sensor value matched LibRaw 0.22.
-
Phase One IIQ files, from the P25 to the IQ3 100MP, developed with the colour matrix they carry
ShootFlow now reads Phase One IIQ L raw files directly and needs no camera profile. On ten backs every sensor value matched LibRaw 0.22.
-
Our e-invoice checker failed every Peppol self-billing invoice. Now it uses the right rules
Peppol self-billing invoices name peppol.eu, so our checker ran the Billing rules on them and rejected all nine of OpenPeppol's examples. Here is the fix.
-
A date with a timezone hid a no-break space from our e-invoice checker
We checked which invoice values our checker treats as dates or numbers against Saxon. Dates like 2024-01-31+01:00 were missed, and 30 February was taken.
-
Fifteen penalties, one Gram matrix: a 5x faster conformal interval page
The conformal interval tool rebuilt each cross-validation fold 15 times. Building it once: 462 ms to 89 ms per analysis, bit-identical output.
-
Forty comments could freeze our e-invoice checker
A one-line regex that spotted France's e-reporting files backtracked 2^n ways on n XML comments. How we found it, the fix, and why CI missed it.
-
Four thousand awaits in a row: a check that spent two-thirds of its time idle
A check read 2,565 pages with one awaited fs call after another and sat idle two-thirds of the time. Sync reads: same output, 610 ms down to 150 ms.
-
Free DXF nesting in the browser, with a gap you can check
A new free tool nests irregular DXF parts on sheets, puts washers inside flange bores, and proves every gap twice: once by construction, once by measurement.
-
Grouping 10,000 photos into bursts without comparing every pair
ShootFlow's cull compared every pair of photos to find bursts. A pigeonhole index on hash chunks gives the same groups 6x faster at 10,000 frames.
-
How many frogs did nobody catch? Capture-recapture on 29 years of USGS data
A free capture-recapture tool on USGS chorus frog data: two frogs per frog seen in 2010, a fourfold model split in 1999, and where each estimator fails.
-
How much tach noise the tennis feeder's contact-time survey can take
On 144 simulated drills the feeder's contact-time survey faded at half a microsecond of tach jitter and was blind from 1.5 us. A new command reads a real tach.
-
How sure is a league table? Re-ranking the 2023-24 Premier League from its results
A free Bradley-Terry tool fits all 380 results of 2023-24: City were likeliest the best side, but only 59% likely, and 13 clubs span 8+ places.
-
Our IDS checker ran 2.85 million attribute tests where 191,000 were enough
Attribute rules that differ only in their value now share one reading of each element. 68 public IDS files run 30% faster, and a string memory leak went away.
-
Our IDS checker read property sets it could never match
Indexing IFC property sets by name cut 68 IDS files on a 40 MB MEP export from 7.9 s to 4.6 s with identical reports. A cache that seemed to help did not fit.
-
Seven of every ten tests our IDS checker ran were repeats
On a 40 MB MEP export, 68 public IDS files ran 11.4 million facet tests, 7.9 million repeats. Keeping the results cut the run 20-30%, same reports.
-
Nine regex anchors our IDS editor was quietly writing into public files
Our IDS editor now repairs one-answer schema faults as it opens a file. Patterns another checker would misread in what it saves: 9 to 0.
-
A 147-class IDS rule reads as 79 classes once each class gets its own subclass box
IDS matches exact IFC classes. Our free IDS editor now gives every class its own subclass box, and opened files list 368 class names where they listed 506.