[BC-Breaking] TuSimple max lane number testing constrain bug fix #13
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This bug fix brings 0.1~0.4% F1 score increase on all uploaded models (on one extreme case ERFNet Baseline, 0.8%).
The original code did not mask out the lane prediction with lowest existence probability, but it accidentally masked out the first lane when the network predicted 6 lanes (TuSimple has a maximal number of 5 lanes).
This change is only applied to testing scripts, so any previous downloaded/trained weights still can be used, they just need re-testing. Also this change is too small to have much of a effect on hyper-parameter validation, so hyper-parameters will remain unchanged as well.
However, we are providing new best model weights for download (since the previous ones now are not the best among the 3 runs after re-testing), these models are:
Be sure to re-download the new best models (filename ends with
_20210424.pt
).