-
Notifications
You must be signed in to change notification settings - Fork 131
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
KeyError: 'gqa_accuracy_answer_total_unscaled' #47
Comments
@TopCoder2K Did you manage to find a solution to this? |
Not sure why this is hardcoded. When doing QA, the list of keys (metrics) available when using the CLEVR dataset is as shown below. Changing 'gqa_accuracy_answer_total_unscaled' to 'clevr_accuracy_answer_total_unscaled' in the code should fix the problem. dict_keys([
'clevr_loss',
'clevr_loss_ce',
'clevr_loss_bbox',
'clevr_loss_giou',
'clevr_loss_contrastive_align',
'clevr_loss_ce_0',
'clevr_loss_bbox_0',
'clevr_loss_giou_0',
'clevr_loss_contrastive_align_0',
'clevr_loss_ce_1',
'clevr_loss_bbox_1',
'clevr_loss_giou_1',
'clevr_loss_contrastive_align_1',
'clevr_loss_ce_2',
'clevr_loss_bbox_2',
'clevr_loss_giou_2',
'clevr_loss_contrastive_align_2',
'clevr_loss_ce_3',
'clevr_loss_bbox_3',
'clevr_loss_giou_3',
'clevr_loss_contrastive_align_3',
'clevr_loss_ce_4',
'clevr_loss_bbox_4',
'clevr_loss_giou_4',
'clevr_loss_contrastive_align_4',
'clevr_loss_answer_type',
'clevr_loss_answer_binary',
'clevr_loss_answer_reg',
'clevr_loss_answer_attr',
'clevr_loss_ce_unscaled',
'clevr_loss_bbox_unscaled',
'clevr_loss_giou_unscaled',
'clevr_cardinality_error_unscaled',
'clevr_loss_contrastive_align_unscaled',
'clevr_loss_ce_0_unscaled',
'clevr_loss_bbox_0_unscaled',
'clevr_loss_giou_0_unscaled',
'clevr_cardinality_error_0_unscaled',
'clevr_loss_contrastive_align_0_unscaled',
'clevr_loss_ce_1_unscaled',
'clevr_loss_bbox_1_unscaled',
'clevr_loss_giou_1_unscaled',
'clevr_cardinality_error_1_unscaled',
'clevr_loss_contrastive_align_1_unscaled',
'clevr_loss_ce_2_unscaled',
'clevr_loss_bbox_2_unscaled',
'clevr_loss_giou_2_unscaled',
'clevr_cardinality_error_2_unscaled',
'clevr_loss_contrastive_align_2_unscaled',
'clevr_loss_ce_3_unscaled',
'clevr_loss_bbox_3_unscaled',
'clevr_loss_giou_3_unscaled',
'clevr_cardinality_error_3_unscaled',
'clevr_loss_contrastive_align_3_unscaled',
'clevr_loss_ce_4_unscaled',
'clevr_loss_bbox_4_unscaled',
'clevr_loss_giou_4_unscaled',
'clevr_cardinality_error_4_unscaled',
'clevr_loss_contrastive_align_4_unscaled',
'clevr_loss_answer_type_unscaled',
'clevr_accuracy_answer_type_unscaled',
'clevr_loss_answer_binary_unscaled',
'clevr_accuracy_answer_binary_unscaled',
'clevr_loss_answer_reg_unscaled',
'clevr_accuracy_answer_reg_unscaled',
'clevr_loss_answer_attr_unscaled',
'clevr_accuracy_answer_attr_unscaled',
'clevr_accuracy_answer_total_unscaled',
'clevr_coco_eval_bbox'
]) |
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
This mistake is really strange... I follow the readme for training MDETR on CLEVR.
Firstly, I've ran the following command:
The only difference with the one in the readme is that I've used
run_with_submitit.py
and added--nodes 1 --ngpus 1
parameters.The training has gone well and the job has finished successfully. Then I've ran
And after the first epoch and testing I've gotten the following in
28574_0_log.err
file (warnings were deleted):Why the loss is missing?((
Also, here is the end of
28574_0_log.out
file:The text was updated successfully, but these errors were encountered: