-
Notifications
You must be signed in to change notification settings - Fork 102
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Incremental/additional training of FSDv2 #188
Comments
It depends on the domain gap between your data and the pre-training data. I personally believe tuning all parameters is better. |
How do I can estimate this domain gap? We have 80-beam Robosense RS Ruby Lite LIDAR, Argo2 is created with two VLP-32C LIDARs. Argo2 paper says that two VLP-32C effectively create 64 beams, but it's not fully clear for me, how are clouds from these tho LIDARs being merged and what the resulting beam distribution is... |
It is hard to estimate the domain gap without experiments. My experience is only using xyz as input without intensity is good for narrowing the domain gap. Different sensors have quite different intensity values. |
Unfortunately, I am very limited in my ability to conduct experiments.
I guess the best possibility to train a detector in these conditions is to freeze some pre-trained layers and apply additional training. Do you can assume, which layers I have to freeze? |
Is there a way to apply additional training on our data to pre-trained checkpoint (say on Argoverse2)?
If there is a simple CNN, I can fix conv layers weights and re-train fully-connected layers (on even the latest conv layers). Do I can apply similar technique to FSDv2?
The text was updated successfully, but these errors were encountered: