Skip to content
New issue

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

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

Already on GitHub? Sign in to your account

Running fixmatch with RandAugment #19

Closed
dsuess opened this issue Mar 23, 2020 · 2 comments
Closed

Running fixmatch with RandAugment #19

dsuess opened this issue Mar 23, 2020 · 2 comments

Comments

@dsuess
Copy link

dsuess commented Mar 23, 2020

First of all, thanks for publishing the code for this paper -- it makes reproducing your work much easier.

I am trying to run fixmatch with RandAugment+Cutout instead of CTAugment (as it's much easier to implement in practice and the performance is often comparable). I've read #4 which states that fixmatch always uses CTAugment (additionally to what's provided in the --augment flag). So if I understand this correctly, --augment d.d.rac does not achieve what I want since CTAugment is always added on top? I suspect that's what's happening since I still see the CTAugment-weight printout when running training with that argument.

If that's the case, is there an easy way to disable CTAugment?

@carlini
Copy link
Collaborator

carlini commented Mar 24, 2020

You can see the ablations for lots of examples on how we do these experiments, e.g.,

https://github.com/google-research/fixmatch/blob/master/ablation/ab_fixmatch_onlycutout.py

@dsuess
Copy link
Author

dsuess commented Mar 24, 2020

Thanks, that folder contains everything I need

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

No branches or pull requests

2 participants