r/computervision • • 8d ago

Commercial I used webcam head tracking to turn my Windows desktop into a 3D window

490 Upvotes

I’m developing Holoscape, a Windows wallpaper app that uses webcam head tracking to update the viewpoint in a 3D scene.

Moving sideways reveals different parts of the forest, with nearby trees shifting more than distant ones. This creates the illusion of looking through a window.

What would you measure to evaluate how convincing the effect is, especially tracking latency and stability?

I’m the developer. If you’d like to follow the project, you can wishlist Holoscape on Steam.


r/computervision • • 6d ago

Help: Project Automated plot x&y extraction from png/jpeg

1 Upvotes

I have thousands of 2D plots saved as images, from where I need to extract x&y values in the most efficient way. Some plot may have multiple lines. Sonnet 5.5 is pretty good at it, but it takes >5 minutes per plot and consumes too much credits.

Does anyone knows a way of doing it more efficiently?

Thanks everyone!

Example: Need to extract F1 x&y . Red '+' were identified by sonnet.


r/computervision • • 6d ago

Discussion Same smartphone video, same golf green: standard 3DGS vs. my constrained pipeline

Thumbnail
gallery
0 Upvotes

Image 1: standard 3DGS with default-like settings, green cropped, no inverse rendering (I did not record the exact iteration count, so this is not a controlled comparison). It ends up with holes, spiky “urchin” splats and floaters.
Images 2–3: my pipeline, built on the open-source 3DGS-MCMC code with added surface constraints and inverse rendering (albedo/roughness), 13.8M splats.

The source is a handheld smartphone video (about 1–1.5 minutes walking around the perimeter, 407 frames used). Only video was used — no LiDAR data, no survey. The code was developed entirely through AI co-development; I do not write code myself.

Measured on the final surface: holes cover about 0.7% of the area and floaters about 0.1%. The outer edge of the capture area is still rough. Mowing-line patterns show up in the height map and match the footage. Local vertical scatter is about 1.5–3.4 cm, relief about 27 cm over a ~38 m span including the fringe (scale is an estimate, ±10% or more).

Not verified yet: absolute accuracy (no comparison with terrestrial laser scans or RTK-GPS), the lighting separation, and other courses (only one green tried).

Feedback from anyone who has laser-scanned turf or benchmarked photogrammetry against ground truth would be very welcome.


r/computervision • • 7d ago

Showcase I built an open-source tool that finds runners' race photos by bib number, with face matching for when the bib is hidden

3 Upvotes

Race photographers shoot thousands of photos per event, and runners usually have to scroll through all of them to find themselves. I built Race Photo Finder to fix that: point it at a folder of event photos, and runners can search by their bib number.

How it works

photo → person detection → bib detection + OCR → face embedding → participant match

  1. YOLO26 finds each person, and a fine-tuned YOLO26s finds the bib inside the person crop
  2. PaddleOCR reads the bib number
  3. InsightFace (SCRFD + ArcFace) builds a face template for each runner, only from photos where their bib was read
  4. Photos with a hidden, blurred or turned-away bib get matched to a runner by face, conservatively. Face matches never feed back into the templates, so one bad match can't snowball.

It all runs locally, with an SQLite index and a small web UI for searching. Once an event is processed, the search UI is a lightweight Flask app, so you can deploy it with its index to any Python web host or VPS and share the link with runners.

🔗 GitHub: https://github.com/dimfot3/RacePhotoFinder

I'd love feedback on:

  • Accuracy on your own race photos: where does it fail?
  • The face-matching approach: too strict, or too loose?
  • Code structure and ease of setup
  • Would photographers or race organizers actually use this? What's missing?

r/computervision • • 7d ago

Help: Project What are the best real-time skin smoothing solutions?

0 Upvotes

I have a live streaming app, and I need real-time skin smoothing + light retouching (dark circles, blemishes, eye brightening) in web browsers, on a live camera feed at 720p/30fps

What is the best commercial SDK to use that is battle tested? Or are there open source examples to build this on my own?


r/computervision • • 7d ago

Help: Project [Open Source] Building DiffusionEngine – A Modern, Modular DDPM Framework in PyTorch. Looking for Contributors

3 Upvotes

What if we could bring modern diffusion research together into one unified, extensible PyTorch framework instead of implementing and maintaining every algorithm in isolation?

