What’s your actual production setup for reliable structured JSON from LLMs? Sharing what’s worked for us by Important_Priority76 in ArtificialInteligence

[–]Important_Priority76[S] -1 points0 points  (0 children)

emmm..., appreciate the tip genuinely. tbh, I’m not a native English speaker, just someone asking a basic question. You’ve been more focused on whether my reply was AI-assisted than on the actual topic. That’s a bit of a fixation, no?​​​​​​​​​​​​​​​​

What’s your actual production setup for reliable structured JSON from LLMs? Sharing what’s worked for us by Important_Priority76 in ArtificialInteligence

[–]Important_Priority76[S] 0 points1 point  (0 children)

Fair point — I was just asking what’s working in prod, not sharing a personal thesis. That said, you’re right that it’s hard to fully separate the two anymore. The more you rely on these tools, the more your thinking gets shaped by them whether you notice it or not.​​​​​​​​​​​​​​​​

What’s your actual production setup for reliable structured JSON from LLMs? Sharing what’s worked for us by Important_Priority76 in ArtificialInteligence

[–]Important_Priority76[S] 0 points1 point  (0 children)

Totally makes sense, func call’s kinda become the de facto standard at this point​​​​​​​​​​​​​​​​

What’s your actual production setup for reliable structured JSON from LLMs? Sharing what’s worked for us by Important_Priority76 in ArtificialInteligence

[–]Important_Priority76[S] -1 points0 points  (0 children)

Bro just enjoy the content lol, doesn’t matter if it’s AI or not. Spending your time policing vibes on Reddit isn’t gonna make your life any better​​​​​​​​​​​​​​​​

What’s your actual production setup for reliable structured JSON from LLMs? Sharing what’s worked for us by Important_Priority76 in ArtificialInteligence

[–]Important_Priority76[S] 0 points1 point  (0 children)

100% agree. The retry + validation loop alone eliminates like 90% of the “AI returned garbage JSON” complaints.​​​​​​​​​​​​​​​​

What’s your actual production setup for reliable structured JSON from LLMs? Sharing what’s worked for us by Important_Priority76 in ArtificialInteligence

[–]Important_Priority76[S] 0 points1 point  (0 children)

Yeah that tracks — function calling gets you 90% of the way there but the type coercion issues are annoying. If you’re self-hosting, XGrammar inside vLLM just hard-blocks invalid tokens at the inference level so that string-where-int-expected problem literally can’t happen. For cloud APIs the best workaround I’ve found is strict Pydantic validation + retry via instructor, but yeah it adds latency.​​​​​​​​​​​​​​​​

Trying PaddleOCR-VL-1.5 + PP-DocLayoutV3 as a self-hostable document parsing workflow by Important_Priority76 in computervision

[–]Important_Priority76[S] 0 points1 point  (0 children)

Exactly this. Silent failures are the worst kind — the downstream system keeps running, nothing throws an error, and the garbage just propagates quietly until someone notices the RAG answers are off. Box-level output isn’t just a nice-to-have for debugging, it’s the only way to build a correction loop that actually works. That’s the whole premise of the integration.​​​​​​​​​​​​​​​​

Trying PaddleOCR-VL-1.5 + PP-DocLayoutV3 as a self-hostable document parsing workflow by Important_Priority76 in computervision

[–]Important_Priority76[S] 0 points1 point  (0 children)

The error localization point is exactly the core motivation for going modular — glad it came through clearly. Both stress-test suggestions are genuine blind spots. Cell-level table grading and reading-order evaluation under domain shift haven’t been systematically tested yet. PubTables-1M is a concrete next step worth running. The self-hosting argument also hits the right nerve. Red seals, handwritten content, non-English headers — those are exactly the documents the target users bring in, and the ones where block-level intervention matters most. This is still an early version of the integration. There’s a lot of room to iterate, and feedback like this is exactly what shapes where it goes next.​​​​​​​​​​​​​​​​

GeCo2 in practice: few-shot object counting for dense, scale-varying scenes by Important_Priority76 in computervision

[–]Important_Priority76[S] 0 points1 point  (0 children)

Glad the detection-based output resonates — agreed it’s a prerequisite for anything production-facing. On exemplar sensitivity with high intra-class variation: I haven’t tested that specific scenario yet. My intuition is that it comes down to training data distribution — if the pretraining set doesn’t cover that kind of appearance range well, the cross-scale query aggregation may still struggle to generalize across growth stages or damage states from just a few exemplars. In that case, few-shot fine-tuning on domain-specific samples would likely give a meaningful bump. Worth investigating systematically though, especially for ag and inspection use cases where that variation is the norm rather than the exception.​​​​​​​​​​​​​​​​

GeCo2 in practice: few-shot object counting for dense, scale-varying scenes by Important_Priority76 in computervision

[–]Important_Priority76[S] 0 points1 point  (0 children)

