-
Notifications
You must be signed in to change notification settings - Fork 12
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
Question regarding evaluation #12
Comments
The category id definition is the SAME. The name is changed to remind me that the category id starts from 0. |
Thank you very much. Yes i assumed ots the same was just not quire sure why the name was adapted but makes sense! ok cause couldn't find it when checking for gt_handle .. in the git search https://github.com/lolrudy/GPV_Pose/search?q=gt_handle_visibility |
So for eval a different dataset is used compared to training,
how are the values for the dict obtained?
eval:
train:
RGB --> same
depth --> same
depth_normalize --> same
obj_id --> eval ['cat_id_0base'], train data['cat_id']
camK --> same
gt_mask --> same
gt_R --> not used in eval
gt_t --> not used in eval
gt_s --> not used in eval
mean_shape --> not used in eval
gt_2D --> same
sym --> same
def_mask --> eval def_mask=data['roi_mask'], train def_mask=data['roi_mask_deform']
required for eval:
pred_RT --> obtained from line 84, generate_RT([p_green_R_vec, p_red_R_vec], [f_green_R, f_red_R], p_T, mode='vec', sym=sym)
information not present in GPV Pose --> how to obtain gt_handle_visibility
in mentian/object-deformnet --> https://github.com/mentian/object-deformnet/search?q=gt_handle_visibility
gt_handle_visibility = nocs['gt_handle_visibility']
so my question is why is the category id definition different? and for an own dataset how to obtain the value gt_handle_visibility
The text was updated successfully, but these errors were encountered: