-
Notifications
You must be signed in to change notification settings - Fork 16
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
Batchsize #4
Comments
Indeed yes, you can manage this issue in the code level. By using bigger batch, the code should be modified to distinguish different samples in the batch and avoid mixing them up in the CM block. As long as the samples are distinguished properly, they can then form a new batch after the CM block and compute loss with a batch of GT. To realize this, certain modification should be made to the CM block. |
Since RGB images and Depth maps are first loaded as batch data and then connected in the batch before entering the network, they can be split in half in the batch dimension to distinguish different samples. The ``forward'' function of the CM module (the CMLayer in JL_DCF.py) can be modified as follows:
In this way, you can enable bigger batch. |
Hello, I was wondering why it's not possible to have bigger batch. Like if you just do two forward propagation in the JL phase and combine the result in the CM block ?
The text was updated successfully, but these errors were encountered: