-
Fill the payroll service's template, not ours
Shift Roster Builder's team hub now fills the blank hours template your payroll service gives you, matching columns by name, instead of guessing each layout.
-
Fisher's exact test spends under half of its 5% error budget
A free Fisher's exact test calculator with Boschloo's and Barnard's tests. Computed exactly: at 20 per group Fisher's real error rate averages 1.9%.
-
Four receipt tax lines a parser missed: Total HTVA, a header read as TUA, VAT in a subtotal, and 0.00
How ai-bookkeeper now reads French HTVA totals, an OCR-bent TVA header, Philippine VAT printed in a subtotal line, and a zero tax on a zero receipt.
-
France's BR-FR e-invoice error codes, all 384 messages in English
FNFE-MPE publishes France's BR-FR rule messages in French only. E-invoice Preflight now reports all 384 in English, with the French kept beside each one.
-
France's e-reporting file (Flux 10): what the official controls miss
E-Invoice Preflight now reads France's Flux 10 e-reporting file and runs the PPF's controls offline. A 20% VAT line with 0.00 VAT passes all 150 of them.
-
France's BR-FR e-invoice rules now run in the browser, checked against FNFE's own XSLT
E-Invoice Preflight now runs FNFE-MPE's BR-FR Schematron 1.4.0.04 locally. It matched Saxon on 264 of 264 runs, after three fixes to how it reads Schematron.
-
France's e-invoice rules against Saxon, and a hidden space in Flux 10
France's BR-FR, extended, CDAR and Flux 10 rules, in the browser and on Saxon over 1,784 test copies: no rule ids differed. One Flux 10 gap is fixed.
-
Checking France's invoice status messages (CDAR) against FNFE's own rules
E-Invoice Preflight now reads France's CDAR status messages, compares them with the invoice and runs FNFE's BR-FR-CDV rules: 780 of 780 runs match Saxon.
-
A GTIN filed under Peppol's GLN scheme gets the GLN check: 581 test files our checker passed
In a CII invoice, an item's GlobalID under scheme 0088 meets Peppol's GLN rule, so a mistyped digit bounces the file. Our checker now reads line ids too.
-
Half the time, the same prices: speeding up a packaging optimizer without changing one answer
The SaaS feature packaging optimizer spent most of its time building throwaway arrays. Removing them halved the runtime and every output byte stayed the same.
-
Check every IFC model against your IDS on each push: a free GitHub Action
One workflow step checks every IFC export in a repository against every IDS file, with annotations, a JUnit report and BCF files. Tried on four real models.
-
Checking bridges, roads and ducts against an IDS: 348 of 348 results match IfcTester
IDS Model Check against IfcTester on buildingSMART's twelve IFC 4.3 and HVAC sample models: 348 of 348 results identical, plus an IFC2X3 gap.
-
One public IDS specification failed 665,224 entities and took our CI runner down with it
Running public IDS files in CI found an out-of-memory crash and a hang on truncated files. Both are fixed, and the runner is six times faster.
-
A date range in an IDS file is valid, and IfcTester fails every object on it
IDS 1.0 allows xs:date ranges. IfcTester 0.9.0 casts bounds to float and fails every object. An XSD pattern of the same dates reads the same in both.
-
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.
-
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.
-
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 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 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 invisible character, two XPath engines: Dutch VAT numbers and Peppol's R056-2
A valid Dutch VAT number written with B drew a false blocking error; a trailing no-break space slipped past. 3,149 disagreements with Peppol to 0.
-
Peppol checks a Belgian KBO number in three places. The preflight checked one
INV-062 and INV-063 apply OpenPeppol's id rules to party identifiers and legal registration numbers, with 0 disagreements on 18,794 whole UBL and CII files.
-
Peppol checks the payee's ids too: 3,311 of 9,596 test files our checker passed would have bounced
OpenPeppol's id rules match a payee's and a tax representative's ids, not only the seller's. Our checker now reads them: 0 disagreements on 18,790 files.
-
Peppol only warns about a bad Italian or Dutch address. The preflight now does too
Seven warning-level PEPPOL-COMMON rules now run as a non-blocking INV-061 warning, with 0 disagreements against Peppol's own XQuery on 23,999 drawn ids.
-
Our 16-bit raw masters held 12 bits: one table read, fixed
ShootFlow's sRGB encode read a 4,096-entry table at the nearest entry. Interpolating a 16,384-entry one lifts 16-bit masters from 4,096 levels to 45,000-65,536.
-
Keeping a burst together when the camera moves: crop-tolerant grouping in ShootFlow's cull
A perceptual hash split bursts the camera panned 4% through. Matching 88% windows took held-out burst-pair recall from 0.40 to 0.72 for 2 more false merges.
-
Halving one array in a raw develop, and the 12-bit tone table it turned up
ShootFlow's noise-aware develop holds its bilinear image in float32: 15% less memory, and every changed pixel value is one step of a 4,096-entry tone table.
-
Same bytes, 2.2x faster: banding ShootFlow's noise-aware demosaic
ShootFlow's noise-aware raw develop now runs in row bands on every core: 2.2x faster and 41% less memory on 14 real raws, every output byte-identical.
-
Raws with no noise profile now read their own noise: 52 real files through the new default
ShootFlow's noise-aware demosaic now reads the noise from the frame when a raw has no NoiseProfile. All 52 sample raws took it: what it changed and cost.
-
Why the noise scale stays at 0.8: one held-out tile decides it
We tried 861 rules to push ShootFlow's frame-read noise scale above 0.8, all picked on tune tiles only. Every one that won on tune lost on one held-out crop.
-
Pushing a 16-bit raw master 3 stops: what the old sRGB table cost
Lifted 3 stops, ShootFlow's old 16-bit masters skipped up to 39 of 256 screen codes in the shadows. The interpolated encode skips none on five real camera DNGs.