Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Can you update the configuration of dytox++ for imagenet100 and imagenet1000? #23

Open
wwx1474446236 opened this issue Jul 23, 2023 · 1 comment

Comments

@wwx1474446236
Copy link

wwx1474446236 commented Jul 23, 2023

Hi sir!
There is no dytox++ configuration for imagenet100 and imagenet1000 in your code,
I appended the following configuration to imagenet_dytox_plus.yaml to pretend that this is imagenet_dytox_plusplus.yaml:
# SAM sam_rho: 3.0 sam_adaptive: true # ASAM sam_skip_first: true sam_mode: [tr]

and I ran the following command (using 2GPUs):

bash train.sh 0,1 --options options/data/imagenet100_10-10.yaml options/data/imagenet100_order1.yaml options/model/imagenet_dytox_plus.yaml --name dytox --data-path MY_PATH_TO_DATASET --output-basedir PATH_TO_SAVE_CHECKPOINTS --memory-size 2000

and I got the final result is :
"acc": 70.64, "avg_acc": 78.93
compare with "acc": 72.46, "avg_acc": 80.76 in your Appendix Table 10, my result is much lower.

Can you update the configuration of dytox++ for imagenet100 and imagenet1000?

@arthurdouillard
Copy link
Owner

Your config is right, the problem came from a bug, see https://github.com/arthurdouillard/dytox/blob/main/erratum_distributed.md

You can see updated results for dytox and dytox+ in table 17 of the last version of my paper.
Unfortunatly i've never re-run dytox++ because it's slower with SAM.

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants