-
The wall takeoff now counts the studs the outlet cables drill
A finished cable-hole count sat unmerged for 14 days in a conflicted PR. It now ships: studs bored between neighbouring receptacle boxes, per wall face.
-
The fastest cutting-stock solve is the one you already did
A framing takeoff re-solved every lumber size's cutting-stock problem on every edit. Keeping 128 recent answers made a test 4x faster, output identical.
-
Two thousand arrays of zeros per lumber order
Each takeoff in our framing tool built about 2,000 zeroed typed arrays and threw them away. One reused buffer: 11.6 to 9.8 ms, same answers.
-
Every lumber length was even, so the optimizer did twice the work it needed
Every lumber length in the optimizer's knapsack was even. Dividing out the common factor cut our slowest engine test by 28%, same answers.
-
Sizing house water pipes with Hunter's rule, computed exactly
Free house water pipe sizing by Hunter's 99% rule, computed exactly. On a two-bath example the normal approximation picks a 3/4 in main; exact needs 1 in.
-
The lumber optimizer was checking 28 million cutting patterns one digit at a time
An exact lumber search spent 0.5 s per wall testing which cutting patterns fit. Bitsets made the test suite 57% faster with identical answers.
-
A framing takeoff that ignored a mistyped option
wall-framing-takeoff used to ignore any option it did not know, so a typo gave a plain lumber order with no warning. It now stops and suggests the right option.
-
A flag that does nothing is worse than an error: wall-framing CLI
Drawing-only options on a plan JSON, and --swing without --sensitivity, were silently ignored. The CLI now says so.
-
February 30th is no longer March 2nd in the construction schedule
The wall-framing takeoff's schedule and order-by dates now refuse a calendar day that does not exist instead of quietly reading it as the next month.
-
Wall framing takeoff: order-by dates now say why the schedule was refused
The order-by-date command used to say only that the schedule had problems. It now names the problem.
-
A malformed plan file now gets a plain sentence as its error
The wall-framing takeoff command line now names what is wrong with a plan file of the wrong shape, instead of printing a raw JavaScript error message.
-
A committed sample went stale when the cutting-stock solver got faster
Five speedups to the whole-house lumber order changed which boards a small sample job rounds to; the committed sample bid page still showed the old order.
-
Probing every layout function in a framing tool for raw crashes
A sweep of every layout function in wall-framing-takeoff with null, empty and NaN input found one that threw a TypeError.
-
A null in the lumber list crashed two framing repairs
Probing the framing takeoff modules that no fuzz test covered found one crash in 2 of 5, now fixed and tested.
-
A framing sketch editor let a door be of kind NaN
Calling every sketch-editor function with hostile values found one gap: addOpening stored any kind, and NaN saved as null.
-
Batching new rows made whole-house lumber ordering a third faster
Adding a round's new cutting patterns to the LP together, then pivoting once, cut a 950-piece lumber order from about 3 s to about 2 s.
-
Is exact steepest-edge pricing worth building for a lumber cutting-stock LP?
Removing the row-norm term from a dual simplex leaving-row rule slows a 950-piece lumber order from 1.5 s to 2.3 s; exact weights would gain little.
-
Five more ways the wall-framing engine could crash on empty input, closed
Calling every export of the wall-framing engine with null, a number, text and an empty list found five more raw TypeErrors. All now return a reason.
-
Calling every framing-engine export with garbage
Probing the wall-framing engine's exports with null, numbers and empty objects found three layout functions that failed with raw JavaScript errors.
-
Six more raw TypeErrors gone from the wall-framing takeoff
Calling every wall-framing-takeoff export with null found six more that threw an unhelpful TypeError; now each says what it needs.
-
Choosing the simplex row by its norm cut a lumber-order solve by a third
A one-rule change in the dual simplex of a framing lumber optimiser took a 950-piece order from 1.9 s to 1.4 s, still within 0.06% of the LP bound.
-
Profiling first: a 2.5x faster whole-house lumber order
A CPU profile of the whole-house lumber order showed the simplex took 88% of the time; a sparse pivot made it 2.5x faster with identical output.
-
A whole-house lumber order on a real Revit model: 48 seconds to 7
Three floors of a real wood-frame house, 978 pieces, one lumber order within 0.04% of its lower bound, now in about 7 seconds of CPU.
-
Stacking floors survived hostile plans
Probing the --stack floor-stacking code with hostile plans found no crash; five tests now pin the behaviour.
-
Sweeping a framing takeoff's exports with hostile input: what is left
Calling about 40 takeoff modules' exports with null, 5, text, {}, [] and NaN found one public function still throwing a raw TypeError.
-
Warm-starting the cutting-stock LP: 7.5 s to 5.1 s on a whole house
Adding each round's cutting patterns as rows to the last optimal tableau, instead of re-solving, cut a 950-piece lumber order from 7.5 s to 5.1 s.
-
A board foot calculator that says which size it counted
A free board foot calculator that counts lumber on the sold size, shows the milled size beside it, and handles hardwood quarters and cost.
-
A whole-house lumber order that stopped hanging
Ordering a three-storey house's framing lumber as one cutting-stock problem hung for 12 minutes; a dual bound and column pruning cut it to 48 seconds.
-
Advanced framing on a real house: the saving held at about 27%
The advanced-framing bench, run on a real Revit house instead of invented plans: all three details plus 24 in spacing cut the lumber order 24 to 28% per floor.
-
Stress-testing a board-foot calculator with 400 random lumber lists
The board-foot calculator from wall-framing-takeoff now has a seeded property test: random lumber lists either get a reason for refusal or add up exactly.
-
Framing allowance rules against a real house: one is close, one over-orders by a quarter
Two common stud-count rules of thumb set against a counted lumber order on a real three-floor house, with the numbers and what they do not show.
-
Half a nail per stud end: fractional counts in the framing takeoff
Probing the takeoff's validators found that 2.5 nails per stud end and 1e-9 screws per box were accepted. Now refused.
-
How Many Lag Screws Hold a Deck to the House? A Ledger Check You Can Read
The deck framing tool now turns joist load into pounds per foot of ledger and compares it with the fastener value you type from the maker's table.
-
How many cubic yards of mulch, topsoil or gravel do you order?
A free page now turns bed sizes and a depth into cubic yards to order, tons and bags, with the arithmetic shown.
-
Moving a Door to Another Wall in the Framing Sketch Editor
The sketch editor's engine can now move a door or window to a different wall in one step, with the same overlap and fit refusals as placing one.
-
How many hurricane ties does a roof need? A takeoff that counts them from your engineer's numbers
The roof tool now turns a typed uplift pressure and a connector's rated capacity into connectors per rafter end and a total to order.
-
A roofing waste factor of -1 ordered minus 39 bundles of shingles
The roof takeoff accepted any typed roofing setting. Nonsense values now get a reason instead of a negative or missing order.
-
Stacking three real floors: it works, and it takes five minutes
Two runs of the wall-framing takeoff's --stack on the Schultz Residence floors agree it saves about 0.3%, and show the solve is slow.
-
One flag frames all three floors of a real house
The wall-framing takeoff's --whole-house flag, run on the Schultz Residence IFC, matches the four-flag form and skips no wall.
-
When the Door Is as Tall as the Wall: framing takeoffs from messy BIM models
Four walls in a real house model were refused: the header was deeper than the room under the plates. A new flag swaps in the deepest header that fits.
-
How many boards do a winder stair's radial supports need?
The stair tool now turns a winder's radial supports into a stock-board count, checked by hand arithmetic.
-
Does a saw cut change how many boards a winder's supports need?
Winder support board counts now allow for saw kerf, which can add a board when pieces just fit.
-
A negative window sill, one fix after the last one
The door and window schedule refused a window taller than its header height only when typed per opening; the plan-wide default slipped through.
-
A lumber size called toString got through the framing validators
Eleven size lookups in the wall-framing tools used the JavaScript
inoperator, so names like toString passed validation and crashed or returned null orders. -
A real wood-frame house breaks our IFC reader in useful ways
We ran a real US wood-frame house through the framing takeoff: 30 of 102 first-floor walls were concrete, and doors at wall ends still block framing.
-
A stair wall's cutouts were being framed as a door
Dropping floating low voids as stair cutouts lets the takeoff frame the Schultz Residence first floor: 213 pieces, 0.19% over the cutting-stock bound.
-
A window schedule that printed a sill below the floor
Our door and window schedule happily printed a sill height of minus 53 inches. It now refuses header heights that cannot exist.
-
The concrete calculator now plans the saw cuts, not just the truck
A slab order says how much concrete to buy. The free calculator now also prints control-joint panels, saw-cut feet and cut depth from a checkable rule of thumb.
-
Counting stucco from the wall plan: bags, lath and trim for an exterior
The framing takeoff now counts cement stucco over metal lath from the same walls and openings the siding uses, with every assumption typed and visible.
-
A door and window schedule from typed walls, in the browser
Type walls and openings, get D1/W1 marks, counts, rough openings, headers, sill heights and a CSV. Same engine as the whole-house framing takeoff.