Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Move param handlers to core part
See original GitHub issue🚀 Feature
As discussed in https://github.com/Project-MONAI/MONAI/pull/1949#issuecomment-815283287 moving https://github.com/pytorch/ignite/blob/master/ignite/contrib/handlers/param_scheduler.py to the core part: https://github.com/pytorch/ignite/tree/master/ignite/handlers could be great addition for users, apps and toolkits which do not use contrib module (e.g. MONAI).
While moving the code, we would like to ensure BC-compatibilty for at least one future release. Once the code has been moved we can put deprecation message for classes and methods inside contrib module. contrib/handlers/param_scheduler.py will be removed in v0.6.0.
A follow-up feature to this feature request could be enlarging the scope of ParamScheduler to scheduling any parameter (e.g. hyperparameters) like it is done in MONAI: https://github.com/Project-MONAI/MONAI/pull/1949
Issue Analytics
- State:
- Created 2 years ago
- Comments:8 (1 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
@vfdev-5 perfect, will aim to have it done by the end of the weekend.
@vfdev-5 thanks for ccing.
Just to make sure I get your right.
For now we will just move ParamScheduler out of contrib and add MONAI ParameterScheduler to Ignite?
In this issue we will not aim to combine the two into a better class because we want to maintain backwards compatibility between 0.5.1 and 0.5. Right?
Thanks!