* UI: rim and wall picking tests for a circle of arcs that is one wall A circle drawn as two half arcs now extrudes to one full-turn wall with its seam edge, and each rim is one closed edge (tangency-labs/smlib#67). The tests keep their intent on that body: a rim clicked once is one item, measured and highlighted whole and picked from either side; a wall picked either side of its seam is the same surface, lit whole, and toggles off from the other side; every face is its own patch. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Fillets: a later round at a corner where earlier rounds meet blends them again with it The owner's ruling of 2026-10-30: a later fillet on an edge at a vertex where earlier rounds already meet in a mitre makes the corner rounding all of them at once makes, one smooth patch, the mitre gone. A body made by constant-radius rounds keeps what they were made on and which edges they rounded at which radius; a later round reaching such a corner blends the earlier rounds' edges (from the earliest of those meeting there on) with the new edges in one SMLib blend of the body before them. The result's history is put over the body the later round was given: an earlier round's face is that face trimmed anew (its name kept), the corner patch and the new rounds are the later fillet's. A picked mitre seam has no round of its own: it is refused unless a new edge of its radius meets it. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Tests: a later r3 round at an r2 mitre, through the Fillet feature, makes the all-at-once corner Two box edges rounded r2 in one fillet, then the upright edge at their mitre r3 in a second fillet (tangent chain on, so the seam comes with it): 10 faces, 7928.743041 mm³ as fillet_radii of the box gives, the r2 rounds' names kept, the r3 round and the corner patch the second fillet's. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Kernel: a body's record of rounds goes with its history, and can be read back The rounds that made a body are over the body its history is over: a new history (an operation carrying a step's result back to its own operands) leaves the record out, so a later round never reads one history against another body. Body::rounds gives the record and Body::with_rounds_of takes one back, checked (edges of the body before them, a fillet's radii, the body's history over that body), for a saved model to keep it. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Model cache: a body made by rounds keeps them, so a later round blends them the same after opening A design gave another body when opened from its model cache: the rounds a body was made of lived only in memory, so a later round at their mitre was built sequentially (or refused, as too large) after opening and blended with them when evaluated anew. The saved model now records, per kernel body made by rounds, the body they were made on (a place in the bodies, stored once though no state holds it) and the edges with their radii; reading it attaches them back down each chain, and a thinned model keeps those bodies with the bodies made from them. Model cache format 7. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Tests: a corner patch of rounds 2/3/4 takes no more than the strips leave in its block three_rounds_at_a_corner bounded the patch's extra cut at 3 mm³ beyond the strips, a figure with no derivation; SMLib's all-at-once body at radii 2, 3, 4 takes 3.099 (V 7878.579574 against strips 7881.678). That body is the strips' outside the block its patch lies in: its rounds are the strips' cylinders ending at a's section y = rc, b's x = 20 − rc and c's rails where they meet a's and b's (the patch's four corners, now asserted), so the patch takes at most what the strips leave in that block (11.86 at 2/2/3, 32.69 at 2/3/4). The lower bound is that block; the upper one, at most the strips' volume, stays. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Tests: the io crate's hand-built saved models list their rounds, as format 7 records do Model cache format 7 (f3cf0c4f3) records a `rounds` list in every saved model, and reading one without it is refused ("saved model: rounds"), as is a model without any of its other lists: the states, the preview and the thinned model all came back empty. The io tests' saved_model and timeline_model wrote format-6 records, so six tests (the round trip, the repeated part stored once, and the four too-big-for-the-file cases) read nothing. Their bodies are none made by rounds: the list is empty, and every expectation stays as it was. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * SMLib: pin eaa998a (tangency-labs/smlib#68, #69, #70) Batch 4: drafts and loops, mitre corners, rim chamfers, rulings, tight box, stitch, point classification, eased corners. Batch 5: a face's tight box divides its cells at the surface's knots (thread boxes exact); a cylinder, cone, sphere or torus is extended along its own circles. Batch 6: a revolution's extension closes its turn; a dropped point's foot is the converged one. The C API is ABI 5 (smlib_blend_dropping and smlib_brep_classify_point are new; nothing existing changed), so the binding expects 5. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Tests: a strip's tangent and curvature run-offs are the distance long across the surface SMLib measures an extension's distance across the surface (smlib_extend_sheet corrects CreateExtendedSurface until the parameter line through the side's middle is that long), so each run-off of the cylinder strip, swept 20 along z, adds 5 x 20: 10 pi/2 20 + 100 = 414.159 for both. The parabola-length formula (418.18) was truck's. Ruling d2 (2026-10-30). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * kernel: one smooth angle, and a round too small to change the part is refused The blend's tangent angle is the shaded view's half degree (smooth_edges::ANGLE), one value for smooth. A constant round lies r (sec(d/2) - 1) inside the crease it replaces (about r d^2/8); below the edge's tolerance it changes nothing and is refused before SMLib (which answered SM_ERR_INVALID_INPUT), naming the smallest radius that rounds, tolerance / (sec(d/2) - 1). d is the least turn along the edge (tangent_edge::least_angle_along, at tangent_all_along's stations). Ruling d3 (2026-10-30). The block's tolerance is 2e-5 mm, not 0.1 um: at 1 deg the smallest radius is 0.526 mm, so R2 and R20 reach SMLib, which still calls an edge within 2 deg smooth (SmEdge::GetBlendEdgeuse); that test is ignored until SMLib uses 0.5 deg. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Fillet rig: the knife-edge chamfers name SMLib's cause, a cusp's ball radius of 0 smlib_chamfer turns the distance into a ball radius d sqrt((1 - c)/(1 + c)), c the faces' binormals' dot (capi chamfer_radius); at #851's cusp the binormals agree, the radius is 0 and the call is SM_ERR_INVALID_INPUT before the fillet executive runs (gdb: chamfer_edges sees radius 0; the dump's why is empty). SolidCraft hands every chamfer to SMLib, so the ball-contact chord (the ball of radius d: 3.822 wide at d = 2, 159.2365 removed) is SMLib's to build. Ruling d4 (2026-10-30). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * kernel tests: a corner round wider than its faces overflows and takes the corner's other edges R21 on a 20 mm cube's edge builds (6107.529370, closed form, to 2e-12). With R5 on the corner's other edges the R21 takes the faces they lie on, so the body is R21's alone; SMLib fails that blend (status 1001, fillet error 4, Unable to Trim Rail Curve) and the test is ignored until it builds. It replaces the refusal test that expected TooLarge. Ruling d8 (2026-10-30). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Tests: a 1 degree crease rounds, and the knife edge's chamfers build, on SMLib smlib-batch-4-rulings With SMLib's smooth limit at half a degree (422e6f1) the 1 degree crease rounds R2 and R20 (the test is no longer ignored), and with a cusp's chamfer the ball of radius d (d231547) the The 0.5 one stays, for its own cause (the chamfer face left apart from the body). Two corner cases the same SMLib (replay/1.0.1 and those commits) builds come off too. Needs SMLIB_REV at that SMLib once it is pushed. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * kernel, doc: an overflowing round goes first; an edge it removes is gone, and the fillet says so SMLib (smlib-batch-4-rulings 0e83cca, SMLIB_ABI_VERSION 5) rounds the edges whose rounds overflow their faces first and then what is left of the others; smlib_blend_dropping says which picks' edges the overflow removed whole. The smlib crate binds it (Brep::blend_dropping), the kernel returns those picks (fillet_removing), and a fillet notes them as its warning: "the edge at (0, 0, 10) was removed by the larger round, so it is not rounded" (a 50 x 50 x 20 block, R21 on its bottom front edge with the front left upright: the block is R21's alone, in closed form). Ruling d8: [21, 5, 5] on a 20 cube builds as R21 alone (6107.529370); the test is no longer ignored. R25 with R2 at a corner (blend_corner) builds the same way, R25's alone in closed form, where it was refused. The rig's 1080 notched block outline at R8 builds now and comes off the known-failing list. Needs SMLIB_REV at that SMLib once it is pushed. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Fillet rig: the knife edge's 0.5 chamfer builds SMLib's trim took a fillet meeting its face at more than 78 degrees for one with no side (smlib-batch-4-rulings 971e567); the chord of the knife edge's 0.5 chamfer meets the flat face at 81 degrees. The case comes off the known-failing list. Needs SMLIB_REV at that SMLib once it is pushed. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Tests: a 15° tapered text builds, every letter grown, exact where its outline gives it Owner ruling d6: the letter t of "tres long" was drafted inward by SMLib (its loop's normal, summed from the cross products of its chords, pointed down; fixed in SMLib). With the fix every letter grows, and the join builds at 3° and 15° by the Round rule and by the default rule (tangent for spline outlines), where before 15° was expected to be refused. Exact where the outline derives it: a letter's section at height z is its outline offset by e = z tan a, by the Round rule of area A + P e + C e² while the offset trims nothing (Steiner; C half each loop's turning less tan(t/2) - t/2 at each reflex corner), so the letter is A h + P k h²/2 + C k² h³/3. Each extruded alone, the t at 3° and s, l and o at 3° and 15° are checked to 1e-6 (SMLib measures them within 1.3e-9; its mass properties integrate to 1e-8). The concave joins of r, n, g and e are tighter than e already at 3° (their swallowtails trimmed: r 1.1e-3 under the formula), the t's by 15° (9.9e-5 over), and on the block the letters grow into each other, so the whole word is checked for what holds exactly: one closed body with the block, and half-way up every point of each straight letter's outline inside the solid (the t drafted inward failed that). With SMLib's fix (smlib-batch-4-text-loops 82133b2). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Kernel rig: a sloped basin's mitred rim rounds are checked tangent along their contact lines 1080-fillet-sloped-basin-1-mm-rim-r0-5-4-edges asked G1 at every blend seam. Its front wall leans 19 over 20 and the others 10 over 20, so at each rim corner the two mitred rounds meet the sloped corner edge at different heights (0.155625 and 0.276393 below the top): the deeper round runs on past the corner edge and is cut by the plane of the other's wall, a crease by construction, the gap below the shallower round filled on that plane. The check now measures the rounds' contact seams, on the top and on each wall, where the rounds are tangent. The volume is unchanged. With SMLib smlib-batch-4-mitre (1c15364): the case passes (V 144530.427946 against 144530.427909, 15 faces, sound); before it, only the four corner creases failed the check. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * smlib: Brep::classify_point says exactly where a point lies against a body Binds the fork's smlib_brep_classify_point (SmBrep::Point3DClassify at the body's own zone tolerance): inside, outside, or on the boundary within that tolerance of a face, an edge or a vertex. A box and a cylinder just off its curved wall in measure's tests. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01NvoxKQ2rEZvcXNQnhE3Sgs * kernel: Body::classify_point decides inside, outside or on the boundary exactly SMLib's point classification at the body's own tolerance, on the exact faces and edges, in place of a mesh at a chord of 2e-3 of the body's size (about 0.4 mm on a 200 mm part). A point within the tolerance of a face, edge or vertex is OnBoundary, never decided by a ray. A mesh body's triangles are its exact shape: on them within the record's tolerance, else by ray crossings. The kernel's own probes move to it; Body::contains goes once its last callers have. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01NvoxKQ2rEZvcXNQnhE3Sgs * doc: a hole decides whether it exits at its drill point's shoulder exactly Material past the depth needs a body with the point inside, air before it needs every body to have it outside; a point within a body's tolerance of the exit face is neither. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01NvoxKQ2rEZvcXNQnhE3Sgs * engine tests: probes ask for the exact point class Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01NvoxKQ2rEZvcXNQnhE3Sgs * ui, cli tests: probes ask for the exact point class Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01NvoxKQ2rEZvcXNQnhE3Sgs * kernel: Body::contains, the mesh test, is gone Every caller asks Body::classify_point now. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01NvoxKQ2rEZvcXNQnhE3Sgs * kernel tests: the rim chamfers running off their rims build, on SMLib 737c392 chamfer_wider_than_sloped_basin_rim_builds and a_rim_loop_chamfer_running_off_its_rim_builds waited for SMLib to build the cliff overflow (CloseRemovalRegion refused it, SM_FILERR_NO_ROOM). The pinned SMLib builds it (eddf0ede4, bba9914b6): both pass on aarch64 Linux and are no longer ignored. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Fillet rig: the cases SMLib 737c392 builds come off the known-failing list The gate on aarch64 Linux reports 16 fillet cases FIXED with the pinned SMLib: the sloped and equal-slope basin rim chamfers and rounds past their rims (1080-*, 5835-*), the pocket rim chamfer past the floor, and the three pocket rim rounds now mitred at the pocket's corners (every-pocket-*). No other area's gate reports a case fixed. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * kernel: the re-blend's removed picks formatted as rustfmt lays them out Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * kernel: blend_smlib laid out by the 2024 edition's rustfmt Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Skills: the tests skill's unit-test example stays under the 3600-character limit Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Fillet: the radius-too-large choice in plain nouns "If too large: Stop and say so / Largest that fits / Narrow where needed" becomes "Face limits: Exact radius / Largest radius / Narrowed radius", in every language of the catalog, with the error and the tip that name them. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * kernel: a round that would cut through its wall into a hollow is refused The owner's rule of 2026-10-30: a round running past a rim of its faces into open air builds; one whose section would remove material through to a hollow behind its edge (a slit into the hollow, a cut through the part) is refused as too large, so the fillet names the largest radius that fits. Decided exactly in the section of a straight convex edge between planar faces: the round's centre is at depth r below both planes, and it opens where its arc uncovers a boundary point strictly inside the wedge with no material beyond it toward the centre (the body's exact point classification). Looked at: straight edges parallel to the round's (a hollow's corner), cylinders about parallel axes (a rounded corner), and a picked concave parallel edge's own round, which fills the corner. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Fillet rig: 1668's R7 past the inside corner is refused at 4 + 2 sqrt2 The round's centre (32 - r, 42 - r) leaves the hollow's corner (30, 40) outside its circle, opening the wall, where sqrt2 (r - 2) = r: the case expects the refusal naming 6.828. 2852's R30, refused naming 25.24, now passes too: both come off the known-failing list. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * xtask: known-failing grades a nextest junit report against tests/KNOWN_FAILING_TESTS `cargo xtask known-failing --junit PATH` reads nextest's junit (a file, or every .xml under a directory, so all of a run's junit artifacts at once) and fails on a test that failed and the list does not name, and on a listed test that passed (FIXED: take its line off, as the kernel rig's gate does). A listed test that did not run is neither, since a pull request tests only the packages it touches. The list has the rig's KNOWN_FAILING format (`<test> <cause>`, sorted, the rig's own parser), with `<test>` nextest's `<binary id>::<test name>`; `cargo xtask lists` checks it is sorted. The list starts empty. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * CI: the test jobs grade their junit against tests/KNOWN_FAILING_TESTS Native Linux tests and the GPU path test shards no longer fail on any failed test: nextest's "tests failed" exit (100) goes to `cargo xtask known-failing --junit`, which fails on a failure the list does not name and on a listed test that passes. Any other nextest exit (a build error, a bad filter) still fails the step at once. The tests skill says to list a failing test with its cause, in place of ignoring it. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Tests: the known-failing list takes develop's 10 failing tests Develop 38fd4a4f6 (CI run 41157648345, after the SMLib eaa998a pin) fails 10 cargo tests; each is listed with the cause its failure message gives. Seven are SMLib refusals or results off their derived volumes (fillet, chamfer and shell), the cli action matrix and naming corpus among them; the two corner_g2 tests are the fitted G2 corner patch bulging past the box, which the explicit G2 corner fixes. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Reference tests: the eight cases that fail on SMLib eaa998a name their cause as known failures Develop 38fd4a4f6's Reference tests fail 34, 35, 77, 78 and 81 (STEP export finds fillet edges 4.6e-5 to 6.1e-5 off their surfaces against 2e-5), 37 (the apex blend 0.193 off), 80 (the taper-to-fit area) and 83 (thicken status 1001). Each expected.json names its cause in known_failure, which the oracle already reads: a known failure that passes fails the job. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Sweep path: a curve of several pieces is turned round whole The path chain oriented its first piece, not its first curve: a first curve of several exact pieces (a fit spline, an ellipse, a projected free-form edge) was never turned round, so a path whose next curve meets it at its start was refused as "not connected end to end". The chain now orients curve by curve: the first runs toward the second where they meet at one end only (else from the end nearest the profile), each next one starts where the previous ended, with one joint tolerance for both questions. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * SMLib: pin 2fc375f (tangency-labs/smlib#71, #72, #73) A sheet's side is extended exactly the distance asked, or the call says it cannot (#71); NVIDIA's -Werror build passes again (#72); a body splits by a sheet of several faces as it is, smlib_split_body_by_sheet (#73). The C API is ABI 6 (the new entry), so the binding expects 6. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * kernel: Extend grows a surface of several faces face by face A surface body of more than one face (a fit-point spline's spans extruded, #3830) was refused. Each face with a picked edge is now extended alone by SMLib's extension of its surface, and the faces are sewn back together, each the face it was. A side that lengthens onto a face meeting it tangent takes that face along, past its edge continuing the picked one; across a crease the neighbour grows only when its edge is picked too, otherwise the extension is refused. Faces whose lengthened sides no longer meet are refused. Up to a target keeps the pieces every grown face lies in. 3830's extensions now build; its split still fails (the tool point picks one span, and a face tool cuts with that face's surface alone), so it stays on the list with that reason. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * kernel: Split Body by a face of a smooth sheet cuts with the whole sheet A face tool cut with that face's surface alone, so a face of a surface body made of spans joined tangent (a fit-point spline extruded, #3830) cut nothing where its span ends inside the body. Split Body by a face of a surface body now takes the faces joined to it tangentially (the exact check Extend uses, within the one angle for smooth) and slices with them as they are, through SMLib's slice by a sheet (smlib_split_body_by_sheet, tangency-labs/smlib 7a01f1b), its sides those of the picked face. A sheet that only nicks the body cuts nothing, as before; a lone face, or a face of a solid, still cuts with its surface extended. 3830 comes off the booleans list. Its answer counted the two halves of the cup and not the surface that cut it, which stays as a body of its own (4879 removes its surface for that reason): three bodies, the volume unchanged. Needs SMLib 7a01f1b pinned (SMLIB_REV, prebuilt; its SMLIB_ABI_VERSION 6, which crates/smlib now expects) to link. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Tests: a cylinder strip's run-offs are 100 pi + 100 to 1e-6, SMLib's exact area The tangent and curvature run-offs of the quarter cylinder r 10 strip, 5 across the surface, are its section swept 20 along z: exactly 10 pi/2 20 + 5 x 20 = 414.159265. measure is SMLib's integration on the exact surface (1e-8), not a mesh, so the run-off check is 1e-6 relative and the 'measured on meshes' notes go. Red until SMLib's extension is solved to its distance (smlib-extend-converges 590d8a1): eaa998a's curvature run-off is 4.986 long, area 413.882. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * kernel: an extension SMLib cannot make exact says so, naming the length asked Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Sketch: a control spline can carry its own knots and weights A sketch spline over control points was always the clamped uniform B-spline over them, so a free-form edge whose knots are not evenly spaced (or whose weights are not 1) could only come into a sketch as one curve per Bezier span. A control spline now may save `nurbs`: its clamped knots and its weights. Its points, polyline, exact pieces (one a knot span; conics for a rational quadratic), the solver's distance and curvature, links, parallel re-projection and inspect.sketch all read them; a loaded design's are checked. One pending format file (spline-knots). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Sketch projection: a free-form edge comes in as the one exact spline it is A projected spline edge of several Bezier spans came into the sketch as one curve per span (#1508), so a G2 round's bottom edge was 16 curves and a path naming the corner named one span of it (#3604). The kernel now reads such an edge (a spline, or an elliptical arc of several spans) as the one clamped B-spline it is over the edge's interval, its knots and weights its own, and the sketch takes it as one control spline whose ends sit on the edge's vertices. Planar regions still read edges span by span. The 3604 case builds with its original path and leaves KNOWN_FAILING. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Fillet rig: blends past an outer rim of their faces build, on SMLib smlib-blends-past-rims The owner's ruling: a round or chamfer that runs past an outer edge of its face into open air builds, tangent where it has room and cut by the face beyond where it runs out. SMLib's branch smlib-blends-past-rims builds them by the rig's analytic answers. Off the known-failing list: the disc's rim past its 2 mm wall (190), the hole's top rim R12 past the plate's bottom, the chamfer past the cylinder's bottom (2893), each closing on the wall continued as itself, and 926's chamfer ending on the boss's wall, which now builds to its answer too. The sloped basins' R4 rim rounds (1080, mitred rounds built together where one overflows) build to their analytic volumes (to 6e-9), and stay listed with that reason: their continuity check (g1 at every blend seam) takes in the mitres' creases, G0 by the mitre ruling. 2893-chamfer-two-distances-elliptical-rim is graded as a solid (the owner: it builds) and stays listed, waiting on the ruling on unequal chamfers along a rim whose angle varies. 5158-fillet-round-just-past-a-10mm-face stays listed with its cause found: the round passes 5e-6 under the box's top back edge, inside the body's tolerance. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Naming: test that a round of a round's end has no seam with that round's faces The r1 round of a block's top edge, chained onto the end curve of the r2 round of its arc at a cylinder (rig fillets/every-block-cylinder-crease- top-edge-after-arc-round-r1), ends where it runs into the cylinder. That edge is no seam of the r1 round: the cylinder is a face of the r2 round, not of the r1. blend_seams takes it for one today (the r2 round's name F3:blend:F1:+z|F2:side holds a | of its own), and the rig reads it as a contact seam at 60 degrees. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Naming: a blend's seams split its edge's name at the | between its two faces A blend face's name holds the edge it replaced, <face>|<face>, and a side of that edge can be a blend face whose own name holds a |. Whether a face is a contact of the blend was read as the edge's name starting or ending with the face's name next to a |, so the r2 round's own face F2:side read as a contact of the r1 round F4:blend:F1:+y|F3:blend:F1:+z|F2:side. The edge's name is now split into its two faces, a blend side read whole as the two faces of its own edge. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Fillet rig: five refused blends build, off the known-failing list 926 (the chamfer ending on the boss's wall), the oblique cut's r0.1 round, the every-block r1 round (its seam with the cylinder is no contact seam, after the blend_seams fix), the up-down squares' concave chamfers and the shelled box's lip chamfer build with SMLib branch smlib-blend-refusals (f8650b8 and later). 1207 r0.5 passes SMLib's check on its rails now and stays listed for the next cause: its end rib on the boss, which starts where the round and the boss are tangent. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Kernel rig: the trough and the pocket whose floors fall to a drain build SMLib now offsets a vertex where four faces meet (two walls and two facets at the floor's corners, four facets at the drain) to two vertices joined by a new edge (tangency-labs/smlib branch smlib-shells). Both volumes match their closed forms. The pocket's lining, hanging from the top's rim round the pocket, stands apart from the slab's outer walls with the cavity rising between them to the open top: the case says two shells in the one body. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Kernel rig: the plate with a hole through its arc side shells open at its far end SMLib's merge now intersects the offsets of an edge's faces where they could not be mated along it (the hole's offset poking out through the half-round side's; tangency-labs/solidcore#1795): one closed valid solid with the one face open, as the owner ruled. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Kernel rig: the ring cut frame and the up-down join shell SMLib's inset now keeps only the regions that are cavity, not the one the offsets close where they overlap (between the two faces of #545's 0.5 floor, round the up-down join's two empty octants). The frame's core under the recess is hollowed to a sealed void, so the case says two shells and its closed form, 21044 mm³. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Kernel rig: #616's lid shells open at a rib's side, with the 0.15 lip SMLib keeps the skirt top's offset where its loops wind the other way under the opening, the cavity's floor (the owner's ruling of 2026-10-31: build it; a lip thinner than the wall is no break-through). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Known failing tests: the action matrix's shells and chamfers as they fail with SMLib batch 7 The ring cut frame's and the up-down join's shells build now, and so do the up-down join's and modern-plastic's chamfers (SMLib smlib-blend-refusals). #616's lid in the corpus still fails SMLib's loop check, the shelled box shelled again at an inner wall is unchanged, and the oblique cut of a cylinder's fillet still fails SmSurfOfRevolution's Test #7: 3 actions of 7. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * SMLib: pin 26cc451 (batch 7: rounds past a rim, blend refusals that build, shells) Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Known failing tests: the shell after a cut whose end touches an arc side builds on SMLib batch 7 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Surface fair test: the energy falls strictly, the face moves, and the edges are read after the fair Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Sketch scaling test: the first dimension sets l1 to 40 and scales both joined rectangles about the origin Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Frames tests: a pick on a moved component or an instance removes the exact round and bore volumes Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Issue 1080 tests: the rib's rounds and the mitred corner chamfers and rounds have their exact volumes Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Engine tests: lip_after_boss checks each lip's and groove's exact band, hole_as_deep_as_the_plate each hole's exact bore Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Robustness tests: lip_after_boss and hole_as_deep_as_the_plate live once, in the engine's tests.rs with exact volumes Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Engine tests: loft_cut goes; loft_spacing's hollow elbow covers its section counts and more Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Kernel loft test: the square-to-circle loft has the oracle's exact ruled volume, without printing Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Tessellation lens test: the lens's triangles fill exactly the rhombus through its arcs' midpoints Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Pattern test: six chamfered holes take exactly five more holes' bore and chamfer rings Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Kernel pocket floor fillet test: the corner rounds and the floor loop round add their exact volumes, by Pappus at the corners Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Shell regression: the saddle-corner shell opened on the top box's side has its exact volume Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * SMLib history test: every operand's order is the identity on its record's faces and edges Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Boolean history tests: the SMLib module's box-minus-sphere, box-minus-cylinder and box-union-box copies go; the top-level ones check more Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Modify history tests: shell, offset and thicken are one test each through the public API, with the volumes, refusals and history the SMLib copies checked Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Chamfer history test: the chamfer after each box cut is exactly one face on the painted block too Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Grid test: a pole side's face is the five triangles fanned from its one grid node, none degenerate Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Kernel tests: the twelve ignored print-only debug tests and surveys go; coplanar_curved_booleans checks the flush-capped cylinder cuts and unions they printed Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Kernel: the #883 board fixture generator is an example, not an ignored test Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * STEP import test: a seam sphere whose meridian stops short of the pole imports as the whole 2 mm ball Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Material tests: the nine copies in material_properties go; the persistence file checks the library copy's card and formats 20 and 21 in one loop Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Sample test: one loop checks every sample builds cleanly and without a panic; the robustness copy goes Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Known failing: the non-antipodal seam sphere import, refused for a loop of no (u, v) area Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Tests: rustfmt the board fixture example and the coplanar asserts Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Kernel rig: the two 3871 cone cases were byte-for-byte the 258 cases; the 258 cases carry their sources Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Kernel rig: a volume or area can be graded as a hand-derived range where analysis only bounds it Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Kernel rig: fillets keeps one case per regime; 17 replications of a case in the same regime go The sloped-basin chamfers and rounds at 0.5 mm rims repeat the 1 mm rim's regimes; two of the three knife-edge chamfer tips, the r1 and box r3 curvature corners, the r1 tangent corner, the 1 mm pocket-rim and hole-rim chamfers short of the floor and the r1 together-round each repeat a kept case's regime and grades. #854 moves to 851-chamfer-arc-top-edge-9-5, and the cases that cited a dropped one cite the kept one or state its formula. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Kernel rig: five cases outside fillets repeat a kept case's regime and go A square cut is the slanted plane's ordinary crossing; the cam's half turn is the quarter turn's contact at a symmetric angle; the r15 slab stands inside the same coincidence tolerance as the r10; the 90 degree unfold and the 40 degree flange repeat the 72 degree and 20 degree cases' formulas. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Kernel rig: 3243 rim and tooth join graded on its volume (rim plus the trimmed tooth less their 0.01 mm overlap) Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Kernel rig: 3782 emboss on a cylinder graded on its volume, area, faces and box (the wrapped 4 x 5 badge raised 1 mm) Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Kernel rig: 3604 G2 swept-tool cut graded on a volume range (filleted box minus the swept corner section) Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Kernel rig: 4505 coil joined through a cylinder wall graded on its volume, area and box (cylinder plus the wire's screw-swept segment outside r 76) Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Kernel rig: 4879 window cut through a thickened spline revolve graded on a volume range and its faces Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Kernel rig: 4623 join of crossing pleated loft skins graded on its volume and box (both skins less their overlap) Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Kernel rig: 831 tapered glyph extrude graded on a volume range and box (the font's S drafted in by 10 deg) Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Kernel rig: 2357 ring of 90 cylinder segments graded on its volume and box (the segments less their 90 joint overlaps) Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Kernel rig: 4542 fluted wall joined on a revolved base graded on its volume and box (the base by Pappus plus the fit-spline ring) Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Kernel rig: 1985 and 2243 STEP-export enclosures graded on their volume and box (the outline less the cavity, plus gusset and standoffs) Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Kernel rig: both 4092 loft, ribs and pad unions graded on their volume and box Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Kernel rig: 1525 graded on its volume (the convex body's exact 2 mm inward offset), faces and box Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Kernel rig: 1494 graded on its volume (box and cylinder less the 1 mm-offset cavity, sharp to rounded concave edges) and box Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Kernel rig: 4492 graded on its box and a volume range (the face's 19 mm sweep added, within the block's sides) Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Kernel rig: 745 graded on its volume (the end moved 1 mm plus the spline boss's exact area), faces and box Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Kernel rig: 4567 graded on its volume (the revolved spline less its revolved 2 mm offset), faces and box Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Kernel rig: the up-down squares shell graded on its volume (the columns less the 0.346 mm-offset cavity, sharp to rounded concave edges) and box Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Kernel rig: 545 graded on its volume (the frame less its 0.5 mm-offset cavity, sharp to rounded concave edges), its sealed pillar void and box Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Kernel rig: the shell-again case graded on its volume (the shelled box less the 0.5 mm-offset cavity in its walls) and box Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Kernel rig: the arc-sided plate shell graded on its volume (sharp to rounded at the hole's bottom), faces and box Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Kernel rig: 616 graded on its volume (the lid less its 0.5 mm-offset cavity, sharp to rounded concave edges) and box Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Kernel rig: 391 graded on its volume (the shelled housing, sharp to rounded at the flange, less the letters' 0.6 mm deboss) and box Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Kernel rig: shell/3576 was the ladder's drafted box with rounds shelled, recipe for recipe; the ladder case grades it and carries #3576 and #3573 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Kernel rig: the two 851 chamfers of 2 graded on their volume (the cone's sweep, and its union with the front edge's prism) Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Kernel rig: the chamfered corner of the lipped shell graded on its volume (the chamfer's triangle through the wall) Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Kernel rig: the concave round into the peg's cylinder graded on a volume range (the torus it must add, the band it can't leave) Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Kernel rig: the two folded 72 degree trays graded on their volume (flat area x thickness) and the walls' reach Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Kernel rig: the flanged rhombus graded on its volume (flat area x thickness, all four reliefs cut) and its walls' ends Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Kernel rig: the base with two adjacent flanges and a hole graded on its volume (base, bends and panels folded) Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Kernel rig: the flange beside the ledge graded on a volume range (the flange's two readings of its length) Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Kernel rig: the two G0 window patches graded on the box the part they close keeps Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Kernel rig: the hub's six swept grooves graded on its volume (the revolved hub less each tube's part inside it) Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Kernel rig: the cut mirrored loft graded on the box its sections pin Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Kernel rig: the three modelled-thread joins and the fine M48 graded on their volume (the basic profile's groove, Pappus) Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Kernel rig: the oblique-cut round graded by its seams (tangent, not curvature-continuous); the flanged rhombus says what it tests (its reliefs stay apart at 60 mm) Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Kernel rig: 3841 is 168's rim touching its coin along a circle, and 4092's reduced recipe is its report less a flange clear of the failing join; the kept cases carry their sources Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Kernel rig: the oblique-cut round keeps its old grade until the new blend algorithm lands Its seams grade needs the continuity check to skip the body the round is not on. Fillet cases wait for the new algorithm. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Kernel rig: 1985's enclosure is 78 x 77 (74 and 73 inside, 2 mm walls); its volume 38063.827 by hand Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Kernel rig: the three spline walls' face counts wait for the one-wall decision; their volumes grade them Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * STEP import: a face bounded by seams alone runs its loop the other way, never turns over A loop that uses each of its edges once each way (a whole torus within its tube and ring seams) is the same set of uses run backwards, so it says nothing of the face's side. One written clockwise in (u, v) turned the face over, against its same_sense: the torus came in inside out with a warning. Such a loop is now reversed and the face keeps its side. Test: seam_only_torus_imports_as_a_whole_ring, both orders of the two seams, volume 2π²Rr². Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * STEP import: a face bounded by a slit alone is the whole of its closed surface A loop that runs out along a chain of edges and straight back (a meridian from a sphere's pole stopping short of the other, out and back) encloses no (u, v) area, yet on a closed surface it bounds all of it less a cut of none. The reader only read such a face when the slit already ran pole to pole (and moved the sphere's frame onto it only then), so the 2 mm ball whose meridian stops at 2.5 rad was refused for its empty loop. The slit is now made the face's seams, so its loop bounds the surface's whole domain: on a sphere, a revolution whose profile ends on its axis, or a spline closed round u that collapses at both ends, the slit's meridian is run on to both poles, out and back (a sphere's frame put on the slit first, whichever two points it joins); on a torus, the circle the slit lies along is closed and the other circle through its start is the second seam. The seams on a sphere are its own meridians (angle 0 on the equator), so their pcurves are exact lines on its form. Tests: non_antipodal_seam_sphere_imports_as_a_whole_ball passes (its known-failing line goes); seam_only_torus_imports_as_a_whole_ring adds a torus bounded by a slit along its tube. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Rig: the test-peg's concave arc and front top edge rounded together stay within the body's box A new fillet case, report-fillet-concave-arc-and-front-top-edge-together-solver-residues: the reported part's bar (with the sketch solver's residues) whose sides run tangent into the cylinder, its concave arc and front top edge rounded r2 together. The plane of the front face bounds the whole body, so every blend lies within the unblended body's exact box (SMLib's tight box); graded to 4e-5, the corner patch's own tolerance. On SMLib 2fc375f the corner patch stands 0.0374 out of the front face (box y min 0.0205): listed in KNOWN_FAILING. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Rig: the test-peg corner at r5 and r7 Two more fillet cases, the reported part's concave arc and front top edge rounded together at r5 and r7, with the same exact-box containment check (graded to 4e-5, the corner patch's tolerance). On SMLib 2fc375f the corner patch stands 0.128 (r5) and 0.230 (r7) out of the bar's front face (box y min -0.0699 and -0.1723): listed in KNOWN_FAILING. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Rig: blends that end where their face runs tangent into another Fifteen fillet cases on the test-peg's shape with clean numbers: a bar 40 x 16 x 10 whose far end is a half disc R8, a disc R8 standing 10 on its top, joined, so the front face runs tangent into the cylinder along x = 40 and the front top edge (convex) meets the concave arc of the top tangentially there. Each blend ends on a face tangent to the one it rolls on. - Rounds: both edges together at r2 and r5; one after the other in either order at r2, and at r1.5 and r3; the front edge alone as a curvature round, whose end on the cylinder is a semicubical cusp. The containment invariant (the unblended body's exact box, to 4e-5) and G1 seams, or the analytic volume where the blend has a closed section. - Chamfers: the front edge alone and the concave arc alone (analytic volumes: the section along x up to the wall, the cone's spandrel ring clipped by the sides), both together, and one after the other (1 then 2). - STEP: the peg written to STEP and read back, its front edge rounded (analytic) and both edges rounded together. - A cone: the peg drafted 5 deg, whose front face runs tangent into a cone along a generator, its front edge alone and both edges together. The quadratures are tanh-sinh, converged to 1e-13; SMLib's own volumes of the passing analytic cases agree to 4e-9. A sphere is left out: a plane meets a sphere tangentially at a point, not along a seam, so it is not this ending. On SMLib 2fc375f eight fail, listed in KNOWN_FAILING: every chamfer that ends tangent (status 1001, SmFilletNx1Corner), the two rounds together (the corner patch 0.0374 at r2 and 0.128 at r5 out of the front face, and the rounds meeting with normals 180 degrees apart where their contact lines on the top cross), the same on the STEP-read peg (status 1001) and on the drafted peg (its corner refused as unsupported). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Rig: fillet corners graded curvature-continuous, the default to be Six fillet cases that pick their edges with no type, so they take the fillet's default, which the owner has ruled is to be curvature-continuous (G2) at every corner, with circular rounds kept as an option. Each grades every seam of the rounds and of the corner patch G2, on one valid body: - an oblique convex corner (a block drafted 15 deg); - a four-edge and a five-edge apex corner (pyramids lofted to a point); - a pocket's concave corner; - a mixed corner (a step: one concave edge, two convex); - a corner beside a cylinder (the top corner of a half cylinder). All six fail on SMLib 2fc375f, listed in KNOWN_FAILING: today's default is the circular round, whose seams jump in curvature by 1/r. On the five-edge apex the corner patch also meets two rounds at 8.45 degrees (G0). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Rig: the test-peg's front chamfer builds With the SMLib fork's smlib-tangent-ends (a rail's end on its side edge is the rail/edge crossing), report-peg-front-chamfer-d2 passes. Its line leaves KNOWN_FAILING, for the pin that carries that fix. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Rig: the curvature-continuous corner cases pick the curvature fillet The six corner cases added in 3a854104a took the fillet's default type, on the premise that the default would become curvature-continuous. The default stays the circular round, so each case now asks for the curvature fillet itself (type curvature: curvature-continuous sections and corner patches) and keeps its grading: every seam of the rounds and of the corner patch G2, one valid body. They are renamed from cov-fillet-g2-default-* to cov-fillet-g2-*. The oblique three-edge corner (a block drafted 15 deg) and the pocket corner pass. Four fail, as KNOWN_FAILING now says: - the corner beside a cylinder: the curvature fillet builds its sections only between planar faces; - the four- and five-edge apex corners: refused because the default setback is shorter than where the rounds' contact lines meet (3.90 and 3.51 mm from the apex); - the mixed corner: SMLib sets back a corner only where its edges are all convex or all concave. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Rig: the test-peg's concave chamfer, alone and after the front chamfer, builds With SMLib's tangent end as an event of the fillet's trace (blend-end-event 6d73e4f), the concave chamfer's rail on the cylinder ends where it crosses the seam along which the front face runs tangent into the cylinder, continued past the vertex, and its end rib on the front face is built from there. report-peg-concave-chamfer-d2 and report-peg-front-chamfer-d1-then-concave-chamfer-d2 pass and leave KNOWN_FAILING. The two chamfers together still fail, now at the mixed-convexity corner where they meet: its line says so. Rig against SMLib 0cc48bd: no area regresses (963/993 pass, 961 on a87c502), ladder 168/168, kernel lib only its listed failures. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Kernel rig: constant rounds of the exact classes, and a tee's round A plane cutting a cylinder or a cone at an angle, a sphere or a cone coaxial with the other face, a cone and a cylinder touching one ball, two pipes touching at a point: their rounds' centre lines are rational, so the rounds are rational surfaces of degrees fixed by the construction ((4, 2), (2, 2) revolved, (6, 2), (12, 2)). The tee's centre line is not rational; its round is graded on its volume. Volumes from the divergence theorem over the exact pieces, at rel 1e-6. The six that SMLib 0cc48bd traces are listed in KNOWN_FAILING with what they come out as. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Kernel rig: the exact-class rounds pass on SMLib's classified exact rounds The rounds now come as the rational surfaces their classes give, closed ones as two faces split at their seams, the touching pipes' as four: one splines entry a face, each of the class's degrees. Their KNOWN_FAILING lines go. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * SMLib: pin 7ac037e (the new blend's tangent-end event, zero-speed G2 ends, and its exact-class rounds) Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Kernel rig: the fillets known-failing list is the 22 cases that fail on SMLib 7ac037e Twelve listed cases build on the new blend's end event and exact classes, or were already built on develop: they come off the list. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Kernel rig: #316's bottom rounds as large as the wall, or larger, shell with a step wall at the opening, not refused Where the round meets the open bottom the cavity's wall steps down along the bottom's normal, so the round meets it at 90 degrees and the opening is exactly the picked face. The cases are renamed and graded on the exact volumes, and come off the shell known-failing list. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Merge fixes: every crate and test target compiles on the merged tree, but for crates/geom's hlr world_state, view::bounds, home_camera and scene return Result on develop; new main code takes that with ? or session_world. New fixtures carry the spline's nurbs. ForeignCopy::of returns Result. occurrence_placement_with walks the path with its moves, since the placement index holds pending_moves only. The hlr port is separate and still to come: this commit does not compile as it stands in crates/geom/src/hlr. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01MNXLXkZLQ6T7TSi4wswcmk * Drawings hidden lines: read develop's B-rep records Edges come from the record's edge list, cut to their interval (C3::of_edge), and faces from its face list; a cylinder, cone, sphere or torus chart takes its bounds from where its NURBS form lies on its label (S3::of_face). A rigidly placed revolution has main's revolution chart; other placements stay refused. Moving a body to its centre goes through Brep::moved. Loops are read against the natural normal of the face's parameters where a chart wraps. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01MNXLXkZLQ6T7TSi4wswcmk * Hidden-line fixtures: build develop's records from the fixtures' data Fixtures keep their bounded curves and surfaces and their own edge numbers; a private builder makes the canonical record, and the local prepare puts the edges back in the fixture's numbering. Assertions are unchanged. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01MNXLXkZLQ6T7TSi4wswcmk * Hidden lines: tests of the bounded edges, face charts and placed revolutions Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01MNXLXkZLQ6T7TSi4wswcmk * drawing-hlr doc: what is drawn and refused on develop's records Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01MNXLXkZLQ6T7TSi4wswcmk * hlr tests: a placed revolution is refused when its placement is not rigid The new model has one record for main's Revolution, which was drawn, and its PlacedRevolution, which was refused. An identity placement is now the former, so this test's fixture takes a non-rigid one. The refusal it asserts is unchanged. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01MNXLXkZLQ6T7TSi4wswcmk * Hidden lines: a traced intersection is drawn only where its spline lies on both surfaces A leader off either surface is refused like a curve with no spline to follow. Tests: a traced rim drawn on the circle and plane within tolerance, the same leader 1 mm off refused, and kernel bodies with arcs through the production prepare against closed forms. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01MNXLXkZLQ6T7TSi4wswcmk * Hidden lines: kernel bodies through the production prepare against closed forms Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01MNXLXkZLQ6T7TSi4wswcmk * Tests from main: the world state is a Result here Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01MNXLXkZLQ6T7TSi4wswcmk * A blend's pick measures close edges on their curves, not their polylines A polyline can be a chord off its edge, more than two edges are apart near a tangent point. A pick exactly on a ball's rim took the straight edge the rim is tangent to, and solidcore built a chamfer of that edge with a clean check. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01MNXLXkZLQ6T7TSi4wswcmk (cherry picked from commit c786db6bf49804fb83a02f0eb7f83bd9f82fa643) * Merge fixes from the first SMLib test pass Model cache key covers the crates develop's kernel adds under doc (profile, smlib, step). A piece taking a name also takes the feature that made it: SMLib lists a cut's pieces in another order, and the swap left the name on a piece of the wrong feature. A replaced analysis keeps its status slot. A command with no world picks does not place the model first, so assembly.mass_properties answers for a flattening placement. FeatureCommon loses the touching key the merge added; only the contracts that read it take it. Two of main's tests listed as failing on SMLib, with why. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01MNXLXkZLQ6T7TSi4wswcmk * Merge fixes from the ui test pass and the gates Main's thread.direction keys go with develop's thread hand, which replaced them. Vietnamese for the messages develop added while main made vi a complete catalog. CGA and 1-bit themes set develop's comb and section hatch colours. A ribbon button with a persistent effect is pressed only while its tool runs, so persistent_ribbon_pressed alone decides how its effect is shown; other analyses stay pressed while on. Two of main's ui tests listed as failing on SMLib, with why. Gates: fixed thread tables become slices, one collapsed if, rustfmt. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01MNXLXkZLQ6T7TSi4wswcmk * A silhouette takes its facing from the surface's normals A flat triangle beside the outline can tip the other way from the surface it approximates, and its edges joined the outline. On SMLib's sphere that made 192 segments instead of the equator's 64, 100 curves and 95 profiles from the tight fit of #7989. Each corner's normal is used where it is close to the triangle's own; a mesh without such normals (none, zero, not numbers, or averaged across creases) keeps the triangle's normal, as before. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01MNXLXkZLQ6T7TSi4wswcmk * Clippy and rustfmt on the merged tree Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01MNXLXkZLQ6T7TSi4wswcmk * Stepwise open checks every feature under the session's mode OpenSteps::start evaluated under the default check mode, and finish kept those results under the session's mode: an each_step or off session opened in steps recomputed nothing. start now takes the mode (the app passes its session's), and a mode that changed before finish evaluates the design again under the new one. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01SdcgEu4Lr3moCCisdZShKz * Clippy without SMLib: the planar-sheet edge reader is built only with it Its one caller is in the smlib-only sheets module, so without the feature it was dead code and clippy -D warnings refused the kernel. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01SdcgEu4Lr3moCCisdZShKz * SMLib: pin d01d7b0 (the new blend's one Gⁿ section generator: the chord, circle and curvature sections, and the variable rounds as the union of their balls) Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Kernel rig: the section orders, chord, circle and curvature section, on planes and against a cylinder Eight fillet cases for the blend's cross-section by its order of contact with the faces, each graded on its analytic volume at rel 1e-7 and its exact continuity (the order, and not the next): - a box's top back edge chamfered 3 (G0), rounded r3 (G1) and curvature-rounded 3 (G2): the areas cut off the corner s^2/2, (1 - pi/4) s^2 and 113/756 s^2, the last by the default thumbweight's definition; - a pipe R10 dipping into a plate, its concave edge chamfered 2 (the chord between the contacts of the ball SMLib rolls for that setback, radius 1), rounded r2 and curvature-rounded 2, each section's added area by Green's theorem along the plate, the section and the pipe's arc; the order-2 section is built from the faces' feet of the point at distance d from both, which on the pipe are not linear in d; - a boss root curvature-rounded 2, the square corner's section revolved (Pappus); - a variable round r1 to r5 along a box edge (rel 1e-5): the balls' envelope is a circular cone, and the volume is the cone's sections integrated along the edge. Three fail today and are listed: the two curvature rounds whose faces are not a square corner of planes (SMLib's quintic blend curve, not the order-2 section: rel 6.5e-7 and 1.2e-5) and the variable round (great circles, not the envelope's: rel 4.8e-5). The other five pass on SMLib 7ac037e. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Kernel rig: the curvature fillets' expected bodies from the order-2 section at thumbweight 0 SMLIB_BLEND_CURVATURE's section is now the order-2 G^n section at thumbweight 0. Between two planes square to each other it cuts A = 0.154192655384275 s^2 off the corner, its first moment about either face 0.0291753295725360 s^3 (Green's theorem on the section): the curvature cases built on that corner (862, 2708, every-box-edge, every-hole-top-rim, every-l-bracket, every-block-cylinder-crease, the three-edges-at-bar-corner reports, 3604's fillet) take their volumes from it by their own methods, the peg's front blend 23.3237146876 (its section along x up to the wall). Between planes the section's t^3 term vanishes (their feet are linear in the distance): the box edge case is exactly G3. The boss root is a certified fit, G3 to the plate and G2 to the wall at Continuity Analysis's tolerances: at least G2. The boss root and the pipe on the plate pass on SMLib's section and leave the known-failing list. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Curvature fillets: the section's default thumbweight is equal area, so the round's volumes are the circle's On the round's rails the order-2 section takes off what the ball's circle does: (1 - pi/4) s^2 at a square corner, first moment 0.0474559669443 s^3 (w = -0.5252123889). The kernel and engine tests and the curvature rig cases take their volumes from it by their own methods; the pipe on the plate from its own wedge (70.52878 degrees, w = -0.8544103493). The G2 corner patch's seam test is listed until the corner step. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Kernel rig: four G2 corners wait for the corner step: their patch meets the new section's rounds G1 at one face seam Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Kernel rig: the turn at a corner of two rounds, Mitre (the default) and Swept, at a pocket's floor and a boss's base, by exact volumes A round's spandrel A = (1 - pi/4) r^2 and its first moment about its wall M = r^3 (5/6 - pi/4): Mitre adds L A -+ 2 M per edge (cut at, or run on to, the corners' bisector planes), Swept turns the section about a convex corner's edge, (pi/2) M a corner, and refuses a concave corner rounded less than the ball. The pocket's tangent chain round its R3 corners is a torus each. Graded to 1e-7, where Mitre and Swept differ by 6.6e-6. The Swept cases are listed until solid.fillet takes a turn. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Kernel rig: a junction family: oblique wedges 30 to 150 degrees rounded and chamfered (exact), bosses upright and tilted, pipe tees and a Y junction Four are listed with their causes: the equal-pipe tee (its exact conic-pair rounds meet at the ellipses' crossings in a corner the old corner code cannot join), the tilted bosses (1001, before the blend rework too) and the Y junction (refused for room at its triple points). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Variable rounds: graded by the union of their balls (their envelope), not the balls' great circles The smlib crate's laws and ladder 005, 006, 007 and 012 take the volumes the balls' envelope removes; the law with a corner is its own test, listed as failing until the corner step. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Kernel tests: variable rounds graded by the union of their balls, the removed volume to 1e-4 of itself removed_by_balls integrates, in each plane square to a right-angled edge, the corner the union of the balls leaves (by rays from the edge, the least entry over the balls), cut to the body's section. The law with a corner through a middle point is its own test, listed as failing. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Kernel tests: a spline radius whose balls fold over one another at its peak is refused Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Kernel rig: the variable round on its cone passes (the round is the balls' envelope) Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Tests: three rounds of different radii at a corner listed: the corner's transition kinks with the balls' touch circles Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Ladder: the variable rounds graded to 1e-6 by the union of their balls; 012 by its law going on past the edge At the default 1e-3 the great circles' volumes (4e-6 off) passed too. SMLib builds each within 1.6e-7. The golden takes the new volumes and areas; counts unchanged. The G2 corner test listed as failing passes on SMLib's step 3 and leaves the list. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Reference tests: the variable rounds 77, 78 and 81 pass on SMLib d01d7b0; their known-failure marks come off The new section builds their edges on the surfaces, so STEP export no longer finds them 4.6e-5 to 6.1e-5 off. develop's Reference tests (60393a718) report all three as passing while marked. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * STEP import: a ball's halves whose seams are off each other's quarter lines each form within one turn A sphere split into two halves along a circle about its axis, each half covering a pole with no seam, gets a seam per half from the first vertex of its loop to the pole. The circles between the halves group their frames so they turn together, and when the two seams are not a whole number of quarters apart no one turn fits both: the group kept its frames, a half's form ran past one turn, SMLib's trim (SMLib and solidcore alike) across the form's end crossed the face, and the mesh folded over the ball (a rotor's ball showed torn; its half had 196 times its area in triangles). When no one turn fits the group, each spilling face is now turned on its own to start on a quarter line. On the rotor file this also clears three other faces that were filled leniently and a 0.076 mm edge gap; regression test in step_in/tests.rs with the area and volume of each half. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01SdcgEu4Lr3moCCisdZShKz (cherry picked from commit b3188e005d427043b918267449c2336a1777e54f) * SMLib: pin 5e8c9c1 (the new blend's corners: Ball and End/Join; exact fold and room checks with fit sizes; overflow in place; the round as its definition) Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DtL5M41G8Nua7HvuFPZkmJ * Kernel tests: a law's dip shows its corner ball's sphere, a peak's two rounds cross (the reasons had them swapped) Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Reference tests: the variable rounds 77, 78, 80 and 81 expect the union of their balls A variable round is the envelope of the balls rolled along the edge, which takes less than a quarter round in each section. The expectations are now that union, the law continued past the edge's ends along its end slopes, integrated by Gauss-Legendre panels in x and t; 2, 4 and 8 panels agree to 1e-9 of the body's values, and 77's removed volume matches a brute-force union of balls to 2.5e-10. The nearest-ball search now scans the balls the ray meets around ball x (|x - s| < r(s) sqrt(sin 2t)) on their own, which near the faces and where 78's radius closes to 0 are narrower than the global scan's step. Regenerating keeps each case's known_failure. 79, a constant radius, is unchanged. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Known failing: the law corners' kernel and crate tests and rig 1207 pass on SMLib 48ea616 SMLib builds a variable round's law corners as its balls' union (the corner ball's zone at a dip, the sides' crossing at a peak): the kernel's corner through a middle point (39.5410) and the crate's 4 -> 2 -> 4 law (39.5421) pass. Rig 1207 (the bar's top edge rounded after the boss's arc, r0.5) builds and grades on the same SMLib; it failed on c820346. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Kernel rig: every fillet and chamfer case rounds its tangent chain The owner's ruling of 2026-11-01: the rig and the ladder round with tangent_chain true, how a user's default pick behaves. The 38 fillets-area recipes and the ladder's 07-fillets/016 and 018 that passed false now pass true. The shell recipes keep theirs: a shell's tangent_chain is its open-face chain, a different feature. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DtL5M41G8Nua7HvuFPZkmJ * Kernel rig: the partial-selection cases kept as -partial-chain copies, tangent chain off Where a case's point is one edge of a tangent chain rounded alone, a copy keeps tangent_chain false as its own case (SMLib rounds exactly the picked edges, ending at the smooth vertex); their expectations stay as they were, to be re-derived: - fillets/1207-fillet-box-end-edge-into-unblended-round-partial-chain; - fillets/every-fillet-after-fillet-curvature-front-then-side-r3-partial-chain; - fillets/1207-fillet-bar-top-edge-after-boss-arc-round-partial-chain, renamed from ...-no-tangent-chain: with the chain on it is exactly 1207-fillet-bar-top-edge-after-boss-arc-round, which the rig already has; - ladder/07-fillets/020 and 021, the r5/r3/r7 and r5/r3/r2 corners (016 and 018) with the r3 on its edge alone: with the chain on, the r3 runs on along the r5 round's end arc and down the vertical edge the third round was to take. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DtL5M41G8Nua7HvuFPZkmJ * Kernel rig: the concave arc between the block's tangent sides kept with tangent chain off fillets/every-block-cylinder-tangent-concave-arc-r2-partial-chain: the pick takes one piece of the concave half circle, which SMLib splits; with the chain off its other pieces are left out, and the blend is refused at the piece's end (the base gate's outcome). With the chain on the case rounds the whole half circle. The copy keeps its expectation, to be re-derived. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DtL5M41G8Nua7HvuFPZkmJ * Kernel rig: two chains that now build graded by their exact volumes With the tangent chain on, two cases round more than the edge they pick, and their old expectations were the single edge's: - 1207-fillet-box-end-edge-into-unblended-round: the r1 chain is the end face's top edge, the r3 round's end arc and the back upright; 34 A + (pi/2) A (3 - c) by Pappus on the arc: V = 7953.139216 (it built 7953.139216, the old 7957.505 passed only inside 1e-3), 10 faces. - 851-fillet-top-front-then-front-left-upright: the upright's chain runs up the first round's end arc on x = 0 and along the left top edge, so the corner becomes the R2 ball's eighth: V0 less the first round's spandrel to the wall (35.344727) less 27 (4 - pi) + 2 pi/3: V = 9530.777979 (built 9530.777987), 10 faces. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DtL5M41G8Nua7HvuFPZkmJ * Kernel rig: a curvature chain round a round's end refused for its size; the concave half circle builds - every-fillet-after-fillet-curvature-front-then-side-r3: the side edge's chain runs round the first curvature round's end curve, whose radius of curvature has a weighted mean of 3 (its setback) and is unbounded at the ends, so somewhere below 3: the size-3 blend's contact line folds back on itself. Refused, "larger than the faces beside its edges allow", as ladder 07-fillets/016's r7 on the r5 arc. (It was solid or refused for running on tangentially.) - every-block-cylinder-tangent-concave-arc-r2-no-tangent-chain: the chain takes every piece of the half circle and ends at the convex edges it runs on into; it builds the analytic 19091.9620, so the outcome is solid (the refusal alternative was the chain-off one's). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DtL5M41G8Nua7HvuFPZkmJ * Known failing: two 851 chains whose corner piece is a ball of tube-centre radius 0 851-fillet-arc-then-top-front and 851-fillet-top-front-then-upright: with the tangent chain on, each R2 chain runs along the end curve of an R2 round on a curved face (the arc round's end on the front face; the first round's end on the wall), where the rolling ball sits on that round's own centre line, so the piece is the ball about (39.2538, -19, 8): the three-edge rolling-ball corner. SMLib fails with status 1001; the same piece on a plane end arc builds (front-left upright). Expectations unchanged. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DtL5M41G8Nua7HvuFPZkmJ * Ladder: 016 and 018 refused, their r3 chain takes the vertical edge; 020 and 021 recorded With the tangent chain on, 016's and 018's r3 runs on along the r5 round's end arc and down the vertical edge, so the third pick (60, 40, 8) is 3 from both of that round's contact lines and names no edge: refused, asking for a point along one edge. The corners they were made for are 020 and 021 (the r3 alone), whose golden entries are 016's and 018's (021 measured on f12a101). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DtL5M41G8Nua7HvuFPZkmJ * Kernel tests: three rounds at a box corner end on one rational patch on the ball's sphere, not an analytic sphere SMLib's Ball corner is always the rational patch exactly on the sphere (owner ruling, blend design §23), so the corner counts as an 'other' face beside the three cylinders and six planes. The removed volume still checks the corner against r³ − πr³/6. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DtL5M41G8Nua7HvuFPZkmJ * Kernel rig: the curvature round on a pipe on a plate is listed: a seam grades G3 where exactly G2 is wanted Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DtL5M41G8Nua7HvuFPZkmJ * Kernel tests: the box-and-fillet wire fixture records the round's cylinder frame as SMLib now keeps it The round's cylinder keeps the frame it was made on when it is turned (SMLib's SwapUV no longer re-derives it): its origin sits at x = −20 on the same axis line, (x, 2, 8) along x, radius 2. Same cylinder; one number in the record moves. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DtL5M41G8Nua7HvuFPZkmJ * Known failing: two kernel tests' reasons as they fail on SMLib 5e8c9c1 (a partial selection running into an unblended tangent edge) Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DtL5M41G8Nua7HvuFPZkmJ * Kernel rig: two curvature rounds get 600 s, past the 180 s default, while G2 certification is slow (tangency-labs/smlib#96) On the CI runners the boss root and the hole rim, both size-2/size-1 curvature rounds, build correctly but take more than 180 s: the order-2 section's span certificate and the round's definition are evaluated station by station. The per-case limit is the one the thread cases use. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DtL5M41G8Nua7HvuFPZkmJ * Lid ring sketch test: find the ring under the pick, not by main's kernel's name On SMLib the lip join's exact history names the lid underside's ring a piece of the lid's own start (F14:start#[...]), as the naming rule says for a face that came from the feature's input; main's kernel named it after the case's top it rests on (F2:top). The test looked the ring up by that name and so stopped before the attachment it guards. It now takes the underside piece under the pick point, which the cap certificate attaches on either kernel. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01SdcgEu4Lr3moCCisdZShKz * Viewport culling test: each box's triangles from its mesh, not 12 SMLib meshes a 10 mm box in 108 triangles, so the hard-coded 12 a box stopped the test before it reached the culling. The expected counts are now each body's span in the scene. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01SdcgEu4Lr3moCCisdZShKz * Timeline chip test: a fillet that really reduces The R20 fillet with fit reduce on one top edge of a 10 mm box builds on SMLib without a reduced-radius warning, so the fixture had no warned feature. It now rounds the four vertical edges at R6, reduced to the full round (5), as the copy-warning test beside it does, and checks the warning says so. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01SdcgEu4Lr3moCCisdZShKz * Oracle: 34-chamfer-then-fillet and 35-fillet-curved-curved pass on SMLib 5e8c9c1 (their STEP edges are on their surfaces) Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DtL5M41G8Nua7HvuFPZkmJ * Known-failing: the shell of a fully rounded box opened at one face fails on SMLib 5e8c9c1 (tangency-labs/smlib#102) Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DtL5M41G8Nua7HvuFPZkmJ * Known-failing: the action matrix's oblique cylinder cut fillet passes on SMLib 5e8c9c1; two shells still fail Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DtL5M41G8Nua7HvuFPZkmJ * Kernel rig: the boss root's curvature round gets the rig's 1800 s cap: on the CI runners, 8 cases at a time, its G2 certification passed 600 s (tangency-labs/smlib#96) Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DtL5M41G8Nua7HvuFPZkmJ * Kernel rig: a case's continuity can ask for an order per seam (seams: [{order, edges, exact}]) Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DtL5M41G8Nua7HvuFPZkmJ * Kernel rig: the pipe on a plate's curvature round meets the plate G2 and the pipe G3, 40307.8856312 (option B's order-2 jets, tangency-labs/solidcraft#10845) Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DtL5M41G8Nua7HvuFPZkmJ * Edge names: a seam names its one face once; the curve-id test reads every edge kernel-neutrally A seam's two sides are the same face, and edge names list each face an edge bounds once, so SMLib's extruded circle names its side's seam F2:side:c1, with no separator. The name grammar now says one face also means a seam. The #5858 test no longer counts one '|' an edge: every part of every edge name is a whole face name of the edge, one per face it bounds, two for the rims and one only for the side's seam (checked to run bottom to top on the circle). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01SdcgEu4Lr3moCCisdZShKz * rustfmt on the merged tree Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01SdcgEu4Lr3moCCisdZShKz * Known failing on SMLib: two of main's new tests assume truck's box mesh and fillet torus Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01SdcgEu4Lr3moCCisdZShKz * SMLib: pin f916a8d (a round on a definition face is its definition; the G1 setback fill certified convex, setbacks too short refused naming the least; the G2 certificate halves a span no level can certify at once) Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DtL5M41G8Nua7HvuFPZkmJ * Fillet: a setback too short for its corner is refused naming the least that builds (smlib_blend_fit_size) SMLib's setback corner takes a G1 fill only once certified convex, and refuses a setback too short for that as SMLIB_ERR_NO_ROOM with SMLIB_FIT_SETBACK_AT_LEAST, the smallest setback that builds. The kernel reads it (solidcraft-smlib binds smlib_blend_fit_size) and names it; the Fillet dialog says it in plain words. Other room refusals keep their words. The r5 box corner set back 5.5 is refused naming 5.962, which builds. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DtL5M41G8Nua7HvuFPZkmJ * Kernel tests: three rounds of different radii at a corner meet in SMLib's setback corner Each round runs whole to its section square to its edge at its setback (the owner's rule, at least 1.5 r, scaled to the least at which the G1 fill is certified convex), and the hole is the setback split: one patch per round and the triangle in three quadrilaterals, 15 faces, G1. Outside the box the sections span the body is the three strips', so its volume is theirs within that box's. A later r3 round at the mitred corner makes the body all three at once make (7928.142563938, 15 faces), as the engine and the model-cache tests have it. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DtL5M41G8Nua7HvuFPZkmJ * Kernel tests: SMLib's own corner between curvature rounds is curvature continuous, as the G2 patch is Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DtL5M41G8Nua7HvuFPZkmJ * Kernel rig: the boss root's and the hole rim's curvature rounds take the default timeout again (37 s and 34 s on the box under the rig's parallel load, tangency-labs/smlib#96) Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DtL5M41G8Nua7HvuFPZkmJ * Agents: model decisions use exact geometry; a mesh is for display, export, previews and mesh bodies Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DtL5M41G8Nua7HvuFPZkmJ * xtask: mesh-decisions, model decisions use exact geometry; today's 176 mesh decision sites are listed and the list only shrinks Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DtL5M41G8Nua7HvuFPZkmJ * Sheet metal: cuts and holes pass over sheets and bends by their exact boxes, never a mesh's A primitive cut skips the sheets kernel::apart (exact bounds grown by the record tolerance) finds clear of its tool; the bend check leaves the clear case to kernel::boolean, which answers it from the same exact boxes with no intersection work. The mesh-box helpers are gone, and their four lines leave xtask/mesh-decisions.txt (172 sites left). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DtL5M41G8Nua7HvuFPZkmJ * Agents: AGENTS.md loses a stray merge-conflict marker line at its end Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DtL5M41G8Nua7HvuFPZkmJ * Locales: Vietnamese for the setback-too-short refusal, now that vi is a complete catalog Main made vi a complete catalog; develop's new message (ui.fillet_error_setback_short) had no vi entry, so every_complete_catalog_carries_every_english_message failed on the merged tree. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DtL5M41G8Nua7HvuFPZkmJ * Kernel rig: exact volumes for 1213's bent-tube round and 4782's bar round, rel 1e-6 1213: the loft is a cubic skin through the five sections (ellipses between them), not a torus; its volume 131601.597487935 by quadrature less the exact rolling-ball removal 233.662461919 gives 131367.935026 (was a Pappus estimate on a torus, 131360.148, at rel 5e-4). 4782: the section's area in closed form, 25 pi/3 - 5 sqrt(75) + 25, so V = 630.2934873 (was a grid estimate, 630.293125). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01SdcgEu4Lr3moCCisdZShKz * Kernel rig: the boss root's and the hole rim's curvature rounds take 600 s again: under CI's parallel load they pass the 180 s default (develop 820b7b6) They take 37 s and 34 s alone on the box, but CI runs 8 cases at once on slower runners. Their G2 certificate cost is the open item (tangency-labs/smlib#106, moved to solidcore#2344). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DtL5M41G8Nua7HvuFPZkmJ * After the merge: clippy's auto-deref, and the mesh-decisions list for the merged tree Develop's list was taken on develop alone. Main's code (tap-marking reach, cut and hole box checks, join pieces, print faces, placed measuring, selection items, imported mesh payloads) and the branch's own exact_edges and named_vertex use meshes too; three listed functions were renamed by main (face_outline and plate_recesses into FaceSlice, paste into build). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01SdcgEu4Lr3moCCisdZShKz * After the merge: main's new tests on the SMLib kernel - Cut To the far side of a curved wall (#8634): the tool stops past the first crossing of the face ahead of the profile; SMLib's whole bore is one face that a line crosses twice, so the single-crossing rule found none and the cut took nothing. - Clearing view analyses goes through refresh_display, as main's #10687 made the others, so an open feature editor keeps OK and Cancel after Zebra. - vi, a complete catalog on main, gets the setback-too-short message. - fillets/KNOWN_FAILING: 4782's cause is now its continuity check (SMLib f916a8d builds the expected volume). - Known failing, as main's tests assume truck: the spline wall's spans as one mesh patch, a hole touching an edge at a point leaving one body, and a copy of a copy's triangles matching a fresh mesh. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01SdcgEu4Lr3moCCisdZShKz * Twisted sweep: circles about a straight path are exact cylinders (solidcore#2184) A twist about a straight path maps a profile circle centred on the path's line onto itself, so its swept wall is exactly the cylinder. The skin through the stations stayed within 3.9e-9 of it (6.6e-9 on the outer wall), and a boolean with another body on that cylinder failed with status 1001 (solidcore#2184; the kernel's handling of a B-spline face lying on a cylinder stays open there). sweep_controlled now builds those walls exactly when the path is lines along the profile's normal and there is no end scale or rails: a profile whose every loop is such a circle is swept untwisted, and such holes in another outer loop are cut as exact cylinders from the skinned sweep of the rest. Other loops, and an axis-centred arc inside a loop of other curves, are skinned as before; a failed cut falls back to skinning all. Regression test in smlib_sweeps_tests.rs: #2184's tubes joined at 10, 16, 18, 20 and 30 degrees give one closed body of 11.5625 pi with cylinder walls; a twisted hexagon with the bore keeps a cylinder bore. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01SdcgEtwSrdwZxqTQp5MfnU * After the merge: a hole that misses is found by exact boxes; a face is a one-face patch; main's mesh-box helpers gone - `hole_misses` (main's #10701, through brett's branch) decided from the targets' mesh boxes. It now uses their exact boxes (`Body::exact_bounds`). An unknown box still leaves the hole not known to miss. - With #10303's two shortcuts and `hole_misses` off the mesh, `body_box`, `mesh_box` and `padded_box` have no caller left, and are deleted. - `project`'s intersection link passes its one face to `meeting_edges` as a one-element patch. This branch picks one face, not #9009's mesh patch. - xtask/mesh-decisions.txt drops the six sites that no longer use a mesh here: `apply_traced_with`, `cut_end_past_face`, `beyond_cylinder_reach`, `hole_misses`, `body_box`/`mesh_box`/`padded_box`. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DtL5M41G8Nua7HvuFPZkmJ * After the merge: split_move's Result reaches its callers; to_local's duplicated move check goes `frames::split_move` returns a Result on this branch: an unplaceable model is an error, not a silent no-split. - Move/Copy of a component (main's #9914) propagates it, as its other calls do. - `to_local` had the solid.move check twice after the merge (brett's Option one and ours). Ours stays, after the no-picks/not-placed return. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DtL5M41G8Nua7HvuFPZkmJ * After the merge: main's two new tests take world_state's Result, as the rest of their files do Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DtL5M41G8Nua7HvuFPZkmJ * Native B-rep: a ball patch is its own surface kind, read from and written to SMLib's flat kind 6 SMLib's flat arrays now carry the corner of three equal rounds as `SURFACE_BALL_PATCH` (kind 6): its net as a NURBS face's block, with its sphere's centre and radius as its definition (ids 36 and 166). The record reads it as `ball_patch {center, radius}`, a label like the analytic kinds, with the net as its `nurbs`. A plain sphere with a form won't do: the net is not a piece of SMLib's sphere NURBS, so SMLib's `IsNurbSurfaceSphere` would refuse it. Written back, a ball patch is kind 6 with the same definition, which SMLib takes once its net is certified on that sphere. Elsewhere: - Offsets classify it as its sphere, so its offsets stay exact and collapse at the centre. - Face kinds count it as a sphere: fillet_three_edges_at_a_corner's corner is now `sphere`, no longer `other`. - STEP, which has no ball-patch entity, gets the net as the face's B-spline surface, pcurves included. - Iso curves and SSI of the label are refused; the face's form is what evaluates. Test: a_rounded_cubes_ball_patches_go_round_with_their_spheres. The cube's eight corners are ball patches about the corners pulled in by r. Points of each patch lie on its sphere to 1e-12. The patches are kind 6 again after import, with the same definitions bit for bit, and the closed-form volume holds. Format: pending/ball-patch-faces.rs. Docs: docs/native-brep.md and the rig README's `surface_types` (`ball_patch`). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DtL5M41G8Nua7HvuFPZkmJ * SMLib: pin v1.1.0-alpha (a18bbe5): the generic blend's step-4 corners, the Ball's sphere patch through the flat arrays, all-target CI Since f916a8d: - #120: every target again, plus the warnings fix; - #121: the Ball's patch as flat kind 6 with its sphere, read by the previous commit; - #122: tests gated on counts; - #123: the Mixed corner; - #124: the End at a smooth vertex; - #125: four or more rounds, and open setbacks; - #126: the equal-area thumbweight guard; - #127: the trunk merge. The SMLIB_PREBUILT checksums are from the release prebuilt-a18bbe5…, written by `scripts/fetch-smlib.sh --pin`. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DtL5M41G8Nua7HvuFPZkmJ * smlib export tests: rustfmt's line for the rounded cube's edge midpoints Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DtL5M41G8Nua7HvuFPZkmJ * Kernel rig: the fillet and ladder results on SMLib v1.1.0-alpha, the new failures recorded with their reasons Fixed (off the known-failing list): the Mixed corner's peg cases and the concave arc with the front top edge (smlib #123), and the 40° boss junction (smlib #124). Eight cases in all. New failures, recorded as they are, each with its reason. They passed on f916a8d. - **Six cases grade a blend seam G0 where G1 (or G2) is wanted,** at the end of the round's contact seam, after smlib #124's End at a smooth vertex. Two of them also shift in volume. - **Four cases come back unsupported** after smlib #125, which leaves setbacks to the Setback's corners only. - **Ladder 07/012** makes 9 faces, 20 edges and 13 vertices, where its golden had 8, 18 and 12. Its golden entry is the new result, with the reason added. Whether each change is by design or a defect is being established. A defect is fixed in solidcore, where the End and the Setback are being brought over (#2364, #2365), not in the frozen SMLib. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DtL5M41G8Nua7HvuFPZkmJ * Kernel ladder: 07/021 and 06/018 recorded as they are on SMLib v1.1.0-alpha, each with its reason Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DtL5M41G8Nua7HvuFPZkmJ * Kernel ladder: a golden case marked unstable is gated on its status, and 06/018 is marked On SMLib v1.1.0-alpha, 06/018 makes 597 or 594 edges from the same input: the union's post-process keeps pointers to edges it has deleted. A golden entry's `unstable` reason makes the gate compare that case's status only and name it in its output; recording keeps the reason, and only an edit of the golden removes it. v1.1.0-alpha.1 fixes the cause and removes the mark. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DtL5M41G8Nua7HvuFPZkmJ * After the merge with main: its new code on develop's exact bounds, types and thread fields - The sheet cut's cull (#10301) and the tapped wall's (#10227) use each body's exact box (`exact_box`), not its display mesh. - model.threads replies with develop's thread fields: form, hand (right, left or both) and starts. - surface.boundary's schema checks a network curve's continuity as the handler does, and words a list entry's error as it does. - Main's new tests take develop's Hole fields and world_state's Result. - mesh-decisions: contact_sweep's triangle check is now `depth` (main split `hits`). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DtL5M41G8Nua7HvuFPZkmJ * Known failing: the 14 cargo tests SMLib v1.1.0-alpha fails, with what each sees; two cases that pass now Develop's CI after the a18bbe5 pin (run 41522001173) fails 14 tests that passed on f916a8d, and passes two listed ones. Each new line says what the test sees on v1.1.0-alpha; v1.1.0-alpha.1 fixes the setback hole's cause. shell_tangent_chain_that_opens_every_face_explains_how_to_keep_walls and oracle 37-pyramid-apex-blend pass and leave their lists. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DtL5M41G8Nua7HvuFPZkmJ * Cargo.lock: develop's profile, smlib and step crates at main's 0.30.1 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DtL5M41G8Nua7HvuFPZkmJ * Kernel rig: main's six new sketch-only commands are exempt from a kernel case sketch.construction_line (and its horizontal and vertical forms) and sketch.spline.insert_point, remove_point and reverse change only the 2D sketch. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DtL5M41G8Nua7HvuFPZkmJ * Cuts leave the bodies their tools can't reach, by exact boxes (#10225 on exact geometry) - The per-target cut loop skips a body whose exact box lies clear of every tool's, as main's version did with mesh boxes. The sheet culls (#10226, #10301) and this one now leave the far sheets and bodies alone: a_cut_leaves_bodies_it_cannot_reach_as_they_were passes and leaves the known-failing list. - a_cut_still_runs_where_its_tool_touches_grazes_or_meets_a_curved_face: a tool 0.5 µm clear of the block is now left out (exact boxes; 0.5 µm is far past the bodies' tolerances); touching and 0.1 mm in still cut. - Known failing, with reasons: main's edge lookup by a stored point (#11286, on the display mesh) is not taken; SMLib refuses the wrong-way chamfer for its tangent chain first. - EXEMPT: main's eight new sketch-only commands. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DtL5M41G8Nua7HvuFPZkmJ * Kernel rig: main's new view, rendering, appearance and settings commands are exempt from a case 62 of the commands main added change no geometry: the view and render panes, rendering lights and results, appearance tools, settings profiles, point clouds (drawn as points, never a body), the selection, two sketch edits, component links and History bar visibility, edit.repeat, timeline.play, inspect.compare_picture (a picture against the outline), and component.paste_from_design, which pastes the app's cross-window clipboard that no command fills. Each joins EXEMPT's first section under its family's reason. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DtL5M41G8Nua7HvuFPZkmJ * Kernel rig: construct.plane.axis_point gets construction cases The plane through a box edge and its far corner, graded against its closed-form normal (0,-2,3)/sqrt(13) through the origin, and the refusal of a point on the axis. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DtL5M41G8Nua7HvuFPZkmJ * Kernel rig: assembly cases for mass properties, align, find limits and moving items between parts - assembly.mass_properties: two boxes (2 g/cm3) in a rigid group: mass 0.006 kg, centre (18.333,5,5), inertia diag(0.1, 1.0333, 1.0333) kg mm2 by the parallel-axis theorem. - occurrence.align: a block's end face onto a base's top face: a quarter turn about y, centre (70,20,20), box (65,15,10)-(75,25,30). - joint.find_limits: a slider between two stops: min -20, max 10 mm. - component.move_features, browser.reparent and component.move_sketches.to_parts: items moved into a turned and moved part keep their world place (volumes, centres and boxes by hand). The mass case assigns a material it creates, so material.create and material.assign leave EXEMPT. PATHS names the new command modules. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DtL5M41G8Nua7HvuFPZkmJ * Kernel rig: export and print face cases in the import area - file.export_step, export_stl, export_3mf, export_obj: a 30x20x10 box written and read back (the meshes converted to a solid): V 6000, A 2200, 6 faces, box (5,-10,0)-(35,10,10). - file.export_urdf: a hinged arm on a grounded base: 3 links, 2 joints, and the base's mesh, written in metres, reads back as the 1 x 0.5 x 0.2 box (V 0.1, A 1.6). - body.print_face: a cylinder's flat end is accepted, its side refused. PATHS adds the URDF writer and the print face modules. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DtL5M41G8Nua7HvuFPZkmJ --------- Co-authored-by: jyviko <2501648+jyviko@users.noreply.github.com> Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com> Co-authored-by: brett19 <brett19@gmail.com>
42 KiB
Components and joints
A design is a tree of components. New Component (component.create) adds one, and
Create Components from Bodies (component.from_bodies) turns bodies into components. Each
component has its own origin, bodies, sketches and timeline entries. The active component
(the radio button in the browser) receives new sketches and features; the others are drawn
faded.
Sketches drawn on a part's face while the design was active belong to the design, so they
collect in its Sketches folder. Move Sketches to Their Parts
(component.move_sketches.to_parts), on a Sketches folder's menu and on a sketch's menu, moves
the folder's sketches (or the selected ones) to the part whose face each is drawn on, as dragging
it onto the part would. Each stays where it is on its face, and the whole move is one undo step.
A sketch with no single part to go to stays where it is: one on an origin, construction or fixed
plane, on a body of the design itself, on a face without an exact attachment, or already in its
part. The status bar says how many moved and why the others stayed; the command's reply lists
each sketch. With no sketches it looks at every sketch in the design.
A component is placed by its occurrences. Paste creates another instance of the same component, and Paste New creates an independent copy. Move an occurrence with the move triad, then Capture Position to keep it or Revert to put it back. SolidCraft asks before the next command if a move wasn't captured. Ground fixes an occurrence in place, and Unground (the same row of the browser's context menu) frees it again.
The design's first part is grounded when it is made: the first occurrence placed directly in the
design by New Component, Create Components from Bodies or an import. Parts made after it,
standard parts and copies made with Paste or Paste New start free, so do parts made inside other
components. Any number of parts may be grounded, or none; opening a design never grounds
anything. A grounded part refuses Move until it is ungrounded, and component.create takes
grounded: true or false to choose for itself.
Drag a part to put it somewhere else. With the design active, press the left button on a part
and drag: the part follows the pointer, the point you grabbed moving in the plane through it that
faces the view, and stays where you let go, with its position captured. The whole drag is one
undo step, and Escape during the drag puts the part back. The drag moves the placement of the
active component that holds the part, so with the design active a part inside a subassembly
moves the whole subassembly; activate the subassembly to move the part inside it. Moving a
definition shared by several placements moves it in all of them, as Move does. A grounded part
does not move, and a part that joints hold to something grounded moves only as far as its joints
allow (below). Dragging any member of a chain joined to nothing grounded moves the whole chain,
preserving its joint values. Shared nested definitions move in every instance; the selected
instance follows the pointer even when its parent is rotated differently from the first one. A drag that starts on empty space, on a part that can't move, or
with Shift, Ctrl (Cmd) or Alt held draws a selection box instead. Other uncaptured moves stay
pending. Scripts and agents do the same with occurrence.drag {occurrence or path, at, point},
which moves the placement by point - at in world coordinates and answers the placements it
moved.
Move along the joint's free axes. Select a face or a single assembly part, then choose Assemble → Move, or right-click the selected face and choose Move. Thick straight arrows move along the allowed axes; circular arrows turn about them. Grounded parts, rigid joints, fixed coordinates and coordinates controlled by parameter expressions have no handle. The handles appear only after Move is started and disappear when Measure or another command starts. A face selected for measurement does not open Move. If the selected part has no free joint value, Move shows a warning instead of handles. Check rigid joints, grounding, joint limits and parameter-driven values; OK or Escape dismisses the warning without changing those constraints.
While dragging, a readout shows the actual distance or angle from the drag's starting pose, including when a joint limit or contact stops the part. Distances use the design's display units. Rotation uses 10° steps near the ring; pull the pointer outside the dashed guide to use 0.1° steps. Crossing the guide changes precision without jumping to another angle. Change both step sizes under Preferences → Design → Assembly Move. Each drag is one undo step; Escape while dragging restores its starting pose. Done (or Escape when idle) closes the handles.
To use the previous Move panel, turn off Use joint motion handles for assembly Move in the same settings section.
Paste New copies nested component definitions, sketches, feature histories and generated dimension parameters. Repeated child instances remain shared within the new copy. Materials, appearances and wholly internal joints/motion records receive copied references. Design-wide user parameters remain shared; retained external links and omitted cross-boundary motion records are reported. Unsupported destructive links refuse the entire copy. See individual-instance and copy details.
Extract to File (component.extract, in a component's right-click menu) moves a component
into a design of its own: its sketches, features, bodies, subcomponents and the joints among them
go to the new .sc file at its origin, with the parameters they use, and the component
becomes linked to that file, as Insert Design makes it. Its placements and the joints to the
rest of the assembly stay. Components whose own history builds the same bodies are offered to
become placements of the new link too (component.copies, component.replace_with_link).
The menu offers Extract only for a component that can leave: nothing outside uses its sketches
or changes its bodies, no bodies were moved into or out of it, and none of its subcomponents is
joined to the rest of the design.
Joints (joint.create, J) connect two components by joint origins that snap to faces, edges,
circles and vertices: rigid, revolute, slider, cylindrical, pin-slot, planar and ball, with
offsets, flip and limits. As-built Joint keeps the current position, Rigid Group locks
components together, Drive Joints moves a joint through its values, and Motion Link
couples two joints. A rigid joint holds its parts still, so Drive Joints has nothing to drive on
it: it says so and offers Edit Joint, where the joint's type changes to Revolute (rotate),
Slider (slide) or Cylindrical (both). Links can be chained (one joint drives a second, which drives a
third), and a value is carried through a chain of up to 64 links in whatever order they were
made. Contact sets stop motion where bodies would pass through each other,
Motion Study keys joint values along a timeline, and Interference shows overlapping
volumes in red, lists the pairs closer than its Clearance and each body's nearest neighbour.
In the Joint and Joint Origin dialogs, picking a straight edge puts the origin at its midpoint with the motion axis along that edge. A revolute joint turns about the picked edge; a slider moves along it. Round edges use their circle's centre and normal. Existing saved joint origins keep their axes.
A joint origin on a face or a hole keeps the turn it had when it was picked: when the face tilts (a bend angle or a rotation changing with a parameter) the part on it tilts with the face but doesn't spin about it.
A joint origin can also sit on an edge of a flat face ("edge": [x, y, z]): at the edge's middle,
pointing out of the face with its y into it, or with "corner": [x, y, z] at the corner near that
point, its x and y running along the two edges into the face. The edge, the face and the corner
are found again by name, so a bracket set 40 mm in from a panel's corner (a planar joint with
values [40, 40, 0]) stays 40 mm in from that corner when the panel changes size.
A joint's offset, angle and values can be typed as expressions over the design's parameters
("offset": "gap + 2", "values": ["travel"]). The joint keeps them and works them out again
whenever the design changes, so a part seated gap above a panel moves with gap. Renaming a
parameter carries into the joints that use it, and deleting one they use is refused. If an
expression stops working out (say a parameter becomes an angle), the joint is left out of the
solve and joint.solve gives the reason, instead of placing the part from old numbers. Typing a
plain number, or driving the value, drops that expression.
Relations are joints that tie only part of a placement, so a part is placed the way a
designer describes it, one relation at a time: parallel (z along z, free to move and turn
about it), perpendicular and angle (z square to z, or at the joint's angle from mated),
point_on_plane (a point on a face's plane, offset off it), point_on_line (a point on an
axis) and line_on_plane (an axis on a face's plane: a cylinder's radius as offset lays it
tangent). A relation is made where the parts are: B moves no further than the relation needs.
Several relations between the same two parts add up; the solver meets them together, each one's
degrees of freedom come off what is left, and one that can't be met is reported, not forced:
{"command": "joint.create", "params": {"type": "parallel", "a": "Panel top", "b": "Bracket bottom"}}
{"command": "joint.create", "params": {"type": "point_on_plane", "a": "Panel top", "b": "Bracket corner"}}
{"command": "joint.create", "params": {"type": "parallel", "a": "Panel front", "b": "Bracket face", "flip": true}}
{"command": "joint.create", "params": {"type": "point_on_plane", "a": "Panel front", "b": "Bracket corner", "offset": -40}}
{"command": "joint.create", "params": {"type": "point_on_plane", "a": "Panel end", "b": "Bracket corner", "offset": -40}}
leaves the bracket flat on the panel, square to its front, its corner 40 mm in from the front and
the end, wherever the panel's size takes them. Coincident faces are a planar joint, a distance
between faces is planar with an offset, concentric is cylindrical and two points that meet
are ball.
The check behind it, inspect.clearance, does all of that in one call for any number of bodies,
which suits scripts and agents checking a whole assembly:
{"command": "inspect.clearance", "params": {"clearance": 1, "nearest": 2, "skip_within": "component"}}
It returns overlaps (pairs sharing at least min_volume, 0.01 mm³ by default, with the shared
volume, area, box and centre), near (pairs closer than clearance, with the distance and the
two nearest points; a contact sharing less than min_volume is listed here at 0 with its
overlap_mm3), nearest (each body's nearest closest bodies) and unchecked (pairs whose
overlap could not be worked out, with the reason). against limits the check to pairs with one
body in bodies and the other in against, and skip_within leaves out pairs inside one
occurrence ("occurrence") or one placed component, its subcomponents included
("component"): the parts of a bought component that touch by design. Distances are measured on
the exact faces and edges; the meshes only rule out pairs that are too far apart, and the pairs
left are checked in parallel. inspect.interference remains for the overlaps alone: it clears
pairs whose meshes stay apart without intersecting them, intersects the rest in parallel, and
returns after budget_s seconds (default 240) at most, listing the pairs it had no time for as
not checked.
Mesh bodies (STL, 3MF and OBJ imports) are not checked by either command: each is listed in
unchecked as {a: name, b: null, reason: "mesh body: not checked"}, so count: 0 or an empty
overlaps is not mistaken for "no overlap" when a mesh body was in the design.
Gear, Rack and Pinion and Screw (on the ASSEMBLE panel) are motion links whose ratio comes from the parts rather than a typed number:
- Gear (
joint.gear {a, b, ra, rb}) couples two joints that turn. Joint 2 turns ra/rb as far as joint 1, the other way round; Internal gear (one of them is a ring gear) turns both the same way. Pick the round face of each gear, such as its pitch cylinder, or type the radii. Tooth counts work as well as radii, since only their proportion counts. Picking a gear's face also chooses the joint that gear turns on. - Rack and Pinion (
joint.rack_pinion {a, b, radius}) couples a joint that turns with one that slides: the rack travels the pinion's pitch radius times its turn in radians (r·θ). Either joint may drive the other. Injoint.listthe ratio is given per degree, as for any link between an angle and a distance. - Screw (
joint.screw {joint, pitch}, or{a, b, pitch}for a revolute joint and a slider) advancespitchper turn. A cylindrical joint is a screw on its own: its turn drives its travel. The thread is right-handed; Reverse makes it left-handed.
A radius or pitch may be an expression of the design's parameters, and a picked face is found
again whenever the design changes. Change the parameter or the gear's diameter, and the ratio
follows. The new link leaves the driven joint where it is, so teeth modelled in mesh stay in mesh.
Reverse turns the driven joint the other way, for joints whose axes point opposite ways.
Redefining a link (link: i, such as turning it the other way with Reverse) also leaves the
driven joint where it is, so the gears stay in mesh at the pose they are in. These
couplings are motion links, so they work in closed loops, with contact sets and in motion studies:
a rack can push the piston of a slider-crank, or a pinion can steer through a rack and its tie
rods. Drive the joint that drives the coupling (joint 1, the pinion, or the screw's turn), not the
driven one. A joint follows one link at most, and a coupling that would drive its own driver is
refused. joint.list lists each coupling's definition under links with an error when it can't
be worked out (the picked face is gone); the link then keeps its last ratio.
Cam (joint.cam {a, b, profile}, on the ASSEMBLE panel) makes a follower ride a cam. The
cam turns on a revolute joint (a); the follower is a slider (b, a translating follower such as a
valve tappet) or a revolute joint (b, an oscillating follower such as a rocker arm). The profile
is the cam's outline in a plane square to its axis: a closed profile of a sketch in the cam's
component, or the cam's edges picked on its body (one click on an edge takes the closed loop it is
on in that plane). The follower is:
- a Knife edge: a point on the cam;
- a Roller of a radius, typed or taken from the roller's round face (picking that face also says where the roller is);
- a Flat face square to a slider's line, such as a bucket tappet.
A translating follower's line runs along its slider's axis, through its Tip when one is picked
(its knife's point or its roller's centre), so a follower offset from the cam's axis rides the
right flank. An oscillating follower needs its tip, or its roller's face, to know its arm. The
follower rides the cam from the side it is on (Other side takes the other one). The follower's
travel over a turn of the cam is worked out from the profile and kept with the link, one value a
degree with a smooth curve between them that never overshoots its samples. It is worked out again
whenever the design changes: change the cam's sketch, a parameter or the roller, and the follower
follows. Like the gears, the new link leaves the follower where it is (model it touching the cam),
and the cam is a motion link: it drives in Drive Joints, plays in motion studies, works in
closed loops (a tappet can be the piston of a slider-crank) and stops at contact sets. The profile
may also be on the grounded part, with the follower's guide on a turret that the cam joint turns.
joint.list gives a cam's link lift (the follower's lowest and highest values and its rise)
instead of a ratio. A profile that is not closed, a line or an arm that misses the cam somewhere,
a follower that would jump, and axes that are not square or parallel are refused.
A joint moves one component against another, so its two picks must be on different components.
A STEP file with several parts often comes in as bodies of one component, and picks on two of
those bodies make no joint. The Joint and As-built Joint dialogs say so under the picks and offer
Create Components from Bodies: each picked body gets a component of its own and stays where it
is, the picks are kept, and the joint previews. joint.create refuses such origins with the same
advice.
Joints may close a loop, as in a four-bar linkage or a slider-crank. When one joint of the loop
is driven, the other joints in the loop follow so that every joint still meets, and the
mechanism stays in the assembly mode it started in (an open four-bar does not flip to the
crossed one). If the motion would take a loop past the point where it can still close, for
example driving a rocker beyond its swing, the motion stops at the last position where the loop
closes, and the drive reports stopped_by_loop. A loop that cannot close at all is listed
under conflicts and nothing in it moves. joint.list reports how many degrees of freedom each
part still has with its loops closed: the moving parts of a four-bar have one between them, and a
loop locked by a rigid joint has none. A joint a motion link drives adds no freedom of its own:
two meshed gears on a fixed housing have one between them, each turning with the driving gear. The Drive Joints dialog says when a drive stops short and
why. While it previews, a row under the values gives the value the joint reached and the reason
(the loop that can't close further, or the two parts a contact set keeps apart), and after OK the
status line repeats it. The value box keeps what you typed. The dialog opens on the joint
picked in the browser, or on the first joint that moves when none is picked.
Drag a part that joints place and it moves as far as its joints allow: the point you
grabbed follows the pointer in the plane through it that faces the view, the joints on the
part's chain take the values that bring it nearest, within their limits, through motion links,
and with closed loops kept closed, and a four-bar's rocker stops at the end of its swing. The
whole drag is one undo step. A grounded part, or one its joints hold fixed, is not moved; a drag
on it draws a selection box. Each frame runs joint.reach, which scripts and agents use
directly to put a part's point somewhere: joint.reach {occurrence, point} moves the joints on
its chain from where they are to the nearest pose (the arm keeps its elbow up or down, and a
linkage stays on its branch). at picks the part's point (the centre of its bodies by
default), z with axis also turns one of its axes, and joints names the only joints to
move (the other joints of a closed loop they are in follow). The answer says whether it
reached the point and how close it got (error_mm, error_deg), and when it falls short,
the limits it rests on (stopped_by_limit) or the loop that stopped it (stopped_by_loop).
Contact sets are not checked by a reach; drive the joints for that.
The solver places what it reaches from the root and from grounded components. A chain of joints
that is joined to nothing grounded is never placed, so driving one of its joints moves nothing.
The drive says so: joint.drive answers moved: false with a reason and the unconnected
part ("Pedestal:1 is not connected to anything grounded"), the Drive Joints dialog shows the same
row, motion.play lists such joints under unmoved, and joint.list names every such chain under
floating. Ground a part of the chain, or join it to a grounded part (a rigid as-built joint keeps
it where it is), and it moves.
joint.drive answers the joint's values as joint.list gives them, in degrees and millimetres
with their units and limits, and moved says whether any part moved. A joint's origins are mated
by default: B's z axis is turned against A's, as two faces meet. flip: true lines them up
instead, so two origins given at one point with the same z and x stay as they are. A point origin
without x takes its x from z alone, so a part turned about z turns back when it is joined: give
x on both origins, or use joint.as_built, to keep it where it is. Without an
angle, a new joint (other than a relation, which starts where its parts are) takes no turn or a half turn about its axis, whichever turns B less: two
faces that already meet, a plate under a panel, stay as they are instead of B spinning about
their shared normal. For scripts that drive many steps, quiet: true leaves the per-part
degrees of freedom out of joint answers, and
motion.play with quiet: true gives the poses of only the parts that moved.
Motion Trace (motion.trace, on the ASSEMBLE panel) draws the path a point of a part
takes while a joint is driven or a motion study plays, such as the coupler curve of a four-bar.
Pick the point on the part (a face centre, a circle centre, an edge midpoint or a vertex), then
either a joint with the values to drive it from and to (a turn of the joint from where it is, at
first) or a motion study. The path previews in the viewport as the mechanism would move: closed
loops follow, and the path ends where a loop can no longer close or a contact set stops the
motion, which the dialog says under the values. OK keeps the path as a 3D sketch spline in a new
sketch of the root component (Motion Trace1, ...), where no joint moves it, and it can serve
as a sweep or pipe path. New traces retain their source and update when the mechanism's
joint origins, limits, motion links or driving conditions change. Playing or dragging the
mechanism does not redefine the trace: it keeps the assembly branch from when it was made.
Unrelated parameter and display changes do not resample it. A path that comes back to where
it started is kept as a closed, smooth spline.
motion.trace {occurrence, point, joint, from, to, index?, samples?} (or {occurrence, point, study, samples?}) answers the world points without changing the design, and
motion.trace.keep with the same parameters (and name?) keeps them. point_ref can retain a
joint-origin snap (such as {occurrence, face: [x,y,z]}), so the point follows its resized
face; without it, the point is fixed in the part's coordinates. The dialog retains its face
or circle snap. motion.trace.edit {sketch, from?, to?, samples?} changes a joint trace's
driving conditions; joint with from and to, or study, replaces its motion source.
Expressions in from and to follow parameter edits. Study traces follow edits to the
referenced study, including its step count when Samples was left at the default.
auto_update: false in motion.trace.keep makes a fixed curve; in motion.trace.edit it
detaches an existing association, preserving the curve. Curves saved by earlier versions
remain fixed. motion.list includes the associations and their errors. If a source is lost,
the sketch warns and keeps its last successful curve until the source is restored or the
association is detached. Changes and their generated curves undo and redo together.
A trace takes 2 to 500
samples: 100 by default for a joint, one per step for a study.
The Chebyshev linkage demo builds a complete four-joint mechanism, plays a saved study and demonstrates the same retained trajectory updating after a link-length or driving-range edit.
Export Animation… in the Motion Study dialog saves the study as an animated GIF, drawn
from the viewport's camera as the study plays (the keys in the dialog count, even before OK).
motion.export_animation does the same for scripts, the CLI and agents, without a window: give a
study, or a joint with from and to (and index?) to animate a drive, and a path. A path
ending in .gif gets an animated GIF that loops; any other path is a folder that gets the frames
as frame-0001.png, frame-0002.png, and so on (made if missing; frames of a longer earlier
export there are removed), for a video tool. The web app writes GIFs only. samples is
the number of frames (one per step for a study by default, 100 for a joint), width and height
their size in pixels (800 × 500 by default, at most 4096 a side), and fps the GIF's speed (20
by default); grid: false and axes: false leave out the ground grid and the origin's axes.
camera takes the reply of the control channel's ui.camera (or any of its fields;
the rest come from the view view.apply chose, or the home view framing the model). The frames
are drawn by the same renderer as solidcraft-cli snapshot, on a copy of the design, which is not
changed. A GIF keeps one palette for all its frames, so colours don't flicker, and stores only
what changed from one frame to the next. Frames are capped: at most 1000, and a GIF holds at most
2^26 pixels of frames (about 160 frames of 800 × 500).
An exploded view animates the same way: give its name or id as view (instead of a study or a
joint) and the parts come apart at a steady pace, from the assembled placement to where the view
shows them; back: true brings them back together, exploded at the middle frame. That takes 41
frames by default, or 81 with back, and the home view frames the parts both assembled and
exploded. As with explode.show, the design keeps its placements.
Motion analysis. The Motion Study dialog's Study box opens a saved study to edit, and by its timeline the dialog charts what the study does. Plot picks a moving joint value (a joint picked in the Browser is picked here too), or Picked point once a point is picked in the dialog's Point box, and Quantity whether to show its value, velocity or acceleration; the chart runs over the study's steps with a cursor at the step shown, and a click or a drag on it moves to that step. Values are in degrees and millimetres; rates are per step, or per second once Duration says how many seconds the whole study takes. A picked point charts its distance from where it starts, its speed and the size of its acceleration. Check collisions plays the study and lists the pairs of parts that pass through each other, with the steps where they do (a click on one shows the first of them); those steps are shaded on the chart. It checks the parts picked in Components (against the ones picked in Against, when there are any), else every component, or the pairs of the design's contact sets (a choice beside the button once it has any).
motion.plot {study, joints?, occurrence?, point?, samples?, duration?} answers the same
numbers: for each joint value its value, velocity and acceleration per sample (with their
units), and for a point its position, velocity and acceleration vectors, speed and
acceleration_norm. The study plays as motion.play places it (closed loops follow, contact sets
stop it), each sample from the one before, on a copy: the design is not changed. Velocities and
accelerations are finite differences between samples, central inside and one-sided at the ends,
so they are as smooth as the samples are dense (up to 1000, one per step by default). Angles are
unwrapped, so a joint that turns on past half a turn keeps counting.
motion.interference {study, occurrences?, against?, contact_sets?, samples?, budget_s?} answers each
colliding pair with its first_step, last_step, the steps ranges where they overlap, the
most volume they share at a sample (volume_mm3, worked out exactly from the bodies), the first
sample sharing that much (deepest_step) and how far into each other they reach (depth_mm, an
estimate from points of the bodies' contact meshes). When the volume could not be worked out at
every sample they overlap (more than 16 colliding pairs, or past the check's 256 body
intersections), volume_mm3 and deepest_step are null and not_measured says why. It plays the study as motion.play does, but
contact sets don't stop it, and parts are tested at the samples only: a part that passes right
through another between two samples is missed. Parts are told apart by occurrence, as contact
sets tell them apart: an occurrence inside a sub-assembly placed twice is one part, so its two
copies are not checked against each other. A check takes at most 256 bodies; on a large design,
list the occurrences to check (an arm, with against the parts it must miss). When the work
runs out it says truncated and the step it checked_to, and it is not clear, even when nothing
collided in the steps it checked. A mechanism with detailed parts, such as a gear train, can need
more than that fixed work budget: give it budget_s (seconds, at most 86400) and the check runs
until that time instead, looked at between samples.
joint.sweep {joint, from, to, index?, step?, refine?, occurrences?, against?, contact_sets?, report_gaps?, apply?} drives one joint value from from toward to and answers how far it gets
before parts touch: stopped_at (the last value clear of contact), stopped_by (the two parts
and the point at which they touch, or "loop" where a closed loop can no longer close, or
"limit"), and with report_gaps the nearest gap at every sample and the nearest each part came
to another (min_gap). The samples are fine enough that no part passes through another between
two (or step apart), and the first contact is bisected until no part moves more than refine
(0.01 mm by default) across it. Gaps are distances between the parts' tessellations
(gap_method: "mesh"): exact for flat faces, within gap_tolerance_mm for curved ones. Pairs
already touching at from, such as parts joined face to face or a door resting on its frame, are
listed in touching_at_start and stop the sweep only once they pass into each other, deeper than
they start. The sweep runs on a copy (closed loops follow, contact sets don't stop it) and
leaves the design as it was unless apply is true.
Find Limits. In Edit Joint, the Limits section's Find Limits button fills in each
value's Minimum and Maximum from where the parts the joint moves first touch another part,
turning or sliding each way from where the joint is now, and ticks its limits. It searches the
joint as the dialog has it (a type, flip or offset changed but not yet applied included), on a
copy: nothing changes until OK, so the values can still be rounded or edited. They are
rounded toward the joint's value (a tenth of a degree, a hundredth of the length unit) so they
stay clear, and a line under each value says what stopped each side. An angle is searched a turn
each way: a side that meets nothing is set a turn from the other side, or half a turn each way
when nothing is met at all. A distance is searched as far as the parts reach; a side that meets
nothing there keeps what it had, and the limits stay off until both sides are found. Parts
already in each other where the joint is now are named, and stop the search only once they go
deeper. The search runs while the window goes on (Cancel drops it). joint.find_limits {joint, index?, refine?, step?, occurrences?, against?, contact_sets?} answers the same: for each value
its min and max (null where a distance meets nothing), what stopped each side (min_by,
max_by: the two parts and where they touch, or "loop", "limit" (the limit of
another of its values, or of another joint through a motion link), "turn" or "range"), the range searched, and the parts touching_at_start
and overlapping_at_start (with depth_mm). The joint's own limits are left out of the search,
closed loops follow, and each side is bisected to refine as joint.sweep does.
Insert Design (component.insert_design {path, translate?}, on the ASSEMBLE panel and
in the File menu) adds a component linked to another saved design, so each part can live in
its own document. When other designs are open in tabs, the button first lists them under
Open designs. One click inserts that design; a design not saved yet is greyed out, as it has no
file to link; one with unsaved changes inserts its saved file, and the status line says so.
Browse… at the end opens the file picker, as the button does when no other design is open.
Preferences › Design › Insert Design lists the designs open in other tabs first turns the list
off. A STEP or mesh file picked there is inserted as Insert STEP or Insert
Mesh would. The part's solid bodies come
in as they sit in that design, and they are kept in the assembly, so it opens even without the
part file. The link is stored relative to the assembly's folder once the assembly is saved.
For scripts, translate: [x,y,z] places the design's origin in millimetres from the destination
parent's origin (the active component unless parent is supplied). It defaults to [0,0,0].
With reuse: true, insertion reuses the existing linked component but uses the same coordinates;
it does not inherit another occurrence's position or rotation. For example, inserts at
[20,0,0] and [40,0,0] place the two origins at 20 and 40 mm, even when the second reuses the link.
After the part file changes, Update Links (component.update_links) reads it again.
An assembly that opens, or whose tab comes back to the front, does that by itself for the parts whose files
changed since it last read them, whether the part was saved in another tab, another window or by
a checkout. The parts it reads come in as one step, so one Undo takes them all back. A part
that cannot be read keeps its bodies, is tried again the next time, and holds up no other.
Update changed linked designs when a tab comes back (Preferences, Design,
update_changed_links) turns this off.
To edit the source, right-click a linked component or occurrence in the Browser and choose
Open Linked Design. It opens the part in another tab and reports if its file is missing.
Break Link (component.break_link) keeps the bodies and forgets the file, and
component.links lists the links, whether their files are found, and whether they changed since
the assembly last read them (changed). A linked component holds
the part's bodies only: its timeline, parameters and sheet-metal data (flat pattern, bend
table) stay in the part's own design.
To edit a linked part where it sits, double-click it, in the Browser or on one of its faces in
the view, or choose Edit in Place from its menu. Its design opens in a tab of its own with the
rest of the assembly drawn faded around it, at the placement you picked, and the part's own
history, Browser and commands work as usual. Update Links there also reads the assembly's
links again and redraws it. Finish Edit (component.finish_edit), at the right end of the
MODEL tab, or the mouse's back button, saves the part and goes back to the assembly, which
takes up the change; the part's tab closes again when the edit opened it. Run as a command (by
an agent, for example), it does not save: the part must be saved first. Activate still makes
a linked component the active one without opening it, and a double-click on a component that
is not linked activates it. Double-click a component to activate it, or to edit a linked one in
place (Preferences, Design, double_click_components) turns this off: a double-click in the
Browser then activates every component, and one in the view does nothing.
If a source file moves or is renamed, right-click its linked component or occurrence in the
Browser and choose Relink Source (All Instances)…. Choose the saved .sc design
to use. Relinking updates that component's stored path and solid bodies for all its
instances, keeping their identities and placements. Cancelling or choosing a missing,
invalid, empty or self-referencing design leaves the assembly unchanged. The operation is
one undo step and the new path is saved relative to the assembly when possible.
Scripts use component.relink {component, path}. The reply includes previous_path, path,
warnings, joint_errors and joint_conflicts. Changed geometry can invalidate a joint's
face reference: relinking reports those joints in the reply and UI status/message history;
repair the joint or undo the relink. Relink does not repair or verify the intended meaning of
existing joints.
When linked geometry changes and the component has joints, a reminder to check those joints
is also shown even if the solver reports no error: a successful solve does not prove that a
joint still describes the intended connection.
STEP export writes the component tree as an assembly.
Right-click a component in the Browser and choose Properties, or use Inspect → Measure →
Properties for the selected placement or the active component, to inspect material-aware
mass, volume, surface area, centre of mass, first moments, moment of inertia and world bounds.
While the window is open, the view marks the centre of mass with the three principal axes
standing out of it. Descendants and
repeated instances contribute to assembly totals; pending moves are included. A component
uses its first placement; occurrence.properties selects a specific instance. Root Properties
measures the complete assembly. Volumes are summed, including overlapping bodies, rather than
measuring their union. The same workflow is available through component.properties and
occurrence.properties; see
placement and measurement details.
Part properties and the bill of materials
A component definition carries its own part properties: a part number, a description and a
revision, other tools' data under a reverse-DNS key (the same rules as the design's own
properties), and free text properties such as a material grade or a finish. Every occurrence of
the component shares them, Paste New copies them, and they are saved with the component.
component.metadata {component} reads them and
component.metadata.set {component, part_number?, description?, revision?, bom_type?, values?, properties?}
changes them in one undo step (an empty value removes a field). The root component is the
design itself: its properties are document.metadata's. Standard parts (parts.insert) get a
part number from their standard and size (ISO 4762 M6x20, or a bearing's designation) and a
description; Change Part Size renumbers them, keeping a field you changed yourself.
Bill of Materials (assembly.bom, on the INSPECT panel) counts the placed components:
levels: "flat"(the default) lists the parts at any depth, each counted through its subassemblies: a part placed once in a subassembly that is placed twice counts 2. A subassembly is listed through its parts, unless it has bodies of its own.levels: "top"lists the direct children, a subassembly as one row.group_by: ["part_number"](the default) puts definitions with the same part number in one row; a definition without a part number gets a row of its own.["definition"]gives every definition its own row.group_children: truekeeps what is placed inside a part with a part number in that part's row: a bolt with a washer and a nut placed inside it is one row, the washer and the nut listed under it aschildren(items 1.1, 1.2…, witheachper bolt andcountin all) instead of rows of their own. Bolts with different contents (one with a nut, one without) are different rows.total_occurrencescounts the children too, so it is the same either way. For an inseparable part, only its purchased descendants become children; a purchased part still has no children listed. Parts without a part number are not grouped this way.componentlists one subassembly's parts instead of the design's.
A component's bill of materials type (bom_type, a part property set with
component.metadata.set {component, bom_type}) decides how it counts in the assemblies it is
placed in. Without one it is normal.
| Type | For | In the assembly it is placed in |
|---|---|---|
normal |
Something you make | A row of its own; every occurrence adds to its quantity |
phantom |
Something just to group (a fastener set) | No row: what it holds counts as if it were placed there directly, in the same rows as the same parts placed there |
reference |
Something to use as a reference (a fixture shown for context) | Counted nowhere, and nothing inside it is counted either |
purchased |
Something you buy (a gearbox) | One row; nothing inside it is counted or listed |
inseparable |
Something made as one piece: welded, glued, riveted and so on (a welded frame) | One row; in parts only, the purchased parts inside it are listed too, and the rest of what it holds is listed in its own bill of materials |
Two components with the same part number share a row only when their types agree. A
component's own bill of materials (component) lists what it holds whatever its type.
Rows are sorted by part number (rows without one come last) and hold item, part_number,
description, revision, bom_type, count, definition (the component names), components (their ids)
and properties, with total_occurrences beside them. path writes them to a .csv file
(the columns item, part_number, description, revision, count and definition, every field
quoted; children follow their row) or a .json file. The window lists the same rows, switches
between the levels and groupings and shows children under their part, edits a picked row's part
number, description and revision, and exports them. Changing part properties changes no
geometry, so it doesn't evaluate the model or re-seat joints again.