#296 · Inspect a synthetic scan mesh before CAD cleanup
Last checked with GitLab: . Status comes from GitLab using a 2-minute cache. Merge events clear affected cached statuses. An already-open page does not update itself. Refresh page.
An MR completes this bounty when it is merged into main with Closes #296 and GitLab closes the issue. A mention or an updated timestamp is not completion. Awarded points appear in Activity.
cp .dev.vars.example .dev.vars && pnpm dev, after rebasing on main) and fully test your change before opening the MR.
Description
The 3D-scanning guide highlights excessive mesh size and post-processing work. Add a read-only local teaching inspector for one simple documented mesh format with synthetic geometry.
Who might enjoy this
- Community interests: Hardware / fabrication, sUAS / Drones, Research
- Skills: python, graphics, hardware
- Experience: intermediate; work style: analytical.
- Readiness: ready; bounty size: M (existing points tier; standard merge award stacks separately).
Current behavior and starting points
Source-reviewed against main cf05b29c6256dba70d0ebc09b22cc9867cdb786a on2026-10-18. Check current main and related issues/MRs before implementing so existing work is reused.
Relevant Files
- apps/wiki/src/content/docs/hardware/3d-scanning.md
- apps/wiki/src/content/docs/general/fabrication-getting-started-with-cad.md
Deliverables
- An offline Python inspector for ASCII STL with explicit unit selection, triangle count, file size and bounding dimensions.
- Original small synthetic triangle/cube fixtures and a guide relating these diagnostics to the existing scan-to-CAD workflow.
Dependencies and decisions
No prerequisite issue is required. Re-read current main and linked MRs before starting.
Acceptance criteria
- [ ] A known 10-unit synthetic cube reports expected bounds and triangle count; switching the declared display unit changes labels/conversion without guessing the source unit.
- [ ] Truncated, oversized and nonfinite-coordinate inputs fail with clear reasons before unbounded allocation.
- [ ] Files remain byte-identical; run with no camera, LiDAR, scanner, GPU or network and document the supported format limits.
- [ ] Record named baseline failures and the exact commands used. A behavior fix includes a real route/database/protocol check observed failing before the change. Knowledge work includes source traceability and reproducible reviewer evidence.
- [ ] Run the affected app's existing checks. Explain any baseline failures rather than reporting a matching failure count as proof.
Try it locally
Start from the existing source files above. The following is the target demo your contribution should enable; a newly proposed script or fixture is part of the deliverable:
Inspect the supplied synthetic cube and an intentionally truncated copy before opening either in CAD.
Use public or synthetic examples. Starter work should run without production access; explicitly name any software/device prerequisite before claiming it is ready.
Out of scope
- No real scans of sensitive objects/locations, mesh repair/decimation solver or manufacture-ready claim.
- Do not duplicate #254 MuJoCo builder collision/geometry regression fixtures.
- Unrelated refactors, new services/providers, bulk dependency changes, production access changes, unrequested notifications, and copying private member material. Keep credentials and unresolved security findings outside the issue and repository.
For a coding agent and reviewer
Read AGENTS.md, applicable .cursor/rules/, app instructions and docs/contributing/agentic-bounty-review.md. Reuse the existing shared helpers, identity/access paths and app styling. Implement one bounded story and provide evidence the accepting app maintainer can reproduce. State updated / pre-release verified / released / live verified accurately.
A parent index carries no duplicate award for these child deliverables. Open one scoped MR using this issue's actual number after the closing keyword. Link your GitLab identity on Scoreboard; the existing merge webhook handles eligible points.
Catalog index: #258.
<!-- community-interest-bounty:2026-10-18:mesh-size-inspector -->
Relevant files
-
[apps/wiki/src/content/docs/hardware/3d-scanning.md](https://git.juntogroups.org/irregulars/irregularchat-monorepo/-/blob/main/apps/wiki/src/content/docs/hardware/3d-scanning.md)from issue -
[apps/wiki/src/content/docs/general/fabrication-getting-started-with-cad.md](https://git.juntogroups.org/irregulars/irregularchat-monorepo/-/blob/main/apps/wiki/src/content/docs/general/fabrication-getting-started-with-cad.md)from issue
Hints
No hints yet.
Activity
No points have been awarded for this bounty yet.
Comments
Sign in to join the discussion.
No comments yet. Be the first to weigh in.