-
Notifications
You must be signed in to change notification settings - Fork 28
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
How to Debug with pycharm #16
Comments
Hey, |
Thank you for your reply. Secondly, I noticed that you used compute FB, using the features and gt of query set, which means that the FB of each segmentation is known, and the network is used to process new images in the end. For features without gt, the segmentation effect will be greatly reduced. How do you solve this problem? |
Hi, the FB segmentation is not known in advance in our main method (otherwise there would be no point in developing a method at all). Please have a look at issue #10 , and particularly my answer #10 (comment) which should answer your question (if I understood it correctly). If it's still not clear, do not hesitate to ask me further clarification. |
Thank you for your reply. I noticed that in the part of RePRI, you used gt_q of query set to get the high-level feature map of the downsampling , and then passed the valid pixels which you said that is not 255 in get_entropies to get d_KL, cond_entropies and marginal, which are all related to valid_pixels , can you tell me why you use gt_q for this part? |
Please reference precise lines of the code so that I can help you better (copy the permalink of the line you're referring to in your comment). I'm really not sure I understand the question right now. As you said, there is no gt_q involved in computing the loss functions, only for the valid pixels. gt_q is only used for the following purposes:
|
Hi, very excellent work. Thanks for the code, it's very helpful and instructive!I want to study your code structure, but I don't know how to use pycharm to debug your code.
The text was updated successfully, but these errors were encountered: