On Feb 15, 2013, at 12:39 AM, Mike Jarvis <notifications@github.com> wrote:

> In galsim/base.py:
> 
> > +                           It is important to keep in mind that the calculation of a
> > +                           galsim.ImageCorrFunc is a non-negligible amount of overhead, so the
> > +                           recommended ways are (b) or (d). In the case of (d), if the same file is
> > +                           used repeatedly, then use of the `use_cache` keyword (see below) can be
> > +                           used to prevent the need for repeated galsim.ImageCorrFunc
> > +                           initializations.
> > +                           (Default `noise_pad = 0.`, i.e., pad with zeros.)
> > +    @param rng             If padding by noise, the user can optionally supply the random noise
> > +                           generator to use for drawing random numbers as `rng` (may be any kind of
> > +                           `galsim.BaseDeviate` object).
> > +                           If `rng=None`, one will be automatically created, using the time as a
> > +                           seed. (Default `rng = None`)
> > +    @param pad_image       Image to be used for deterministically padding the original image.  This
> > +                           can be specified in several ways:
> > +                               (a) as a float, which is interpreted as a constant value to be used
> > +                                   for the padding;
> Not too crazy to worry about, but I think this is the wrong way to implement that kind of check. The GSObjects themselves should have zero background. After all, they will be drawn on a larger image. So what happens at the edge of the GSObject's extent? You don't want a hard edge there.
> 
Oy, right.  Okay, I removed the const padding option from both RG and II, and added a note in the `pad_image` description about what that keyword can be used for - see the commit I just pushed.