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
{{ message }}
This repository has been archived by the owner on Mar 15, 2024. It is now read-only.
In the issue Why should we set different seed per gpu with DDP, the explanation is that the different seed contributes to the not same data-augmentations on different GPUs. However, I have another question. The different seeds on different GPUs also make different model weight initialization. I dont find the synchronous code like torch.distributed.boardcast(). Is the different initilization helpful in distributed training process? Or, would you provide the synchronous code on model initilization?
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
deit/main.py
Line 182 in 35cd455
In the issue Why should we set different seed per gpu with DDP, the explanation is that the different seed contributes to the not same data-augmentations on different GPUs. However, I have another question. The different seeds on different GPUs also make different model weight initialization. I dont find the synchronous code like
torch.distributed.boardcast()
. Is the different initilization helpful in distributed training process? Or, would you provide the synchronous code on model initilization?The text was updated successfully, but these errors were encountered: