Conform to new torchvision API for specifying pretrained weights #1794
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.
Overview
In version 0.13, TorchVision introduced a new API for specifying pretrained weights and added a deprecation warning for the old API. This PR updates the instances of the use of the old API within Raster Vision to the new API.
This is entirely an internal change and does not affect the
ModelConfig
API, which still accepts thepretrained
field.Checklist
needs-backport
label if PR is bug fix that applies to previous minor releaseNotes
N/A
Testing Instructions