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

"Infer Many Images" function does not work properly for Generic Inference #255

Closed
andredubbel opened this issue Sep 1, 2015 · 6 comments
Labels

Comments

@andredubbel
Copy link

After playing around a bit with the new generic inference functionality I found what seems to be a bug in with the "Infer Many Images"-function; all outputs are the same:

screenshot from 2015-09-01 15 51 55

The displayed filenames are correct, and when testing them one by using the "Infer One Image" button they output reasonable results. I'm running the latest version of master 8a3d791

@gheinrich
Copy link
Contributor

Hi @andredubbel can you try this patch: gheinrich@d26703a
Thanks!

@andredubbel
Copy link
Author

Thanks for the quick response @gheinrich!

It got better but there's still something weird going on:

screenshot from 2015-09-01 17 06 51

For some reason the first and third row are the exactly the same, and the same goes for the second and forth. After that each row seems to be unique.

If I apply the 4 first images one by one the the third and forth get the values seen in the image while the first and second get different values. In simpler words, from row 3 and onward the results seem to be correct.

@lukeyeager lukeyeager added the bug label Sep 1, 2015
@gheinrich
Copy link
Contributor

I don't see this on my test sample. Any chance you can double check? Thanks!

@descampsa
Copy link

I had a similar issue, the results of the first chunk of images is invalid because they are overwriten by the second chunk results.
Try this patch: descampsa@f4a636d

@lukeyeager
Copy link
Member

@gheinrich, your patch seems to solve the problem for me. Can you open a pull request with the fix?

@andredubbel, thanks for the bug report!

@lukeyeager
Copy link
Member

Closed in #261.

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

No branches or pull requests

4 participants