Missing files, weights, and broken paths referenced by README/code

[NBaLogn]

Summary

A second-pass audit across all three branches (main, origin/development, origin/parking_service) found additional missing weights, runtime-required configs, and broken doc references beyond the initial list. This issue tracks them all.

Could you please commit the missing artifacts, fix the broken paths, or update the README accordingly?

---

1. Files/directories missing from ALL branches

Path	Referenced in (README line / file)	Notes
docker.sh	README 92, 634–638	Helper script positioned as the primary Docker entrypoint
quickstart.sh	README 115	One-shot setup script in install instructions
data/config/	README 204	Documented as stream-config dir (streams.txt)
data/scripts/ (and download_roboflow.py, crop.py, record_rtsp_streams.py, yt_downloader.py)	README 209, 542–546, 580–583	Roboflow dataset-download flow depends on this. data/download_roboflow.py exists on parking_service and could be ported.
webapp/utils/	README 231	Listed in project tree
weights/pretrained/	README 213–214, 487	Pretrained YOLO base models dir
scripts/train_yolo.sh	README, TRAINING_GUIDE	Only scripts/train_yolo.example.sh is committed. README/guide both instruct ./scripts/train_yolo.sh.
.env.example	implied by docker-compose env usage	No template anywhere despite ALPR_DEVICE, VEHICLE_WEIGHT, PLATE_WEIGHT, ROBOFLOW_API_KEY, etc. being read.
webapp/rtsp_url.json	webapp/backend/main.py (CAMERA_CONFIG_PATH)	Runtime impact: code does json.load() on hardcoded path with no fallback — camera-config endpoint will crash if absent. A starter {"streams": []} should ship.

2. Missing weight files

Weight reference	Referenced in	main	development	parking_service	Notes
weights/vehicle/vehicle_yolo12s_640.pt	docker-compose.dev.yml:14, README 247, 480	❌	❌	❌	Listed as recommended model but absent. Nearest available: vehicle_yolov9s_640_30oct2025.pt.
weights/plate/plate_yolo11n_640_2025.pt	README 440 (training example)	❌	❌	✅ (.pt, flat path)	.onnx exists on main/dev, but the .pt only on parking_service.
weights/vehicle/vehicle_yolo11m_640_18sep2025.pt	README 481 (model-zoo listing)	❌	❌	❌	Docs-only reference.
weights/rec_ppocr_0.948/	utils/ocr.py:123	❌	❌	❌	Custom PaddleOCR recognition model directory. No substitute; user must supply or retrain.

3. Broken hardcoded paths

File	Line	Problem
tracking/configs/deep_sort.yaml	2	Hardcoded tracking/deep_sort/deep/checkpoint/ckpt.t7 — the actual file lives at weights/tracking/deepsort/ckpt.t7. Path needs updating or a symlink/copy.
webapp/backend/main.py (originally)	46	Default vehicle weight was vehicle_yolo11s_640_30oct2025.pt which does not exist on main. Locally patched to vehicle_yolov9s_640_30oct2025.pt to get the webapp running.

4. Missing from main and development (present on parking_service)

Path	Notes
MODEL_ZOO.md	Auto-generated by scripts/generate_model_zoo.py. README references it without noting it must be generated first. Consider regenerating + committing, or documenting the build step.
data/download_roboflow.py	Useful dataset utility; not ported to main / development.

5. Expected absences (not requesting action, listed for completeness)

• logs/, results/, runs/, recordings/ — runtime-generated.
• samples/, data/<dataset>/data.yaml (LP-11k, Peru_License_Plate, license-plates, vehicles, etc.) — user-provided datasets.
• .env — gitignored.

---

Requested action

Any combination of:

1. Commit the missing files/directories (especially webapp/rtsp_url.json, scripts/train_yolo.sh, .env.example, and MODEL_ZOO.md).
2. Port data/download_roboflow.py and missing weights from parking_service to main / development.
3. Fix the broken hardcoded paths (tracking/configs/deep_sort.yaml, default weight in webapp/backend/main.py).
4. Update README to remove references to artifacts that are intentionally out-of-tree (and explain how users should obtain or generate them).

Happy to open a PR for the README cleanup portion — just let me know which paths are deliberately not shipped.

---

Audit performed on commit 3675a1c (main) across all three remote branches. Read-only inspection — no working-tree changes were pushed.