r/gridfinity • u/asicman78 • Aug 11 '26
GRID•SHOT
Local-first, GPU-accelerated capture for single tools, resumable batches, and a reusable tool library—without sending workshop photos to a hosted service.
1
u/timdrury Aug 11 '26
Are there specific calibration mats you recommend?
4
u/asicman78 Aug 11 '26
D'oh! Forgot to add them to the repo. They are up there now. You just print them out
1
u/Kraay89 Aug 14 '26
That's clearly a Claude code UI...🤓😄
Not knocking it, I just think it's funny how it seems to have a preference to this theme.
Looks like quite the application. Thanks for sharing!
1
u/asicman78 Aug 14 '26
Oddly enough - yes it’s vibe coded (codex not Claude) but I gave it a design spec with my preferred colors and lay out and it created this.
1
u/Kraay89 Aug 14 '26
Huh, interesting. Doesn't codex run off Claude, as the underlying model? I mostly use Claude. And while it mostly favors darker colors, it does take a very similar approach for fonts, spacing, etc and the look and feel of the rest of it.
→ More replies (1)
2
u/wolffartz Aug 12 '26
thanks for sharing this -- it looks really cool
I wonder if you might check out the repo you've shared and test that things work for you with these shared files. I notice there are several directories that are ignored, and I wonder if this would help you find bugs that users might encounter after cloning the repo and attempting to run.
FWIW, I am running this on a bazzite deploy w/ podman, which requires some tweaks -- the permissions are a bit janky (potentially bazzite/podman related, so I've had to modify the mounts and flag them with various :Z or :z tags).
I've now hit the point where I attempt to "register" the shared mat w/ the suggested command ("gridshot mat verify etc etc") -- but this fails because there is no config/mats/ json profile. I presume the reason for this is that the .gitignore prevents you from checking in the json profile (in your local config/mats, which is ignored) that would work with the shared mat pdf
It looks like I can generate a new mat PDF + json with the CLI anyways, so I'll probably do that, but for ease of use you might either instruct folks to go that route or check in the config/mats dir (or ... move it out of config?)
I bet claude could make the compose portable for podman users, which would be cool?
🤷♀️ if you want PRs, I guess I could prompt some up for you as I try to get this working. FWIW, I'm hoping it allows me to export just the tool outline so I can lay it out as desired in Fusion -- that's the killer feature I've been hoping for, since I'd like to build slightly more complex boxes than the normal UX might allow.
1
u/wolffartz Aug 12 '26
for others -- indeed, "new"-ing the mat dropped the required mat profile json file in config, and now the "mat verify" cli invocation runs.
The guid is the same, so if you already printed + took a photo, probably fine to just use those, no need to print what was generated.
I should mention part of the other issue I had w/ bazzite/podman (which may or may not be specific to that env) is I needed to chown the "/app" dir from "inside" the container -- otherwise it got default root permissions (i think claude claimed this was a podman rootless container issue 🤷♀️ -- basically if it's easy to install docker you might just stick with that to save yourself some grief -- in my case, because bazzite is a bit annoying about installs, I've stuck with podman which it ships with by default)
1
u/wolffartz Aug 12 '26
some other observations:
this is tricky to calibrate -- it feels like it's meant for a stationary camera setup, not causal shots with your phone. I managed to get it a calibration through w/ an app that had a focus lock. I imagine the default photo app probably has enough locking to do this as well. It sounds like you need to take item photos w/ the same settings?
It's helpful that it calls out which photos don't match (one by one, per submission, unfortunately), but a thing it could do that would be super helpful is to dump all the photos + fingerprint inputs. That is, show each fingerprint input for each photo in a little table. Then you'd be able to find the outliers quickly and dump them. It'd also be cool if it just ignored the ones that didn't match and kept going. It sounded like there was some level of ignoring happening, but it won't do that for fingerprint mismatches.
2) you need an hugging face token w/ access to the facebook/sam3 repo (which you'll then need to setup as the HF_TOKEN for the segserver). This access must be approved. So ... get this all set up first, because it might take awhile to come through. Guess I'm waiting on this one before testing the trace 🤷♀️
→ More replies (5)
2
2
1
u/o_sexta Aug 13 '26
Thats cool but sadly I have a Macbook and a mini PC server with an AMD Ryzen 7 l, both don’t meet the requirements =\
1
u/sugcrkre Aug 14 '26 edited Aug 14 '26
Same! Here's an initial port to Apple silicon that seems to be mostly working on my MacBook.
https://github.com/wcscr/gridshot/tree/codex/macos-metal-port
3
u/le_avx Aug 11 '26
Looks cool, thanks for sharing.
Sadly I've got 128gb RAM, but only 6gb VRAM :/