Closed ArseniuML closed 11 months ago
Yes, you can directly change the pc_range to this one. However, since FSDv2 is fully sparse, if there are no points beyond 100m in your dataset, I don't think it will be faster after shrinking the range. Anyway, you could have a try. If you have any problems after the modification, feel free to post new replies or issues.
Perception range shrinking seems not to speedup the model. Are there other settings in config I can play with in order to speedup FSDv2?
The most straightforward way is to reduce the size of backbone, and the mixer. For example in this config, we adopt a very lightweight backbone, you could try it on FSDv2.
FSDv2 with pre-trained Argoverse2 weights seems to get good metrics on our dataset, but it would be great to speedup the detector by factor ~2-3. However, our Lidar has perception range +-100 m. Do I can speedup FSDv2 via perception range shrinking? Would it be sufficient to set perception range like this: