pytorch/ignite
GitHub で見る`Timer`'s misleading behaviour when epoch completion time calculated
Open
#2,157 opened on 2021年8月11日
HacktoberfestPyDataGlobalenhancementhelp wanted
Repository metrics
- Stars
- (4,313 stars)
- PR merge metrics
- (平均マージ 18d 23h) (30d で 19 merged PRs)
説明
When I tried calculating the time taken to complete a single epoch via Timer, the handlers attached to trainer before Timer were executed first, and thus their time also got recorded by the Timer too for a single epoch. Therefore the true time taken for epoch completion, provided by trainer.state.times, is less than what Timer calculated. This can be misleading. More clarification on how this actually works in the docs would be appreciated. Or the Timer's functionality can be enhanced to step before all other handlers attached to an event could also be helpful. Notebook to quickly verify this here.