Very nice, thank you for doing this!

On Feb 6, 2013, at 3:26 PM, Mike Jarvis <notifications@github.com> wrote:

> In galsim/base.py:
> 
> > @@ -1384,15 +1391,45 @@ class InterpolatedImage(GSObject):
> >      choose interpolants and pad factors, and no warnings are raised when the code is modified to
> >      choose some combination that is known to give significant error.
> >  
> > +    The user can choose to have the image padding use zero (default), Gaussian random noise of some
> > +    variance, or a Gaussian but correlated noise field that is specified either as an ImageCorrFunc,
> > +    an Image (from which a noise correlation function is derived), or a string (interpreted as a
> > +    filename containing an image to use for deriving the noise correlation function).  The user can
> > +    also pass in a random number generator to be used for noise generation.
> Update: I made some changes to the Quintic (and Lanczos and Cubic) initializations to cache the calculations that need to happen at setup, so they only have to be done the first time. The timing script now reports:
> 
> $ python time_noise_pad.py 
> time for test_corr_padding_cf = 28.08
> time for test_corr_padding_im = 47.51
> time for test_corr_padding_imgfile = 27.84
> time for test_corr_nopadding = 6.79
> So that helped quite a bit. And since the _im pathway isn't cached, it makes your point about the ImageCorrFunc initialization even clearer.
> 
> —
> Reply to this email directly or view it on GitHub.
> 
> 


-------------------------------

Rachel Mandelbaum
rmandelb@andrew.cmu.edu
http://www.andrew.cmu.edu/~rmandelb/