forums.naturalpoint.com

Hi,

I updated to the most recent Camera SDK. The previous version was before the switch to smart pointers for the frames and such.

I am using Precision mode (with 6 cameras divided over two camera bars) and use the roundness value to filter out unwanted points during calibration, so we have the best possible data to base the calibration on.

In the new SDK version, Roundness is always 0.
I tried switching to Object mode, and there the value is either 0 or 1 it seems. I can't get it to produce different values.

The aspect ratio does have some floating point values, but there also seem to be precision issues there (only a handfull of different values occur).

Is this a known issue? If so, I need to revert back to the old SDK which would be a shame. We experience crashes in those versions sometimes, in the CameraLibrary DLL, and I was hoping the new SDK would mitigate those crashes.

Have you checked the updated documentation to see if there's a new way to retrieve the roundness values?

I looked at the updated documentation yes. I looked at the almost non-existent wiki, the .txt files thrown in the doc folder of the Camera SDK, as wel as the example code. None of them even mention anything about the roundness value.

Or am I missing something?

There has not been a real changelog for the Camera SDK in ages, only "made compatible with the latest Motive version". So I don't think anything has supposed to be happening differently with the roundness value.

Also, as far as I can tell there is no other way to get the roundness values than from the cObject instance I get out of the camera frames, which has never changed.

The only place I can see the roundness value mentioned in code is in the undocumented cLabelObject, cFrameFilter and cLabelObjectFilter classes.

Hi JeDi,

I appreciate you bringing this to our attention.

Could you confirm which version of the Camera SDK you were using when the roundness value was working correctly? And which version you were using when you first noticed it was always reported as "0"? This will help us identify where the change may have occurred. It sounds like you might be seeing the issue in the latest 3.2.0 Beta 1 version, correct? Did you observe the issue in any previous versions?

Also, what specific camera model are you interfacing with in the CameraSDK?

Hi, thanks for the reply.

The problem is: the previous version we did a test release with is more than two years old. So I can't really tell you in which version it disappeared. The version I noticed this (the first one I was able to test with actual hardware) was very recent: 3.1.4.

Are older versions available somewhere? Then I could try older versions to help searching when this started occurring. I hope to keep at least a version with smart pointers for the frames and such, as that feels more stable to work with

If it helps, it "feels" like a rounding issue or a wrong range used or something like that. Because the times I got something else than 0 in the roundness it jumped to 1 directly. I know that is very vague, but I don't know the inner workings of course.

If there is anything I can do to help pinpoint the problem? Thanks!

Kind regards,
Jeroen