Skip to content

Add _log_api_usage_once() calls on remaining endpoints #4955

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

Closed
3 tasks done
datumbox opened this issue Nov 17, 2021 · 0 comments · Fixed by #4956, #5038 or #5007
Closed
3 tasks done

Add _log_api_usage_once() calls on remaining endpoints #4955

datumbox opened this issue Nov 17, 2021 · 0 comments · Fixed by #4956, #5038 or #5007

Comments

@datumbox
Copy link
Contributor

datumbox commented Nov 17, 2021

🚀 The feature

Add _log_api_usage_once() calls to:

  • 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.

cc @vfdev-5 @pmeier

@datumbox 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
@datumbox datumbox reopened this Nov 22, 2021
This was referenced Dec 1, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
1 participant