Skip to content
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

Can you tell me what accuracy have you achieved? #26

Open
greathope opened this issue Dec 27, 2017 · 4 comments
Open

Can you tell me what accuracy have you achieved? #26

greathope opened this issue Dec 27, 2017 · 4 comments

Comments

@greathope
Copy link

with this command on vqa v1.0:
python train.py --vqa_trainsplit trainval --path_opt options/vqa/mutan_att_trainval.yaml

@Cadene
Copy link
Owner

Cadene commented Dec 27, 2017

@greathope As far as I remember, we got those results on the testset (with our old Torch7 code, but you should get the same results with this code in pytorch):

Overall Accuracy is: 64.77
Per Answer Type Accuracy is the following:
other : 54.47
number : 38.43
yes/no : 83.81

@greathope
Copy link
Author

@Cadene with trainval datasets? Actually I got 65.42...

@Cadene
Copy link
Owner

Cadene commented Jan 5, 2018

That's good news, isn't it?

It might be related to this little change in architecture: #18

What do you think? @greathope

@eustcPL
Copy link

eustcPL commented Mar 13, 2018

@Cadene how about: vqav1.0 python train.py --vqa_trainsplit trainval --path_opt options/vqa/mlb_att_trainval.yaml, what accuracy did you acheived?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants