Add README.md
Browse files
README.md
ADDED
|
@@ -0,0 +1,70 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
---
|
| 2 |
+
license: other
|
| 3 |
+
tags:
|
| 4 |
+
- heal
|
| 5 |
+
- horizon
|
| 6 |
+
- bev
|
| 7 |
+
- lane-detection
|
| 8 |
+
---
|
| 9 |
+
|
| 10 |
+
# MapTR+HENet (BevFormer)
|
| 11 |
+
|
| 12 |
+
MapTR uses HENet as the camera backbone to extract multi-view features, transforms them to BEV features via BevFormer's single-frame ViewTransformer and BEV Encoder, then feeds BEV features to the MapTR decoder with fixed-point polyline queries (`fixed_ptsnum_per_pred_line=20`) to predict vectorized map elements (divider/ped_crossing/boundary). This task has `use_lidar_gt=False`; map GT is generated online.
|
| 13 |
+
|
| 14 |
+
---
|
| 15 |
+
|
| 16 |
+
## Deployment Metrics
|
| 17 |
+
|
| 18 |
+
### Model Parameters
|
| 19 |
+
|
| 20 |
+
| Model | Model Input | Backbone | Neck | Model Output |
|
| 21 |
+
|---|---|---|---|---|
|
| 22 |
+
| MapTR | 6-camera multi-view images `(B,6,3,480,800)` | HENet-tiny | FPN | vectorized map `(B,L,P,2)` |
|
| 23 |
+
|
| 24 |
+
### Accuracy Metrics
|
| 25 |
+
|
| 26 |
+
| March | Metric | float | calibration | qat | hbm |
|
| 27 |
+
| --- | --- | --- | --- | --- | --- |
|
| 28 |
+
| J6M | chamfer mAP (MAP) | 0.6626 | 0.6588 | — | 0.6315 |
|
| 29 |
+
|
| 30 |
+
> Data tested with `march = March.NASH_M` (J6M); this task has no QAT stage (`—` in the qat column).
|
| 31 |
+
>
|
| 32 |
+
> HEAL versions: heal 0.0.2 / hbdk4-compiler 4.11.11 / horizon_plugin_pytorch 3.3.10.
|
| 33 |
+
|
| 34 |
+
### Performance Metrics
|
| 35 |
+
|
| 36 |
+
> **Performance test methodology**: FPS is measured with 8 threads on a single core; Latency is measured with single core, single thread; Memory is peak DDR usage.
|
| 37 |
+
|
| 38 |
+
| March | latency (ms) | fps | Memory Usage |
|
| 39 |
+
|---|---|---|---|
|
| 40 |
+
| J6M | 9.30 | 111.22 | 88.40 |
|
| 41 |
+
| J6P | 6.16 | 663.68 | 83.30 |
|
| 42 |
+
| J6B | 33.28 | 30.85 | 80.00 |
|
| 43 |
+
|
| 44 |
+
---
|
| 45 |
+
|
| 46 |
+
## Model Overview
|
| 47 |
+
|
| 48 |
+
### Core Design
|
| 49 |
+
|
| 50 |
+
MapTR uses HENet as the camera backbone to extract multi-view features, transforms them to BEV features via BevFormer's single-frame ViewTransformer and BEV Encoder, then feeds BEV features to the MapTR decoder with fixed-point polyline queries (`fixed_ptsnum_per_pred_line=20`) to predict vectorized map elements (divider/ped_crossing/boundary). This task has `use_lidar_gt=False`; map GT is generated online.
|
| 51 |
+
|
| 52 |
+
- **Task type**: Online Vectorized Map Construction.
|
| 53 |
+
- **backbone**: HENet-tiny (pretrained), extracts multi-view camera features.
|
| 54 |
+
- **neck**: FPN.
|
| 55 |
+
- **view transformation**: `SingleFrameBevFormerViewTransformer` + `SingleFrameBEVFormerEncoder` (`queue_length=1`/`test_queue_length=1`).
|
| 56 |
+
- **map elements**: `map_classes=[divider, ped_crossing, boundary]`, `fixed_ptsnum_per_gt_line=20`.
|
| 57 |
+
- **BEV range**: `use_lidar_gt=False` else branch, `point_cloud_range=[-30.0,-15.0,-10.0,30.0,15.0,10.0]`, `bev_h_=50`, `bev_w_=100` (bev 50×100).
|
| 58 |
+
- **Model input**: 6-camera single-frame images `(B,6,3,480,800)` .
|
| 59 |
+
- **Model output**: 3 classes of vectorized map elements (divider/ped_crossing/boundary), 20 points per line.
|
| 60 |
+
|
| 61 |
+
### Official Repo and Paper
|
| 62 |
+
|
| 63 |
+
Official repo: https://github.com/hustvl/MapTR
|
| 64 |
+
Paper: https://arxiv.org/abs/2208.14437
|
| 65 |
+
|
| 66 |
+
Note: The camera backbone HENet is developed in HEAL; the official repo uses a different backbone.
|
| 67 |
+
|
| 68 |
+
### Reference
|
| 69 |
+
|
| 70 |
+
For more J6 chip deployment details, see https://developer.horizon.auto/blog/10142
|