apsc testing: maxdim-related error

[Pete Holzmann]

testing apsc from the command line:

(Windows XP)

If I neglect to give a --maxdim parameter, then on a
simple set of three 6mpxl (2136x2848) images:

Having loaded only the first image, apsc allocated 1.3GB
of RAM and essentially went into some kind of slow
death.

I'm pretty sure it's related to setting a "first octave"
size of 4270x5694 -- looks like it imagines the images
are twice as large as they really are?

If I use --maxdim, even full size (--maxdim 2900), then
everything works nicely.

--p

[ArAgost]

I confirm, it's reproducible

[Seb Perez-D]

On Fri, Feb 8, 2008 at 4:57 PM, ArAgost <ara...@gmail.com> wrote:
> >
> > If I neglect to give a --maxdim parameter, then on a
> > simple set of three 6mpxl (2136x2848) images:
> >
> > Having loaded only the first image, apsc allocated 1.3GB
> > of RAM and essentially went into some kind of slow
> > death.
>

> I confirm, it's reproducible

I would support having a default maxdim equal to 800, just like the
standard autopano-complete.sh script.

Cheers,

Seb