-
Notifications
You must be signed in to change notification settings - Fork 175
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
Did you use random augment as strong aug as claimed in the paper? #4
Comments
Hello, in fixmatch CTAugment is done in addition to |
So for fixmatch, CTAugment is only applied to stronly augmented unlabeled samples(after the default augments), while labeled and weakly augmented unlabeled samples only employ default augments(flip and random crop), is that true ? |
Hi, |
The code you pointed to is used for fully supervised augmentation, for FixMatch it is overloaded Sorry, the code is a bit complicated. Thanks for asking the question. |
Thanks for your reply~~ |
No it is applied to labeled images used as probes. I prefer not to use the word evaluation since it could be confused with the testing phase / model evaluation. CTAugment takes a labeled image and strongly augments it. We call this a probe. We uses the model prediction on it to adjust the augmentation internal parameters. |
Thanks very much! |
So there will be four sorts of training samples in one iter, the weakly augmented labeled samples and the strongly augmented unlabeled samples will be used to train the model(compute loss). The strongly augmented labeled samples will be used to update CTAugment weights, and the weakly augmented unlabled samples will be used to generated the psuedo labels for computing the unlabeled loss. Am I correct on this? |
Yes |
Hi,
Thanks for bring the work to us. I am going through the code you released, and I noticed that the augmentations are assigned with an argment of
augment
whose default value isd.d.d
. Does it mean that in this repo you use default aug methods for both strong and weak augments for the unlabeled samples ?The text was updated successfully, but these errors were encountered: