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
CUlane: Half the input-size #15
Comments
We already downsample the input image by a factor of two (see here) so that input image size is If you want to reduce the image size further, you will also have have to change a few other settings in the dataloader, specifically, here, here, here, and here. For example, if you wanted to reduce the input image size by a factor of 4 instead of the default 2, you should make the following changes in the lines above:
That being said, I would highly suggest you use one of the lighter models for training (for example ENet) instead of reducing the image size further as I anticipate this to affect the performance significantly. |
Sorry, I should've closed this issue as it is not relevant for me anymore. I have tried downsampling the image more and as you have predicted, the performance decreases significantly. |
You don't need keep the ratio of image. Resolution like 512x512 may be a balance between speed and accuracy. |
Hi!
To reduce training time as I only have access to a 1080 Ti, I have reduced the input image size using the resize function you provided in the Dataloader from (1664, 576) to (832, 256). During inference, it always returns that the "Lane too small" as the fitted spline has only less than 10 values. Now, I wonder, what
h_samples = (589, 240)
inget_lanes_culane
really represents and how you got to this value?I have set
h_samples = (589 / 2, 240 / 2)
to see what happens and now, I get splines with values around 15-25, so I'll probably set the threshold to 20 to see how the accuracy will be.Or would you just scale the input back to its original, i.e. (832 * 2, 256 * 2) during inference and keep everything as it is?
Thanks in advance!
The text was updated successfully, but these errors were encountered: