feat(reconstruction): TRELLIS.2 pipeline, welded watertightness, absent-not-zero confidence - #32
Open
Mizunandayo wants to merge 1 commit into
Open
Mizunandayo wants to merge 1 commit into
Mizunandayo wants to merge 1 commit into
Conversation
… absent-not-zero confidence
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Two honesty fixes that improve the InstantMesh pipeline now, and a TRELLIS.2
pipeline that is complete but not deployed.
Both fixes are the same bug: "not measured" reported as "worst possible"
Watertightness was measured on split vertices. UV mapping duplicates a vertex at
every chart seam. The surface it describes is unchanged, but
is_watertightreturnsfalse — so a textured mesh lost 30% of the confidence weight to a rendering
artefact.
measure()now welds a copy before testing watertightness and volume.A test builds a geometrically identical seam-split sphere and asserts it still
reports closed.
An absent measurement scored zero.
field_decisivenessreads an empty deviationarray as 0.0, at weight 0.45 — most of a 39.6% score on a good mesh. A pipeline that
genuinely has no density field now has the component dropped and the weights
rescaled to 1.0, with a
field-decisiveness-unavailablenotice, exactly asforegroundQualityis already handled.TRELLIS.2 — complete, not deployed
MIT, 4B parameters, sparse-voxel, PBR materials and a real UV texture. Adapter,
Dockerfile.trellis2, contract enum, config and wiring are all in and gated.Not deployed. Three builds failed: a wrong extension path, then a worker OOM at
MAX_JOBS=8on an 8GB builder — Cloud Build reports that asINTERNAL_ERROR, whichreads as infrastructure rather than sizing. Fixed to
MAX_JOBS=2and never re-run.A separate Dockerfile on purpose: it needs CUDA 12.4, a compiler and five extensions
built from source, and folding that into the working image would put TripoSR and
InstantMesh — both serving — behind a build that has never succeeded.
Also built, default off
resolution). Works — 53× the colour detail — but UV unwrapping drops watertightness.
Wrong trade for a physics system: mass comes from volume, volume needs a closed
surface.
TEXTURE_RESOLUTION=0, and the default is what matters, becausedeploy-all.ps1uses--set-env-varsand replaces the whole environment.30/90/150/210/270/330 at alternating +20°/−10°. Observation beats invention, but the
capture UX asks for four, so it never fires.
but both models were fine-tuned on an empty prompt.
Gates
127 reconstruction tests ·
ruff·mypy25 files · no contract drift