The only information available from the Epic 100 when you set up a panorama is the vertical field of view of the image and the number of rows and columns. A key variable is the amount of horizontal and vertical overlap and that's not available from the Epic 100. I measured a vertical overlap of around 32% from 3 to 5 degrees FOV, 31% to 41% from 7.5 to 35 degrees and then 35% to 37% from 40 to 60 degrees FOV. I found it much more straightforward and reliable to just measure the angles each of the two axes move for a specific FOV value and use that in the calculation.
So do I understand that the Gigapan head uses different amounts of overlap between image s depending on the overal pano/scene VFOV?
If so, I wonder why Gigapan designed it like that?
Does it compute a similar amount of overlap on both axes?
Using Papywizard would mean basing the movements on the % overlap, which I think is unreliable in this situation.
Is it unreliable in practice?