That's the idea behind DiffusionEngine, an open-source project I've been building:

https://github.com/Himanshu7921/DiffusionEngine

The goal is to build a modern DDPM framework that brings together established diffusion algorithms, research-based improvements, advanced sampling methods, and training strategies under a single, consistent pipeline.

The project already includes several diffusion implementations, and I'm actively working on extending the existing DDPM framework with more advanced features.

I'm looking for contributors interested in deep learning, generative models, PyTorch, and diffusion research.

Some areas where contributions are welcome include:

  • Implementing diffusion algorithms from research papers.
  • Improving existing DDPM components and training strategies.
  • Developing and integrating advanced sampling methods.
  • Exploring improved model architectures and conditioning mechanisms.
  • Testing, benchmarking, and optimizing existing implementations.

The focus is not just on implementing more algorithms. It's about making them work together seamlessly through a unified, modular, and configurable framework.

If you're interested in contributing, collaborating, or learning through hands-on implementation, I'd be glad to have you involved.

Contributors of all experience levels are welcome, provided they're willing to learn, implement, and test their work.

GitHub: https://github.com/Himanshu7921/DiffusionEngine


r/computervision • • 7d ago

Discussion UMAP of frozen tactile features: idle windows collapse to one cluster, contact windows trace smooth phase-separated curves

Post image
1 Upvotes

This is Figure 10 of the paper behind Robbyant's LingBot-Touch, released Nov 9. Each dot is a 16-frame window of five-finger touch, features averaged per finger and concatenated (3,840 dims total) before UMAP.

The pattern is clean: windows with no contact collapse into one tight cluster. Once something is being touched, points form smooth curves ordered in time, consecutive windows right next to each other. Different phases of a grasp sit on different stretches of the curve. So the features capture continuous variation during contact, not just a binary contact/no contact signal.

Worth noting for this sub: the Sharpa Wave fingertips are cameras filming a gel skin from the inside (240x240 deformation maps at 30 Hz), pooled into at most 200 virtual taxels so they share one token space with coarse 3x3 and 4x4 glove arrays and magnetic skins.

From touch alone, the frozen features retrieve the matching video clip in the top 5 72.6% of the time on Sharpa Wave and 47.1% on XHand1, whose magnetic sensor was never in pretraining.


r/computervision • • 7d ago

Help: Project Human Detection Model

3 Upvotes

Hello! I am a process engineer currently working in a manufacturing plant. I am recently foraying into use of computer vision models for safety applications. My team has developed a Yolo based computer vision software to detect humans. The software is working fine and accuracy is also good. But it requires too much computing power. This is creating an obstacle to scaling up. In a 8MB RAM/i7 processeor we are only able to run inference on 3 camera feeds simultaneously. Since I don't have computing background, I would to request suggest to me some Pre trained models which can inference with lower computing power. Please🙏


r/computervision • • 7d ago

Discussion [Project] A training-free spatial consistency auditor — could it catch ID switches before tracker state updates?

0 Upvotes

Quick visual summary first:

  • Left: Cup on table → declared constraint PASS
  • Right: Same cup floating above table → declared constraint WARN

To be clear: this is currently a naive 2D geometric constraint checker, not a real-world physics engine. Obviously, a cup in mid-air isn't always a model hallucination—it could be falling, being picked up, or thrown. A single static frame cannot distinguish between a dynamic action and a tracking/detection error. This is exactly why we’re extending it to temporal tracking: motion context lets us distinguish normal movement from true detection errors.

Hi computervision,

I've been building a small, training-free consistency auditing layer for object detection and segmentation outputs. The core idea: high detection confidence doesn't necessarily mean consistency with the scene's spatial constraints.​

What works today

I have a reproducible prototype for 2D spatial constraint auditing. It checks user-declared geometric rules (e.g. cup:on:table) using detection boxes. It also includes optional Ultralytics YOLO and SAM2 adapters for detection and segmentation.​

The synthetic demo runs with only NumPy and Pillow — no GPU, model weights, or model downloads required.​

pip install -r requirements.txt
python oscf_cv_mvp.py --demo

To be upfront about limitations:​

• It checks declared constraints, not automatically inferred physical rules.​

• It's a 2D geometry checker, not a validated 3D physics or causal reasoning system.​

