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

Does R-Drop need two models? #80

Open
zjh21 opened this issue Apr 5, 2023 · 1 comment
Open

Does R-Drop need two models? #80

zjh21 opened this issue Apr 5, 2023 · 1 comment

Comments

@zjh21
Copy link

zjh21 commented Apr 5, 2023

Thank you for your great work!
However, I do have a problem concerning train_regularized_dropout_2D.py, which is an implementation of R-Drop. From what I know about R-Drop, it constrains two sub-models, i.e., the same model with different dropouts, to output the same results. That is, we can just put data x through the same model twice. The two forward propagations have two different sub-networks due to the randomness of nn.DropOut().
In your code implementation, however, there are model1 and model2. I wonder if it is necessary.

@KzRinga
Copy link

KzRinga commented Jul 18, 2023

Hey,bro.I also want to know the answer to this question.In your implementation, what is the performance of using only one model.

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