You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The constructors of all Segmentation model constructors. The implementation should be identical to what was done for the other models. See Expand usage logging to models #4735
All the Transforms. For those that have functional equivalent the call should be placed directly in their method. For those that don't have a functional equivalent (for example Compose), the call should be placed in the class constructor. The approach is identical to what was done for the Operators. See Add logging to torchvision ops #4799
To the public python IO methods at torchvision.io.image and torchvision.io.video and to the VideoReader class constructor. On the python side these are the following endpoints: 1, 2, 3. It might be also worth covering C++ endpoints that might be called directly (without Python) such as 4, 5, 6.
datumbox
changed the title
Add _log_api_usage_once() calls on Segmentation models and Transforms
Add _log_api_usage_once() calls on remaining endpoints
Nov 17, 2021
Uh oh!
There was an error while loading. Please reload this page.
🚀 The feature
Add
_log_api_usage_once()
calls to:torchvision.io.image
andtorchvision.io.video
and to theVideoReader
class constructor. On the python side these are the following endpoints: 1, 2, 3. It might be also worth covering C++ endpoints that might be called directly (without Python) such as 4, 5, 6.cc @vfdev-5 @pmeier
The text was updated successfully, but these errors were encountered: