Skip to content
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

Add flag skip_epoch_completed to Engine.terminate_epoch() #3312

Closed
bonassifabio opened this issue Dec 3, 2024 · 1 comment
Closed

Add flag skip_epoch_completed to Engine.terminate_epoch() #3312

bonassifabio opened this issue Dec 3, 2024 · 1 comment

Comments

@bonassifabio
Copy link
Contributor

bonassifabio commented Dec 3, 2024

🚀 Feature

It is proposed to add a flag skip_epoch_completed (which defaults to False) to the method Engine.terminate_epoch() to terminate the current epoch without firing Events.EPOCH_COMPLETED.

Motivation

Suppressing the firing of Events.EPOCH_COMPLETED might be desirable for example to avoid checkpointing, early stopping, validation, and calling the scheduler step at the end of a terminated epoch.

What's happening now

Right now, Events.EPOCH_COMPLETED is always fired after Events. TERMINATE_SINGLE_EPOCH.

What would happen after this change

By default, the behavior would be the same, leaving the user the possibility to prevent Events.EPOCH_COMPLETED from being fired.

Context

See issue #3308 and PR #3309

Copy link

github-actions bot commented Dec 3, 2024

Hey 👋, I've just created a thread for this issue on PyTorch-Ignite Discord where you can quickly talk to the community on the topic.

🤖 This comment was automatically posted by Discuss on Discord

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants