Thanks to all who have replied. To clarify my intent, I wish to examine a single image frame that contains multiple instances of pinhole images. Typically these are equi-spaced in either the column or row directions, but not in the orthogonal direction (i.e. equi-spaced along rows, but not in columns).
I have successfully adapted the work done with Jason's project to extract the peaks using localmax function, and from there I can find the centroids, fit 3D Gaussians, extract cross-sections, etc, yielding a very nice tool for pinhole image analysis; many thanks to all who worked with Jason to demonstrate the different ways to skin the cat in MathCad.
The motivation behind my original question stems from the fact that there are often many pinhole images in the frame that I would like to ignore, selecting only a subset to use in calculations that basically measure geometric distortion in a rectangular grid of the most widely separated pinhole images on the frame. The selected subset regions can all be the same size, although this is not required, since I am only interested ultimately in extracting the coordiantes of the image centroids. I do, however, need to preserve the global X Y coordinates that locate each centroid on the overall image frame.
My first thought was that giving the sheet user a drag-select interface would provide a convenient means for specifying which pinhole images to consider.
However, realizing that all of the centroids will have been previously extracted, I would also consider a user input that tells MathCad how many subregions to include in the selected subset within a given radius from the center of the frame, and then, for example, impose additional contraints that require maximizing and equalizing distances between certain image pairs such that the resulting subset of chosen pinhole images forms a rectangular grid of maximal area within the overall image frame. Looked at this way, the centroid data has already been determined, and I would a filter function program to reject data points that don't satisfy the user input selection criteria.
I was just fishing for ideas as to how some of you reading this might attack the same project.
Scott Milligan