Fix loaded data order bug when resuming from epoch >= 1 #40691
ngazagna-qc
force pushed
from
b07715d3
to
750dd2a4
243 days ago
ngazagna-qc
force pushed
from
bca1af55
to
7582e243
239 days ago
ngazagna-qc
force pushed
from
7582e243
to
c2bf0205
239 days ago
ngazagna-qc
force pushed
from
df5523d7
to
7935b869
214 days ago
ngazagna-qc
force pushed
from
79c2fbc8
to
1c87d024
214 days ago
ngazagna-qc
force pushed
from
1c87d024
to
2eb6316f
210 days ago
ngazagna-qc
force pushed
from
2eb6316f
to
fd14b2a0
203 days ago
ngazagna-qc
force pushed
from
fd14b2a0
to
1adc7ba2
202 days ago
ngazagna-qc
force pushed
from
1adc7ba2
to
136dfc4a
186 days ago
ngazagna-qc
force pushed
from
136dfc4a
to
6b787edd
181 days ago
SunMarc
approved these changes
on 2025-12-02
fix resume from epoch >= 1
628dd48a
add test checking order of sampled data points
9029b993
add require_torch_non_multi_accelerator decorator to test method
58600acb
move the epoch setting of epoch_dataloader before iterating over it
fa179ab0
ngazagna-qc
force pushed
from
6b787edd
to
fa179ab0
174 days ago
make fixup
d949cf70
SunMarc
merged
629c0da4
into main 174 days ago
ngazagna-qc
deleted the pr-fix-data-order-resumed-epoch branch 174 days ago
Assignees
No one assigned
Login to write a write a comment.
Login via GitHub