Hi, I’ve just watched this video, I have some questions about it.
Yes resolution and frame size are the same, and I don’t understand the rest of your question.
You can get the depth of the tag, depends on the sensor and lens though. Please see the comments in find_apriltags_3d_pose.py example.
Thanks for replying, I copied the code and I got the readout window size, my question is, I have already set the resolution for the readout window, but in the code it also calculate the readout window size, has the resolution changed or it remained what I set?
readout window size (1280, 960)
readout window size (640, 480)
The resolution changes every time set_framesize is called. Changing the readout window does Not change the resolution/framesize it just crops the pixel array for faster reading (you’ll notice the image gets cropped, but still the same size). At some point in the script it does change both the window and resolution to center on the tag and read frames faster.
Hi again, I’m confused that is the resolution which set_framesize called using logical pixel? And the pixel array is physical pixel? It’s hard to define both when using almost the same units (or exactly the same units?).
set_framesize() changes the output of the camera module. If the camera module does scaling then it’s unrelated to the physical pixel size.
Is there a unit of the output of set_framesize()?
Or is there a keyword that I can find on internet?
Thanks for replying.
I don’t know what you want to know here… the method sets the cameras scalers to produce an output image. It is not the pixel array size. If you want to do that math start from the camera datasheet and look at the pixel sizes.
