# Why is my Gabor patch not resizing as a function of the bounding box?

I'm trying to create a Gabor patch of variable size for an upcoming experiment.

Below is the python function used to generate the code. The code was ported from this tutorial for Matlab (assume import numpy as np):

def gabor_patch(size, lambda_, theta, sigma, phase, trim=.005):
"""Create a Gabor Patch

size : int
Image size (n x n)

lambda_ : int
Spatial frequency (px per cycle)

theta : int or float
Grating orientation in degrees

sigma : int or float
gaussian standard deviation (in pixels)

phase : float
0 to 1 inclusive
"""
# make linear ramp
X0 = (np.linspace(1, size, size) / size) - .5

# Set wavelength and phase
freq = size / float(lambda_)
phaseRad = phase * 2 * np.pi

# Make 2D grating
Xm, Ym = np.meshgrid(X0, X0)

# Change orientation by adding Xm and Ym together in different proportions
thetaRad = (theta / 360.) * 2 * np.pi
grating = np.sin(((Xt + Yt) * freq * 2 * np.pi) + phaseRad)

# 2D Gaussian distribution
gauss = np.exp(-((Xm ** 2) + (Ym ** 2)) / (2 * (sigma / float(size)) ** 2))

# Trim
gauss[gauss < trim] = 0

return grating * gauss


I would like the size of the Gabor patch to increase proportionally to the size parameter. In other words, I would like the dimensions of the bounding box to dictate the diameter of the patch. The problem is that this function does not behave in this way. Instead, the bounding box increases in size while the patch retains the same dimensions.

Example 1: size = 100 Example 2: size = 500 It's not at all obvious to me what I'm doing incorrectly. Could somebody please point me in the right direction?

Please let me know if I can provide further information. Thank you!

• This question appears to be off-topic because it is about a coding problem. Sep 26, 2013 at 22:26
• I assume this question is about programming a psychophysics experiment. There are varying views about when a question about programming a psychological experiment is on topic. This meta question discusses the topic: meta.cogsci.stackexchange.com/questions/471/… Thus, I'd like to think that such questions wouldn't be closed as off topic. That said, I think the OP would get better answers on stack overflow. Sep 27, 2013 at 0:28
• @JeromyAnglim, I'll certainly participate in the meta discussion, but I would just like to point out that this question isn't really about programming per se. It's more about the math behind the Gabor patch than anything else -- it just so happens that I can better express my problem using code as opposed to mathematical notation. Incidentally, I figured out what the problem was. I need to tie the standard deviation to the size of the bounding box in order to get the behavior I expect. Sep 27, 2013 at 17:15
• @JeromyAnglim, I'm a frequent SO poster, so my decision to post here was a conscious one. I needed domain-specific input, which ordinary programmers most likely could not provide. I'd much rather this question not be migrated, if it's all the same. Sep 27, 2013 at 17:27

The size parameter in your code simply means the size of the patch, i. e. the interval in x and y over which you sample your Gabor function. What you are thinking of is the support of the function, i. e. the interval where it is noticeably different from 0. This is determined by the sigma parameter, which is the bandwidth of the Gaussian.
So if you just increase size, you will get a bigger image back, but the area where you can see the ripples will stay the same. If you increase sigma, the area with the ripples will get larger, and then you may have to increase size as well to see all of it.