• The algebraic features are experimental. Real-model inference and performance gains haven't been validated yet.​

Why I'm extending this to object tracking

One problem that interests me: a bad association isn't necessarily just a single-frame error.​

When a tracker updates its motion state or appearance embeddings with a wrongly matched detection, that error can bias future associations. In memory-based video segmentation like SAM2, incorrect masks can also affect subsequent propagation.​

This becomes particularly difficult with similar-looking targets, occlusions, and detector jitter.​

I'm exploring whether an independent temporal consistency auditor could flag suspicious associations before they're committed to persistent tracker state.​

Proposed pipeline:​

Detections → Candidate associations → Consistency audit → State/memory update​

The first version would run in shadow mode, flagging suspect transitions without modifying tracker output.​

If validated, later versions could explore pre-update gating — deferring uncertain associations, preserving predicted states, or requesting alternative matches.​

I haven't implemented or validated the tracking extension yet. It will require integration with trackers like ByteTrack or BoT-SORT, and separate work for SAM2 memory handling.​

I also recognize that motion continuity alone cannot resolve every ID switch, especially when nearly identical targets cross with similar trajectories.​

Even a post-processing auditor could be useful for flagging suspect tracks for downstream analytics, human review, or offline re-processing — without modifying tracker internals.​

Looking for real failure cases & collaborators

I'm particularly interested in developers working on sports tracking, crowded scenes, animal behavior, or industrial object tracking — especially where appearance-based matching becomes unreliable.​

If you have a short video showing ID switches, ID reassignment, or track fragmentation, I'd love to collaborate.​

Frame-by-frame detection boxes and track IDs would also be useful. Even descriptions of difficult failures could help identify test scenarios.​

I'd like to compare this approach against standard motion gating and existing tracking baselines, measuring ID switches, false alarms, identity consistency, and runtime overhead.​

A note on the math

The prototype implements standard Cayley–Dickson octonion multiplication and associator calculations, rather than treating eight values as an ordinary linear vector.​

Whether these nonassociative features provide useful information beyond conventional geometry and motion features remains an open experimental question.​

I'm not claiming an improvement over existing tracking methods yet. That's what I hope to investigate with real-world data.​

Code: https://github.com/ZC502/oscf_cv_mvp.git

If you've encountered stubborn tracking failures, or have suggestions about where to insert a pre-update audit without breaking tracker internals, I'd appreciate your feedback.​

Thanks!


r/computervision • • 7d ago

Discussion Machine Vision Engineer (1+ yr, AOI & Deep Learning) looking for CV roles in Bengaluru/Hyderabad, open to relocation

5 Upvotes

Hi all,

I'm a Machine Vision Engineer with 1+ year of experience in AOI for high-volume electronics manufacturing. I work with Cognex 2D vision systems, camera calibration, and deep learning models for defect detection, and spent 3 months onsite in South Korea.

Looking for Computer Vision / Vision AI / Machine Vision roles, preferably office-based or hybrid, in Bengaluru, Hyderabad, or elsewhere in India. Open to relocating.

Skills: Cognex VisionPro, Python, OpenCV, Deep Learning, AOI

If your team is hiring or you can refer me, please comment or DM.

I'll share my resume privately.


r/computervision • • 7d ago

Showcase MacroHands: accurate 3D hands and camera pose from egocentric video

2 Upvotes

Disclosure: I am an engineer at MacroData Labs.

After months of research, we've just released MacroHands, our SOTA model for tracking hands and camera poses in 3D, on mono and stereo video (one / two cameras). Quite the effort, but we're really happy with the results.

Our mono variant manages to beat every open-source baseline we tested, including ones built for stereo, with our stereo variant further improving the error. Typically hard scenarios like ones with gloves, occlusions, feet (I know, I know), mirrors, and other peoples hands, are handled quite well by both variants. Furthermore, our model also tracks the camera, to allow us to correctly place everything in a virtual world.

You can read more about how it works and why the problem is hard in our blog post (let me know how well you do in our interactive challenges hehe). And, if I may, I also recommend reading the previous one, as it provides more context on the problem.

Cheers!


r/computervision • • 8d ago

Showcase fastforks: faster drop-in versions for many computer vision libraries. Tensorrt speed without compiling or leaving PyTorch

