One of the great features of Papywizard is its ability to generate an XML output file with all the image position information that can be fed into the stitching software to help orient the images before stitching. It’s especially helpful for panoramas with large areas of blue sky or indistinct clouds. Unfortunately, the Epic 100 does not provide for computer control so I’ve had to struggle with manually placing control points on images of featureless skies. Using Papywizard in simulation mode wasn't possible due to the way the Epic 100 works. .
phill.butte wrote: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.
Using Papywizard would mean basing the movements on the % overlap, which I think is unreliable in this situation.
phill.butte wrote:That's correct, a different amount for each FOV. I sent GigaPan support a request for information on the formula or lookup table they used but never got a response.
I can't say if its unreliable in practice, but % overlap is a derived value from my measurements of the angles. It might turn put to be "close enough" in practice but I think using the actual angles will give me more accurate results.
phill.butte wrote:I just ran a comparison on the two methods and here's what I found for the test pano I did yesterday. The pano was 10 columns by 5 rows with a Canon 60D and 200 mm lens. The image FOV was 5 degrees. The first problem is that the horizontal and vertical overlap figures for the Epic 100 are different for almost all FOV settings, sometimes by as much as 10%. In this case the vertical overlap is 33.2% and the horizontal 29.9%. Papywizard only allows one setting for overlap and it doesn't allow fractions, so I used 33%.
Papywizard calculated that the pitch head movement was 2.32 degrees and the yaw movement was 3.88 degrees for each image. The actual is 2.67 and 4.17. Papywizard calculated the total pitch movement at 11.6 degrees and the total yaw movement at 38 .8 degrees, vs. 13.35 and 41.67 actual. That's a total difference of 13.1% for the pitch and 7% in the yaw axis.
So I would say that for a small panorama using the Papywizard simulator for the Epic 100 would probably be "close enough". For the large, 300-400 gigapixel panos that I like to do I think the accumulated error would be too much.
Users browsing this forum: No registered users and 1 guest