ignite: This is breaking my IterableDataset use case: is it a bug or intended?
Looking at the following line of code:
https://github.com/pytorch/ignite/blob/523798c13a9465f4c95565cb54ae3c5aa0786ac6/ignite/engine/engine.py#L742
It breaks out of the loop without resetting the dataloader (means without calling self.set_data(self.state.dataloader)
), it’s breaking all my use cases where my own implementation of dataloader only raises StopIteration
once. Is this a bug or intended?
About this issue
- Original URL
- State: closed
- Created 4 years ago
- Comments: 15
I would like to but there are some proprietary code I cannot share. I’ll look into it at my end. Also, let me know if you find something! Thanks a lot for helping.
@vfdev-5 I haven’t had time to work on this. Feel free to close the issue for now.
@snie2012 here is a working code on DDP with “gloo” backend on 4 procs, 1 node: