fooscodes rendering size wonky

[rsalmond]

@dschnabel you're right, I tried rendering one of those svg's into a PDF and the PDF came out slightly larger. Weird. Based on the camera resolution maybe we can work out a maximum usable camera distance for a given fooscode size?

[dschnabel]

What do you mean by maximum usable camera distance for a given fooscode size?

[rsalmond]

Like depending on how large you print the the image how far away from a camera with 720p resolution will it still actually detect the ID #?

[dschnabel]

In theory the camera can detect different sizes of fooscodes. But the detection itself is a tricky process and there are many factors that have to play together nicely. Also performance is an issue since we don't want to wait 10 seconds for detecting all four cards. So I highly tweaked the program to have the best detection rate for the current size and also finish within 1 second.

If we allowed different sizes either the detection rate would go down or it would take too long to calculate.

[rsalmond]

Cool so based on current tweaks we should be able to provide an optimal print size and focal distance from the camera? I want to figure this out to allow printing of new codes from within the page.

[dschnabel]

Yes, the optimal print size is the one used in foosCodes.pdf. If you find a way to generate a fooscode that has exactly the size when printed then all should be good.