<< return to Pixycam.com

OK in cooked, no good in home

Pixy Software
#1

Hi,

I’m having an issue where the tracking looks good in cooked mode - colors and color codes get tracked decently (not great) - but then when I go to home mode the tracking is really poor.

Any ideas?

Thanks.

#2

Try changing with Pixy parameters from setting

#3

Hello GB,
If your signatures are ‘noisy’, there can be some discrepancies between cooked and default mode, mostly because default mode is 2x the resolution of cooked mode.

You might try improving the accuracy of your signatures. This page has some good pointers:

http://cmucam.org/projects/cmucam5/wiki/Some_Tips_on_Generating_Color_Signatures_2

Edward

#4

Thanks Ed.
It seems that Jose posted (http://cmucam.org/boards/9/topics/7167) about having similar issues to mine (disparity between cooked and default modes). I am using color codes as well and having the same issues he brought up.

I have spent a lot of time trying to optimize the signatures but it has not helped much. I am using big pieces of color (poster boards 20" x 30") to make the signatures so they should be quite easy to detect. The signatures in cooked mode look good, but then get very “jumpy” in default.

Thanks.

#5

Hi GB

I won’t be able to test it properly until tonight, but I think the issue might be caused by the ‘CC multiplier’ setting in the Expert tab. I suspect that the Cooked view does not take it into account, while the Default view does. A quick check, changing the value from 4 to 1, did nothing in cooked view, but for default it made it almost impossible to detect the backlight CC pattern I had taught it.

EDIT: Added some screencaps of what I mean. Again, this is just a suspicion, but to me it looks like Cooked view is set with a 1.1-1.2ish CC multiplier. It’s hard to convey the behavior through a single screencap, but at that value both views seemed just a erratic.

#6

Thanks Jose.

Here are some screen captures that show good tracking in cooked, and only one of two of the objects tracked in default.

#7

Also, note that this only happens with color codes – when i do 4 separate objects, it works fine as seen in the screen shots below (i.e. good tracking in cooked and in default).

#8

Hi GB,
Please make sure you are running firmware version (2.0.17). Also, what version of PixyMon are you using? Assuming you are using the latest versions, these look like good cases that we can reproduce and investigate on our end.

Thanks,
Edward

#9

Hi Ed,

Yes, latest versions of the firmware and pixymon (2.0.17 firmware and 2.0.9 pixymon).

Thanks for the follow up.

#10

Hi GB,
We’ve been trying to reproduce this issue, but haven’t had any success.

Can you try to restore default parameter values from the Action menu in PixyMon? (And then try again.) We want to make sure that there isn’t another parameter setting that’s causing/contributing to this. If so, we need to address it, but we first need to figure out what’s causing this.

Let me know what you find.

Edward

#11

Hi Edward -

I appreciate that you are looking into this. I restored default values a few times, and I am still getting the same behavior.

#12

Hi GB,
When you observe this, is the lack of detection in default mode somewhat intermittent? (Does it detect the top object some of the time?)

Edward

#13

Hi Edward –

Was there any progress made on this issue?

Thanks.

#14

Hello GB,
We tried several times to reproduce this issue and couldn’t. We even replicated your scenario as close as we could with the same colors but couldn’t get the same behavior. We agree that what you are seeing is probably a bug of some sort, but we’re not having much luck reproducing. Sorry, we haven’t made any progress on this. Could you post a video that shows the issue? Please also show the configuration options you are using.

Edward