You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@yunchu , I investigated this issue and found some weird behavior in a test environment. This issue happens because of in train_cls_incr we change datasets, but the number of iterations is much lower than expected, so, runner.current_iter < runner,max_iters, and there are some issues in the scheduler emerge.
Can it be some possible shift in two testing environments (otx_train and train_cls_incr) leading to broken information about proper dataset size/number of epochs?
BTW,
This problem is not reproducible outside of tests. I tried the class incremental approach with the same data and everything is fine. The number of iterations is what it should be without any errors.
@kprokofi I guess you can check the regression test on the repo. I've just checked that was happened on 'develop' branch as well.
AFAIK, the current regression test run only 10 epoch for each training. do you think it could make any issues?
Describe the bug
tested on branch
releases/1.5.0
failures on regression test for semantic segmentation
Steps to Reproduce
Environment:
The text was updated successfully, but these errors were encountered: