Call LossLayer::LayerSetUp
in SmoothL1LossLayer
.
#8
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.
If
SmoothL1LossLayer
doesn't have aloss_weight
explicitly set, then it currently defaults to 0:In particular, note the first line, in which the loss is 0 even though the output is nonzero.
This PR is a 1-line change that calls the parent
LayerSetUp
method, which does the work of setting the defaultloss_weight
to 1.(On a somewhat related note, in the py-faster-rcnn repository it seems to be the case that
loss_weight
is always explicitly set, so this bug was never an issue there.)