question-mark
Stuck on an issue?

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.

[Feature Request] Parameter scheduling

See original GitHub issue

Providing an abstraction to adjust optimizer parameters during training seems like it might be useful - techniques like SGDR seem applicable to many types of models.

The torch.optim.lr_scheduler module in PyTorch core implements some useful schedulers, but (a) can only adjust the LR, and (b) only adjusts it per-epoch.

On the other hand, the Engine event API seems like a really natural way to adjust parameter values, since handlers that manipulate them could be added for either ITERATION_* or EPOCH_* events, and modifying multiple parameters at once (e.g. LR and momentum) would be straightforward too.

I wrote a short IPython notebook as a prototype of one way it could look to do this with the event API in a general way (plots are at the very bottom). I left most of the actual scheduler code in separate files for now to try and see if the idea is even worth it first. Would this be useful?

Issue Analytics

  • State:closed
  • Created 5 years ago
  • Reactions:1
  • Comments:32 (17 by maintainers)

github_iconTop GitHub Comments

1reaction
alykhantejanicommented, May 25, 2018

I think contrib makes sense, would be nice to have community addition (maintained by the community). But I think we should strive to keep the core ignite lib lean

1reaction
sean-adlercommented, May 22, 2018

@sean-adler sorry for the delay on this. Do we think this might be a better change for the LRScheduler in Pytorch itself?

No problem! I’ve been super busy as well for the past couple of weeks. I’m not opposed to opening a PR there, it’s up to you whether it would be a better match in that repo or in ignite. My perspective is that it’s a lot easier to set up these schedules using the event/callback API in ignite, but maybe there is value in moving it to core.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Feature request: multiple schedules for different parameter ...
This creates the environment parameter. I want to create two scheduled searches: one each for "test" and "prod". This would allow me to...
Read more >
Feature Request: Run now option on scheduled jobs
While it is possible to run “start jobs” from jobs section but it can be time consuming if there are multiple and parameters...
Read more >
Using SCHEDULE Parameter - a Few Examples
Scheduling is a feature available to run Reports automatically at a specified time and with a given frequency. Reports can be scheduled on...
Read more >
How do I specify query parameters for a scheduled query in ...
A scheduled query is setup to run periodically in the background, and it's triggers automatically. Hence as it's automatically scheduled, there ...
Read more >
[Feature Request] Set Anki custom scheduling per deck/option
Recently, I implemented an Anki custom scheduling and released it on GitHub. Some users found that the parameters of the scheduler, ...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found