-
Notifications
You must be signed in to change notification settings - Fork 45
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
what is the meaning of path_num? #54
Comments
The Was this clear enough? You mentioned a fix for #52, could you give me some hints on this as well? |
Thanks for your reply. I know how it works. But I cannot understand why use two(four) path_num, if I use one, What impact will it have? Waiting for your reply sinserly. |
I'm not sure, that I can correctly explain how it works, but regarding the "why" have a look at Table 7 in the original paper and at the paragraph "Shared Subnetworks v.s. Independent Subnetworks". Splitting up the network into multiple paths seems to enlargen the representation capacity and therefore improve the accuracy of the model. |
thanks for your reply. In table 7 ,there is three options. 1.Single Path Baseline 2.Shared 3.Independent, the miu gradually raising. |
Hi, thanks for your interest. The key idea is to separate and distribute a large segmentation model's computation into multiple independent lightweight subnetworks, which can be assigned to different frames so as to reduce the latency.
|
Thanks for your reply. Through your explanation I understand the meaning of table 7. But as for reply 2, I think which path will the data go into depends on epoch and pah_num. So I always believe that this bath_size go into path 1 , then the next bath_size go into path 2 , and next go into path1, and repeat it continuously based on this. so I think this training method will train two different parameters for KDloss and parameters of "self.head" functions. |
I'm sorry, there are still some questions I need to ask you. |
I cannot understand the meaning of the setting of the path_num。
for multi-GPU?
waiting for your reply senserly.
The text was updated successfully, but these errors were encountered: