FCP Contact

Version 0.2

One fisheye camera. Lanes, vehicles, lights and signs.

FCP is an open-source front-camera perception and ADAS stack. It uses only open models, public datasets and published methods, and it runs on real recordings today.

Gap to CIPV
34.0 m
Closing speed
0.0 m/s
Time to collision
not closing
Collision warning
Off
The CIPV logic on a test bench. The yellow car is the closest in-path vehicle; the car in the next lane is not. Point at the road to move it. The numbers come from a simple model of this figure, not from FCP, with the warning at a time to collision below 2.6 s.

What the camera finds

FCP shows only what applies to your lane: the vehicle you follow, the light you must obey, the sign that is for you.

Driving functions, open loop

Three functions run on top of the perception output. They compute what the car should do, but they do not actuate it.

ACC
Adaptive cruise control. Keeps a set speed and a safe gap to the CIPV.
LKA
Lane keeping assist. Steers back toward the lane centre from the detected lanes.
FCW
Forward collision warning. Warns when the time to collision with the CIPV gets too short.

FCP Studio

A viewer for MCAP recordings, made for FCP. Camera view, 3D scene, bird’s-eye view, timeline and plots in one window, so you can see what the stack saw and why it decided.

FCP Studio layout: the camera view with lanes and a highlighted vehicle, a 3D scene, a bird’s-eye view, plots and a timeline under them.
Layout of FCP Studio, drawn for this page.

Inside the stack

  1. Fisheye camera

    One 120° front camera. Calibration comes from the fisheye camera model.

  2. Multi-task network

    One network with a DINOv3 ViT-S backbone, trained on public datasets and running on TensorRT.

  3. Tracking and distance

    A camera-only pipeline with tracking and distance fusion.

  4. Driving functions

    ACC, LKA and FCW on top of the perception output, open loop.

  5. Recording and review

    Everything goes to MCAP and opens in FCP Studio.

How it is kept honest

  • A modular architecture.
  • A fault-injection suite that tests robustness.
  • A benchmark suite.
  • An issue tracker that links every issue to its fix.

Where it stands

Works today

Version 0.2 runs on my own recordings: motorway lanes, vehicles with CIPV and TTC, lights and signs of interest, and the three functions in open loop.

Needs work

Distance at long range, rare scenarios and night driving.

Next

Fine-tuning on real-world fisheye data. The source code is not public yet.

Build it with me

If you work on ADAS or computer vision, you can help with ideas, datasets, evaluation or code. Send me a message and tell me what interests you.

Contact on LinkedIn