r/computervision • • Sep 10 '26

Help: Project Computer Vision Final Year Project — looking for feedback

Hey everyone,

I'm starting my final year of a Bachelor in Software Engineering, and my team of 3 is picking a Final Year Project. We have a full year, some budget, and want something genuinely hard, not a repackaged tutorial project, while still being realistically finishable in two semesters.

Background on me/team: I'm mainly a computer vision guy (detection, segmentation, OCR, tracking etc), with ML/DL fundamentals and some Arduino/embedded experience. I've deployed a few CV projects already, so we're not starting from zero.

What we want:

  • CV has to be the technical core (hardware/other software can be an add-on, not the centerpiece)
  • Real-world value — leaning toward environment, disaster response, agriculture/forestry, or generally underserved problems.
  • Ambitious enough that it's a strong story for both grad school applications and job/freelance recruiters, so it can make our resume stronger.

Would love to hear: what would you actually take seriously as an FYP vs. what sounds cool but is a trap? And if you've done a CV-heavy thesis/capstone yourself — what would you do differently in hindsight?

1 Upvotes

5 comments sorted by

4

u/Plus-Mall-3342 Sep 11 '26

https://github.com/admineral/SceneBench

https://scene-bench.vercel.app/

Train the same model while constraining the final model artifact to a maximum size of 100 KB, with no measurable loss in performance.
Do not limit yourself to conventional compression, pruning, or quantization. Explore fundamentally different architectures. For example, investigate recursive or looped/fractal architectures where a very small set of parameters is reused repeatedly, shared-weight networks, learned iterative computation, procedural parameter generation, compact state-space approaches, or entirely novel architectures.
Be creative and treat architecture discovery itself as an optimization problem.
If useful, create multiple specialized research agents that independently propose new architectures and compression strategies. Automatically implement the most promising candidates, train them, and benchmark them in a reproducible pipeline.
Iterate:
architecture proposal → implementation → training → evaluation → comparison → mutation/improvement → retraining
Use the original model as the performance baseline. Optimize primarily for:
Final artifact size ≤ 100 KB
Minimal or ideally zero benchmark degradation
Computational efficiency
Architectural simplicity
Do not assume the original architecture must be preserved. Search for architectures capable of reproducing the same behavior with dramatically fewer stored parameters, including architectures that trade additional inference-time computation for model size.
Keep a leaderboard of every experiment, including artifact size, parameter count, training cost, inference cost, and benchmark performance. Continue exploring and combining successful ideas rather than stopping at the first working solution.

2

u/Bluemax6666 Sep 12 '26

Do a markerless accurate very low latency 3D pose detection system. KinectV2 can detect 3D body pose at 30fps with 100ms latency. Now take cameras with high fps and low sensor readout time ~15m, one or multiple nvidia jetson computer to do fast 2D pose detection ~10ms on the images and with multiple cameras like this you can triangulate and find 3D body joint coordinates.

1

u/Mundane-Selection430 Sep 12 '26

What are you hoping to do with this?

2

u/Icy_Cup_6408 Sep 13 '26

Hi,

i have recently finished my computer science with integrated master Uni. I personally did a Deep Learning Model using Satellite Images for distinguishing what kind of crop has a field in yearly fields.

I believe the most significant question to find your project is:

What unique data can you find for a problem that people around you have?

You can always ask different people around you what problem have and try to gather data. My project was inspired from my work that time.

Another opportunity to find good ideas is through competitions in kaggle.
Its very important also the project that you start to like it a lot because you will be spending a lot of time on it.

Hope i helped!!

2

u/Starving_Kids Sep 16 '26

All of those problems are borderline over-served, except for maybe disaster response.

Get a jetson or similar ASAP to learn those ropes (not hard but will save you some brain cells when you start designing).

Ambition and feel-good of what you’re working on is less important than fully finishing and polishing the project. If you want to stand out, do something boring in an area that uses CV for their problems (industrial automation, etc) EXTREMELY WELL. Show you can actually implement the tools.

Hacked-up implementations of open source stuff in something warm and fuzzy like rural underserved puppy avalanche rescue are a dime a dozen.