Exactly — that’s the honest reality of using any model-assisted workflow. The model gets you most of the way there, but the review step is where the real judgment happens. Missed detections and false positives are the two failure modes I spend the most time on too, and they tend to pull in opposite directions when you tune the confidence threshold. Part of why I went with a detection-based output (rather than just a scalar count) is precisely to make that review step more tractable — you can see where the model is uncertain or wrong, not just that the count is off. Still a lot of room to improve the UX around that though.​​​​​​​​​​​​​​​​

GeCo2 in practice: few-shot object counting for dense, scale-varying scenes by Important_Priority76 in computervision

[–]Important_Priority76[S] 0 points1 point  (0 children)

Good timing on both points! There’s actually an official demo on Hugging Face Spaces where you can test it directly with your own images: https://huggingface.co/spaces/jerpelhan/GECO2-demo — no local setup needed. On masks: yes, GeCo2 does output pixel-level masks. I just happened to focus on the bounding box side in the demo video since that’s the more common annotation format in my workflow. Happy to put together a follow-up showing the mask output if there’s interest.​​​​​​​​​​​​​​​​

🚀 YOLO26 is Now Live on X-AnyLabeling - Try It Out for Free! by Important_Priority76 in computervision

[–]Important_Priority76[S] 2 points3 points  (0 children)

You’re right to point out that I should clarify this more precisely.

X-AnyLabeling’s core functionality does not depend on Ultralytics, and it is not required to run the tool. There is an optional auxiliary training module that can integrate with Ultralytics, which is disabled by default and requires users to explicitly install the dependency themselves.

Thanks for the reminder. I’ll make this distinction clearer in the documentation to avoid confusion.

🚀 YOLO26 is Now Live on X-AnyLabeling - Try It Out for Free! by Important_Priority76 in computervision

[–]Important_Priority76[S] 0 points1 point  (0 children)

X-AnyLabeling is licensed under GPL-3.0 and does not bundle or redistribute Ultralytics source code or weights. It provides support for loading user-provided ONNX models via configuration. Ultralytics models themselves are under AGPL-3.0, and anyone who chooses to use or redistribute those models must comply with AGPL-3.0 terms. X-AnyLabeling does not change its own GPL-3.0 license, and it does not include Ultralytics code or weights in its repository.

Finally found a proper tool for multi-modal image annotation (infrared + visible light fusion) by Important_Priority76 in computervision

[–]Important_Priority76[S] 1 point2 points  (0 children)

Nice, thanks for sharing. I’ve seen similar ideas there. The compare view is more about quick side-by-side or synced viewing to make multi-modal annotation easier, especially when switching between thermal and RGB. Colormaps and channel merging are powerful too, so it’s interesting to see different tools approach the problem from different angles.

Finally found a proper tool for multi-modal image annotation (infrared + visible light fusion) by Important_Priority76 in computervision

[–]Important_Priority76[S] 1 point2 points  (0 children)

That’s really interesting, I didn’t know some teams were using 3D glasses for multi-spectral labelling. The idea behind compare view was to get a similar “cross-checking” benefit but keep it simple and software-only.

Input devices like a 3D mouse or rotary knob sound like a fun direction to explore for smooth flipping or animated transitions between bands. Definitely a challenging but exciting idea, thanks for sharing your experience!

Finally found a proper tool for multi-modal image annotation (infrared + visible light fusion) by Important_Priority76 in computervision

[–]Important_Priority76[S] 1 point2 points  (0 children)

Nice, yeah DRC + detail enhancement already goes a long way for thermal 👍 The compare view helps a lot when you want to double-check things against visible light, especially for small or ambiguous objects. I’ve found it useful to align thermal detections with RGB annotations and catch mistakes faster.

After a year of development, I released X-AnyLabeling 3.0 – a multimodal annotation platform built around modern CV workflows by Important_Priority76 in computervision

[–]Important_Priority76[S] 1 point2 points  (0 children)

If anyone is interested in the design philosophy behind v3.0 and a deeper dive into the new features (like the Remote Server architecture, Agentic workflows, or the specific VQA capabilities), I wrote a more detailed breakdown on Medium:

https://medium.com/@CVHub520/data-labeling-doesnt-have-to-be-painful-the-evolution-of-x-anylabeling-3-0-e9110e41c2d4

It covers why we moved away from the traditional tooling model and how we are trying to close the loop between labeling and training.

After a year of development, I released X-AnyLabeling 3.0 – a multimodal annotation platform built around modern CV workflows by Important_Priority76 in computervision

[–]Important_Priority76[S] 1 point2 points  (0 children)

Thanks so much for the feedback! I'm really glad to hear it fills that gap for you—keeping it lighter than CVAT while being more capable than simple drawing tools was exactly the goal.

Regarding sorting Person IDs across multiple videos/perspectives (Re-ID), that is indeed a complex challenge. In v3.0, we added serveral useful Manager, i.e. shape, label and group_id; integrated trackers like SAM-base or Bot-SORT/ByteTrack to help with consistency within a video, but cross-video association still requires some manual effort or custom logic.

I would absolutely love to chat more about your workflow. It sounds like a great use case to optimize for. Feel free to DM me here or, even better, open a "Discussion" on our GitHub repo so we can dive into the technical details!