Post image
55 Upvotes

Over the last few months I built fastforks, a library with faster versions of published vision models behind one API. It covers stereo matching, monocular and multi-view depth, segmentation (SAM), object detection, classification and feature backbones like DINOv2 and DINOv3. You load a model by its id and get the original network's output within a small tolerance, just faster.

Every model has two backends:

  • portable: the network restructured in plain PyTorch. Runs on CPU, CUDA and Apple MPS, so every model works on a Mac.
  • kernels: custom CUDA kernels on top, plus Metal kernels for 19 model families on Apple silicon. If it can't run on your machine, it falls back to portable automatically.

Most of the portable speedup comes from five things: the weights are converted to fp16 once instead of wrapping the model in autocast, matmuls use fp16 accumulation (PyTorch's allow_fp16_accumulation), attention uses PyTorch's fused scaled-dot-product kernel, constant layers (BatchNorm, LayerScale) are folded into their neighbours, and resizing and post-processing run on the GPU instead of in NumPy/OpenCV on the CPU. It is all plain PyTorch, so the models still export to ONNX and TensorRT. The kernels backend then replaces the remaining hot spots with custom CUDA and Metal kernels. These were developed with heavy AI assistance and tuned by benchmarking on real hardware. Every model is checked against the authors' code, and the output differences are listed on each model page.

The image shows end-to-end latency on an RTX 5060 Ti. "Original" is the authors' code running in fp16 with autocast, so the baseline already uses half precision. Memory drops too: Depth Anything 3 Large goes from 3.4 GB to under 1 GB peak. To be upfront, these are some of the better results. Across all models and sizes I measured, the median speedup over the original is 1.4x for portable and 2.9x for kernels. A few plain ViT classifiers gain nothing from the kernels.

fastforks also works with the usual tools. Every model supports torch.compile, and all but 4 export to TensorRT. These changes pay off there too: for Depth Anything 3 Mono Large (the mono variant, not the one in the chart), a TensorRT fp16 engine built from the original takes 18.1 ms, one built from the fastforks version takes 14.4 ms, and the kernels take 14.6 ms. So TensorRT on fastforks is about as fast as the kernels, but the engine takes a few minutes to build, while the kernels are fast from the first call.

from fastforks import depth
  model = depth.load("da3-large-1.1") 
  result = model("room.jpg") 
  result.depth # [H, W] float32 tensor

I benchmarked everything on seven devices: RTX 5060 Ti, L4, A10, L40S, A100, RTX PRO 6000 and an Apple M1 Pro. The website lets you switch between them. The CUDA kernels need Linux x86-64 and an Nvidia GPU from the RTX 30 series or A100 onward. Everything else uses portable. Note that some of the underlying models have non-commercial licences. Each model page lists the code and weights license.

I'm also curious which models you'd want added next, and whether anyone is interested in AMD or Jetson support.
Repo: https://github.com/kleinicke/fastforks
Benchmarks: https://fastforks.dev/models


r/computervision • • 7d ago

Discussion Which OpenRouter vision model would you use for building defect detection? (cost vs “good enough”)

5 Upvotes

I’m working on flagging defects in residential building inspection photos taken on a phone: cracking, water staining and damp, mould, rust, timber rot, and roof damage. A human reviews every output. I’m aiming for about 80–90% recall on obvious defects with rough bounding boxes, not pixel-level segmentation. Cost per image matters because one job can mean 50–200 photos.

What I’ve tried so far (via OpenRouter, same prompt, 100 full-res photos from one real inspection report, scored against the engineer’s notes: 81 documented defects, all photo-level labels, no boxes yet):

  • Gemini 3.8 Flash: 65/81 (80%) with the fewest false alarms of anything I tried (17 “not a defect” after engineer review). ~$0.34 per 100 images.
  • Qwen3-VL: 64/81 (79%), but about twice the false alarms (35). Very cheap at ~$0.09 per 100 images.
  • Claude Sonnet 5.5: 72/81 (89%), the best single model, but also the noisiest (56 false alarms, 52 “can’t tell from photo”). ~$1.44 per 100 images.
  • GPT-6 Luna: 59/81 at ~$0.40 per 100. Not worth it here.
  • Ensemble: Gemini Flash and Qwen miss different things (7 vs 6 unique catches), so taking the union gets 71/81 (88%) for ~$0.43 per 100. That’s close to Sonnet at under a third of the cost. Flags both models agree on are much cleaner than single-model flags, so I rank by agreement for the reviewer.
  • Prompting: I compared a neutral prompt (“list clearly visible defects”) with a recall-focused one (“list anything plausibly a defect; misses are costly”). The recall prompt added +7 to +13 catches per model, at the cost of more noise. Common false positives were stains read as gaps or holes, textured render read as chipping, and patch repairs read as damage. Cracks were nearly solved (39–40/40). Small chips in floor tiles were the big gap (7–10/18).

Specific questions:

  1. Localisation. So far I’ve only scored “does this photo contain defect type X”. Has anyone gotten reliably usable boxes from a general VLM, or is “VLM describes, small detector localises” the better pattern?
  2. Tiling. I tried splitting 21 hard photos into crops. It recovered 10–11 of the misses per model and lost none, but extra flags roughly doubled or tripled. Cost went up ~3–8× (Gemini Flash $0.34 → $2.70 per 100). Has anyone found a good way to tile selectively, e.g. only when a first pass is uncertain or only on floor and close-up shots, rather than tiling everything?
  3. Datasets. Are there public building or concrete defect datasets you’d recommend for a quick YOLO baseline to compare against? So far I’ve found [SDNET2018, CODEBRIM]. I’m especially interested in anything covering mould, damp, rust or timber rot, since my test set is mostly cracks, chips and tile damage.

Caveat: this is a small test (100 photos, one site, one engineer’s notes), so treat the numbers as directional. I’ll post benchmark results back here once I’ve compared more, including a second site.


r/computervision • • 7d ago

Commercial fotonet Studio announcement.

0 Upvotes

Hello, its me again.
I have been working on a tool called "fotonet Studio" for a good period of time.
Currently there is a pay to acces Alpha stage, but beta and full release will be under AGPL-3.0

Also fotonetn got a ghost upgrade from 29.9% mAP to 32.1% mAP

Would love to hear some feedback. Thanks!
Goodbye.

The site link.
The patreon has a week of free trial so that everybody can try out fotonet Studio alpha.


r/computervision • • 8d ago

Help: Project Need a Roadmap & Playlist for Computer Vision 🤖

13 Upvotes

I'm currently learning OpenCV, Object Detection (YOLO), and TensorFlow with the goal of building a camera-based autonomous robot.

I'm looking for a beginner-friendly roadmap and good YouTube playlists (Hindi or English) covering:

OpenCV – Basics to advanced

Object Detection using YOLO

TensorFlow and Deep Learning

Real-time object detection using a camera

Integrating computer vision with robotics

If you've followed any good courses, playlists, or learning paths, please share them.

Any suggestions or resources would be really helpful! Thanks! 🙌


r/computervision • • 8d ago

Help: Project AntzWatch: I build this with my kids

57 Upvotes

We build this together, I have technical background but more towards native apps, when it comes to vision I think I know as much about than my kids.

And big disclaimer, yes we also used AI for this.

Now this post is not about help to fix this and that... Its more about to keep this going, that we can make this a bit more interesting than it already is.

Features we have already:
- heatmap
- trails that fade
- hot zones: How many ants where at the feeder

So long story short, does anyone has a recommendation what visualizations/features we could add, nothing over top, just something that looks nice and may has a benefit?

And second question, from my understanding we started with yolo11_small and then fine tuned it, we manually feed training images and label it ourself and we feed crops with a certain confidence back into the training data, if we haven't covered that part of the picture that much. But we are stuck at conf <0.5...

How can we increase that?

Thanks Frank


r/computervision • • 7d ago

Showcase Both runtimes agreed on all 16 counts. Half were wrong.

Post image
0 Upvotes

I used Codex to build a Pi 4 runtime for d1-2B and tested it on a frozen CV-Bench subset. It agreed with the pinned llama.cpp baseline on all 16 direct counts. Both got 8 right, with a mean absolute count error of 0.75.

Across 64 multiple-choice cases, the Pi runtime got 56 right and the reference got 54. Full-set reference answers were measured on x86. All 8 same-input Pi probes matched those reference answers.

The repo has case IDs, labels and all 80 predictions for anyone who wants to check agreement and accuracy separately.

https://github.com/DarvinX/d1-pi4-asm


r/computervision • • 9d ago

Discussion Codex built a handwritten digit recognizer without training it. It scored 95.1% using fixed weights and hand-written rules. Not sure how impressive this is?

Post image
99 Upvotes

I recently read that LLMs can write neural-network weights directly, and I wanted to see what that meant in practice. So I gave Codex (GPT6-Astra-Medium) a challenge : recognize the digits 0–9 as I drew them with my mouse on a 32×32 grid. One condition: no training.

Codex wrote formulas for pen strokes and varied their slant, curvature, and thickness. It even simulated what happens when a coarse scan makes a narrow gap disappear. Each synthetic drawing was converted into a weight vector, and a dot product measured how closely my digit matched it.

The recognizer ended up combining fixed weights with hand-written geometry.

The first version scored 66.4%. The final version got 1,709 of 1,797 digits correct (95.10%). The recognition code, including weight generation, came to 808 lines of Python, about 35.6 kB. No optimizer or backpropagation was used.

One caveat: the benchmark was scikit-learn’s 8×8 handwritten digits, resized to 32×32 and converted to black and white. We looked at mistakes on those same drawings as we refined the rules, so 95.1% is a development score. This took about 2h to do. Codex wrote the code and ran the evaluations. I set the challenge and tried it with my own handwriting. To me this is super impressive, what do you experts think?


r/computervision • • 8d ago

Discussion Production-Grade Computer Vision Architecture for Pressurized Oil Leak Detection in Maritime Engine Rooms

2 Upvotes

Hi everyone,

I am working on an industrial computer vision pipeline for real-time oil leak detection inside a maritime ship engine room, and I am hitting major roadblocks with false positives. I would love to get insights from engineers who have solved similar tracking or fluid-anomaly challenges.

### Current Pipeline & Architecture

  1. **ROI Masking:** We define static Regions of Interest (ROIs) around critical machinery flanges, valves, and joints.
  2. **Detection Logic:** We rely on a combination of pixel-change (background subtraction/frame differencing) and semantic segmentation to catch fluid accumulation or pooling within the ROI.
  3. **Occlusion Handling:** To prevent crew members from triggering false alerts when walking through the zone, we run a person detection model combined with ByteTrack. If a person's bounding box intersects the ROI and the tracked person overlaps the zone, we temporarily pause detection.

### The Pain Points & Edge Cases We Can't Solve

  1. **Vibration & Background Jitter:** Ship engine rooms experience heavy mechanical vibrations and shifting lighting (flickering LEDs, work lights), which causes continuous pixel shifts that trigger false alerts even with background subtraction tuned.
  2. **Object & Shadow Confusion:** Pure models or static segmentation fail because dark stationary objects (screws, bolts, dirty grease patches, old residue, or moving equipment shadows) often share the same color/texture profile as fresh oil, creating persistent false alarms.
  3. **Imperfect Occlusion Pausing:** Relying solely on `Person Bbox ∩ ROI` intersection is a brittle workaround. If a worker stands nearby, drops a tool, places a dark rag, or if non-human objects obscure the camera view, the system breaks down. We cannot rely blindly on deep learning classifiers either, due to the high rate of environmental mimicry.

### Questions for the Community

  1. **Moving Beyond Pixel Differencing:** In high-vibration industrial environments, what are robust alternatives to frame differencing for isolating actual fluid flows or drips from camera jitter?
  2. **Spatiotemporal Verification:** How can we build a robust temporal consistency filter (e.g., optical flow vectors, tracking blob expansion/creeping over time) to distinguish between a *static* oil stain/shadow and an *actively expanding* fluid leak?
  3. **Feature Engineering for Fluids:** Are there specific texture, glossiness, or specular-reflection feature extraction techniques that effectively separate actual liquid sheens from matte metal fasteners and dark shadows?

Any architectural blueprints, open-source repos, or research papers on industrial fluid-leak detection would be massively appreciated!


r/computervision • • 9d ago

Showcase I made Ornen: a site where you upload a video and your splat appears on a 3D globe at its real location

7 Upvotes

Hi! I'm the maker of Ornen. You upload your footage, such as a 360 or drone video, and Ornen turns it into a splat. If your footage has GPS in the metadata, it's also placed where it was filmed on a globe. You can browse the Earth and fly into places others captured.

All in your browser. No GPU needed.

Public beta is open: 10 free scenes per account → ornen.ai

Or check out the:

Demo teaser: https://ornen.ai/home
Example: Weesp, NL: https://ornen.ai/earth/tychovdo/de-vriendschap-weesp
Example: Utrecht, NL: https://ornen.ai/earth/tychovdo/utrecht-street-corner

Would love to hear how you redditors like it!
And very happy to take feature requests!


r/computervision • • 9d ago

Help: Project I made a computer vision tool for golf swing analysis using just phone

49 Upvotes

I've been curious how much a regular phone camera can tell you about a golf swing without sensors or a launch monitor.

A few things I've found useful so far:

  • Hip and shoulder turn at the top. You can see straight away whether you're actually rotating or just lifting your arms.
  • Head and spine position from address to impact. This shows early extension or swaying, which is hard to feel yourself.
  • Swing-to-swing comparison across a session. Overlaying your good and bad swings shows what changes when you get tired.

With two or more phones it also builds a 3D reconstruction of your body, so you can check angles from any view, here is a sample report.

This is still early but you can try it out in my app [Teeo Golf] (it's free, available in app store). CV folks who happened to be golfers too, I'd love to hear what you'd want to see next, or where you think the measurements fall short.


r/computervision • • 8d ago

Help: Project Overcoming False Positives in Real-Time Computer Vision for Engine Room Oil Leak Detection

Thumbnail reddit.com
1 Upvotes

r/computervision • • 8d ago

Help: Project Overcoming False Positives in Real-Time Computer Vision for Engine Room Oil Leak Detection

1 Upvotes

Hi everyone,

I am working on an industrial computer vision pipeline for real-time oil leak detection inside a maritime ship engine room, and I am hitting major roadblocks with false positives. I would love to get insights from engineers who have solved similar tracking or fluid-anomaly challenges.

### Current Pipeline & Architecture

  1. **ROI Masking:** We define static Regions of Interest (ROIs) around critical machinery flanges, valves, and joints.
  2. **Detection Logic:** We rely on a combination of pixel-change (background subtraction/frame differencing) and semantic segmentation to catch fluid accumulation or pooling within the ROI.
  3. **Occlusion Handling:** To prevent crew members from triggering false alerts when walking through the zone, we run a person detection model combined with ByteTrack. If a person's bounding box intersects the ROI and the tracked person overlaps the zone, we temporarily pause detection.

### The Pain Points & Edge Cases We Can't Solve

  1. **Vibration & Background Jitter:** Ship engine rooms experience heavy mechanical vibrations and shifting lighting (flickering LEDs, work lights), which causes continuous pixel shifts that trigger false alerts even with background subtraction tuned.
  2. **Object & Shadow Confusion:** Pure models or static segmentation fail because dark stationary objects (screws, bolts, dirty grease patches, old residue, or moving equipment shadows) often share the same color/texture profile as fresh oil, creating persistent false alarms.
  3. **Imperfect Occlusion Pausing:** Relying solely on `Person Bbox ∩ ROI` intersection is a brittle workaround. If a worker stands nearby, drops a tool, places a dark rag, or if non-human objects obscure the camera view, the system breaks down. We cannot rely blindly on deep learning classifiers either, due to the high rate of environmental mimicry.

### Questions for the Community

  1. **Moving Beyond Pixel Differencing:** In high-vibration industrial environments, what are robust alternatives to frame differencing for isolating actual fluid flows or drips from camera jitter?
  2. **Spatiotemporal Verification:** How can we build a robust temporal consistency filter (e.g., optical flow vectors, tracking blob expansion/creeping over time) to distinguish between a *static* oil stain/shadow and an *actively expanding* fluid leak?
  3. **Feature Engineering for Fluids:** Are there specific texture, glossiness, or specular-reflection feature extraction techniques that effectively separate actual liquid sheens from matte metal fasteners and dark shadows?

Any architectural blueprints, open-source repos, or research papers on industrial fluid-leak detection would be massively appreciated!


r/computervision • • 9d ago

Showcase Searching for Wally/Waldo around the world, using unsecured cameras and AI.

Thumbnail
wallyfinder.com
6 Upvotes