search

robinj / parse-client

0 stars 0 forks source link

RGBScanner returns 0 location. #31

Closed bernien2s closed 11 years ago

bernien2s commented 11 years ago

Assuming this is not an issue with the scanner marker being used, this class returns 0,0,0 each time suggesting it isn't identifying the scanner at all. Misleading print line in SensorTracker states that "Sensor found, but not close enough to hand" prints regardless of whether sensor in scene or not. Probably something small.

bernien2s commented 11 years ago

i should add this is based on the latest commits.

amoebanath commented 11 years ago

Yeah, I'm still working on getting the text elements to show in the right order... That should ideally indicate that a sensor has been found, but it wasn't close enough to a hand for the skeleton recog to work.

To verify scanner isn't an issue, re-add the Prototyping/Nathan folder to the project. Set App.xaml to use BasicTracker as the main application window. Then, you should be able to run and see the basic tracker window. There, over a few runs, use the click-to-find on the live colour window to get the RGB values for the scanner. If they fall in these ranges it should be found. Otherwise, try adjusting these values in Tracking/RGBTracker.cs

if ( image[i * 4 + 2] > 155 & image[i * 4 + 2] < 225 & // RED image[i * 4 + 1] > 155 & image[i * 4 + 1] < 225 & // GREEN image[i * 4] > 0 & image[i * 4] < 70 // BLUE )

Where are you getting the coords from? SensorTracker:: x, y & z?

I'll be in the Lake District today - leaving imminently... do try phoning me if you fancy, but no promises I'll have any signal!!! :P I'll keep pondering. I did test it last week, didn't think I should have broken anything since...

Nath

bernien2s commented 11 years ago

Thanks Nathan! We will certainly have a look to see if it's something more persistent or just something odd on the day. I'll keep you posted. Have fun at the Lake District!

On Sunday, April 7, 2013, amoebanath wrote:

Yeah, I'm still working on getting the text elements to show in the right order... That should ideally indicate that a sensor has been found, but it wasn't close enough to a hand for the skeleton recog to work.

To verify scanner isn't an issue, re-add the Prototyping/Nathan folder to the project. Set App.xaml to use BasicTracker as the main application window. Then, you should be able to run and see the basic tracker window. There, over a few runs, use the click-to-find on the live colour window to get the RGB values for the scanner. If they fall in these ranges it should be found. Otherwise, try adjusting these values in Tracking/RGBTracker.cs

if ( image[i * 4 + 2] > 155 & image[i * 4 + 2] < 225 & // RED image[i * 4 + 1] > 155 & image[i * 4 + 1] < 225 & // GREEN image[i * 4] > 0 & image[i * 4] < 70 // BLUE )

Where are you getting the coords from? SensorTracker:: x, y & z?

I'll be in the Lake District today - leaving imminently... do try phoning me if you fancy, but no promises I'll have any signal!!! :P I'll keep pondering. I did test it last week, didn't think I should have broken anything since...

Nath

— Reply to this email directly or view it on GitHubhttps://github.com/WarwickPARSE/parse-client/issues/31#issuecomment-16011439 .

robinj commented 11 years ago

Assumed to be fixed