-
Asking for a door height range in an IDS: the model's own units, not metres
The IDS editor now offers a model's range for OverallHeight and other numeric attributes. Attributes compare as written, so mm and feet models need mm and feet.
-
Lenght, AkousticRating: the IDS editor now offers the standard name
17 rows in 7 public IDS files name a property one slip from the standard one. The IDS editor now says which name was meant and fixes it in one click.
-
The IDS editor now writes "more than" and "less than", and 5 of 6 public exclusive ranges open as rows
Range rows in the IDS editor can now be exclusive. Eight door-height ranges get the same verdict in IfcTester; 5 of 6 public exclusive facets open.
-
External walls only: the IDS editor now narrows a specification by property, attribute or classification
The free IDS editor adds conditions to a specification's applicability and counts how many of an open model's objects each keeps, as the checker counts them.
-
An IDS written for IFC2X3 and IFC4: the editor read it as IFC2X3 only
The IDS editor opened multi-version files in their first schema and flagged IFC4 sets as errors. It now edits in the best schema and audits in all.
-
LoadBearing = TRUE: the same IDS file checks the walls in one tool and none in another
Three public IDS files ask Pset_WallCommon.LoadBearing = TRUE with no dataType. Two checkers disagree on what that matches. The IDS editor now flags it.
-
When the IDS is the problem, CI now points at the IDS
72 of 507 specifications in 64 public IDS files carry an audit warning. The IDS model check Action now annotates each on its own line in the IDS.
-
A 219 MB IFC model in 1 GB of memory: read the geometry only if someone asks
IDS Model Check now reads IFC entity arguments lazily. A 219 MB federated model drops from a 2.5 GB peak to 1.0 GB, with identical reports.
-
Lists of dates in IDS: xs:date or xs:string, and why P24M is not P2Y
The IDS editor now writes date and duration lists on xs:date and xs:duration. Both checkers compare the values as text either way, so list every form.
-
Two IDS checkers agreed on 51 results per model, and both skipped 112 walls
65 public IDS files on four real IFC exports, against IfcTester: 1,661 of 1,736 results identical, and a gap both tools share that reports now show.
-
Twenty number checks the IDS editor held back, and the 12 it still should
IDS-Audit-tool's files ask for numbers on attributes with no class named. Eight now open as editor rows; twelve are list checks that always fail.
-
A list of numbers in IDS: one checker allows a millionth, the other wants every digit
The IDS editor now writes one-of lists of numbers. IfcTester compares them exactly, so the list from a model names each value to the last digit.
-
One wall in two discipline models: checking GlobalIds across a federated IFC set
Each file passed its own GlobalId check. Compared as a set, HHS Office's architect and structural exports share a wall, and buildingSMART's scene a roof.
-
Seven public IDS files ask for a data type no standard model can have
16 requirements in 7 public IDS files give a standard property the wrong dataType. The IDS editor now opens them as rows and fixes each one with a click.
-
Half the ranges taken from a Revit model's own values fail that model in IDS
The free IDS editor now offers the values a model holds. 364 of 752 ranges copied from them failed their own model, because IDS ranges take no tolerance.
-
An IDS specification doesn't have to name a class, and buildingSMART's own test files mostly don't
Our IDS editor opened buildingSMART's audit-tool files as 28% editable. Letting a specification select by attribute alone took that to 76%.
-
IDS specifications that apply to every entity: 68 public files, 96 s down to 13 s
37 specifications in public IDS files apply to every IFC entity. Three changes cut a 68-file check of a 40 MB model from 96 s to 13 s, same reports.
-
Filling in a map from 371 points: kriging ocean waves, and why inverse distance lost to the nearest point
A free browser kriging tool maps scattered readings with standard errors. On ERA5 wave heights it misses by 0.39 m; inverse distance by 0.62 m.
-
LA County's Fair Workweek is not the City of LA's: asked cover is exempt and short rests cost less
Shift Roster Builder now prices LA County's Fair Workweek from the ordinance text. Five late changes at $18 an hour: $99 in the county, $172.50 in the city.
-
Build the season fairly, then load it into TeamSnap or SportsEngine in one upload
The free league schedule generator now writes TeamSnap's and SportsEngine's own schedule import files, columns copied from their published templates.
-
Take away the oracle hour: a leak localiser keeps about half its hits when a real detector sets the day
On BattLeDIM's L-Town, localising at a real detector's alarm day instead of the oracle hour drops 300 m hits from 15 to 8 of 30 detected injected leaks.
-
Held out: the shape-chosen leak rule finds 25 of 64 unseen L-Town leaks, against 16 for the newest source
On 64 new leaks simulated through BattLeDIM's own model, the steepest-ramp rule places 25 within 300 m against 16 for the newest source (P = 0.022).
-
Slow leaks look like ramps, but timing the ramp against the alarm loses them again
On BattLeDIM's L-Town, a step-or-ramp fit labels every slow leak's source a ramp, yet timing it against the alarm finds 3 of 17 slow leaks, not 6.
-
Let the leak's shape choose: the steepest ramp, else the newest source, finds 15 of 32 L-Town leaks
On BattLeDIM's L-Town, picking the steepest ramp-shaped source, else the newest, places 15 of 32 leaks within 300 m, with 6 slow leaks and 9 bursts.
-
Little Lamps: Anselm and the whitest bread
A new Little Lamps bedtime story: the Aosta boy who dreamed of bread at God's table, the abbot of the young tree, and the hare under his horse.
-
Little Lamps: Bernard and the fair share
A new Little Lamps bedtime story: the monk who talked his whole family into Cîteaux, and the little brother who said heaven was not a fair share.
-
Little Lamps: Bruno and the seven stars
A new Little Lamps bedtime story: the Reims schoolmaster who kept a promise made in a garden, and the bishop who dreamed of seven stars.
-
Little Lamps: Charles Borromeo and the prayers at the windows
A new Little Lamps bedtime story: the archbishop who stayed in Milan through the plague of 1576 and had a whole city pray together from its windows.
-
Little Lamps: Gertrude and the heartbeat at Helfta
A new Little Lamps bedtime story for 16 November: the girl who loved books at Helfta, and the heartbeat she wrote that she heard.
-
Little Lamps: Hedwig of Silesia and the shoes in her hand
A new Little Lamps bedtime story for 16 October: the duchess who fed the poor at her own table and, the old story says, carried her shoes.
-
On a year it never saw, a solar boat's sun correction works only if the clamp stays narrow
Scored on 2025 sunlight, narrow learned corrections still beat the raw climatology by 5 to 6 of 84 cases. Wider clamps fall 6 to 9 below it.
-
A solar boat can choose how hard to trust its own sun log, from the log itself
Letting a solar boat set the clamp on its learned sun correction from its own ratios cuts the worst-case loss from 23.8 to 13.8 cases of 168.
-
With three seasons of log, a solar boat's self-set clamp beats the pooled correction, but not up north
With two or three seasons of its own sun log, a solar boat that clamps its correction to the log's own spread wins 159.5 of 168 cases, against 155.5 pooled.
-
The solar boat's 'widen the correction up north' result came from one bright point
Weighting nine high-latitude points equally, a wide sun-correction clamp's lead fell from 21.2 to 2.5 of 168 cases. The narrow clamp is the safer default.
-
A solar boat's sun correction should widen as its log grows, not as it sails north
Scaling a solar boat's self-set correction clamp by √seasons cut its worst-case shortfall from 26.6 to 7.1 of 168 cases. A latitude switch did nothing.
-
A solar boat's learned sun correction works best held to ±5%, unless it plans and sails on different data
Sweeping the clamp on a solar boat's one-season sun correction: ±5% beats no correction on all 30 points, but a plan-sea mismatch wants it wide.
-
At 50 to 60 degrees the solar boat is mostly parked, so its sun-correction scores there say little
No sun-correction rule beat the 7-day baseline at eight 50 to 60 degree points. Every loss was distance, not dark hours: with 50 W the boat barely moves.
-
A Wave Glider out-sails a solar boat at high latitude, but its sensors are dark most of the winter
On its own 225 W deck and 6.8 kWh pack, a Wave Glider's 30 W payload is dark 229 days a year at 46 to 60 degrees, yet it still out-sails a solar boat there.
-
Mercury against the cuff in 4,212 adults: least squares says 0.87, Passing-Bablok says 1.02
A free method-comparison tool on NHANES blood pressure: the cuff reads 1.3 mmHg below mercury; least squares wrongly finds a 13% proportional error.
-
Three merged pull requests that stayed open, and the one-line check that finds them
Stalled-PR sweep: four open PRs were already on main under their own numbers. A commit-subject check now flags them; two green PRs landed.
-
A nail gun's recoil lifts the nose off the wall. Does that undo a humanoid's millimetre spec?
A framing nailer's recoil, bracketed from published data at 0.09-8.7 N s, lifts the nose. The re-press keeps the 0.012 mm spec; the stance is the risk.
-
Nine trials in ten never needed to leave the module: 30-team leagues join the page
Counting first showed most of a schedule search's tables were copied out of WebAssembly and thrown away. Keeping them in cut the step 34%.
-
One call for several local CI checks
The local CI runner took one workflow per call and refused --only without a sweep. Now it takes several names and gives one verdict per workflow.
-
One command now checks a new blog post: check_posts.py
Agents ran three post checkers by hand, or guessed a name that did not exist. check_posts.py runs front matter, links and near-copy checks on a branch's posts.
-
One filter, four loudness readings, run four times
Chant Forge's master check filtered every channel four times to report four loudness figures. Sharing one pass cut it by about 30% with identical output.
-
One gear-pump rule for every idle setting: weight both idle drags by how long the excavator idles
Adding the load-sensing pump's standby power, scaled by idle share, lets one gear-pump rule predict idle settings it never saw, within 0.0062.
-
One GlobalId, three material links: what shared IFC GlobalIds really are
Of 35 GlobalIds buildingSMART's Simple-Scene shares between files, 8 are elements. The rest follow them, or reuse one id for different links.
-
One loop for one cost: a 23% faster PELT without changing a bit
PELT's inner loop served every cost model. Giving the Gaussian mean cost its own loop made 6,225 real calls 23% faster with identical results.
-
One pip install, three broken Pythons
Installing torch with python3.13's pip deleted the setuptools that python3.11 and 3.12 shared. Our interpreter finder now puts it back.
-
One calibrated lithium-plating exponent per cell type halves the ten-cycle fade forecast's error on LG M50
On 128 fresh PyBaMM designs, a plating exponent calibrated once per parameter set cut LG M50's 100-cycle lithium-loss error from 9.3% to 4.9%.