1Transform(3) User Contributed Perl Documentation Transform(3)
2
6 PDL::Transform - Coordinate transforms, image warping, and N-D
7 functions
8
10 use PDL::Transform;
11 my $t = new PDL::Transform::<type>(<opt>)
13 $out = $t->apply($in) # Apply transform to some N-vectors (Transform method)
15 $out = $in->apply($t) # Apply transform to some N-vectors (PDL method)
16 $im1 = $t->map($im); # Transform image coordinates (Transform method)
18 $im1 = $im->map($t); # Transform image coordinates (PDL method)
19 $t2 = $t->compose($t1); # compose two transforms
21 $t2 = $t x $t1; # compose two transforms (by analogy to matrix mult.)
22 $t3 = $t2->inverse(); # invert a transform
24 $t3 = !$t2; # invert a transform (by analogy to logical "not")
25
27 PDL::Transform is a convenient way to represent coordinate
28 transformations and resample images. It embodies functions mapping R^N
29 -> R^M, both with and without inverses. Provision exists for
30 parametrizing functions, and for composing them. You can use this part
31 of the Transform object to keep track of arbitrary functions mapping
32 R^N -> R^M with or without inverses.
33 The simplest way to use a Transform object is to transform vector data
35 between coordinate systems. The "apply" method accepts a PDL whose 0th
36 dimension is coordinate index (all other dimensions are broadcasted
37 over) and transforms the vectors into the new coordinate system.
38 Transform also includes image resampling, via the "map" method. You
40 define a coordinate transform using a Transform object, then use it to
41 remap an image PDL. The output is a remapped, resampled image.
42 You can define and compose several transformations, then apply them all
44 at once to an image. The image is interpolated only once, when all the
45 composed transformations are applied.
46 In keeping with standard practice, but somewhat counterintuitively, the
48 "map" engine uses the inverse transform to map coordinates FROM the
49 destination dataspace (or image plane) TO the source dataspace; hence
50 PDL::Transform keeps track of both the forward and inverse transform.
51 For terseness and convenience, most of the constructors are exported
53 into the current package with the name "t_<transform>", so the
54 following (for example) are synonyms:
55 $t = new PDL::Transform::Radial(); # Long way
57 $t = t_radial(); # Short way
59 Several math operators are overloaded, so that you can compose and
61 invert functions with expression syntax instead of method syntax (see
62 below).
63
65 Coordinate transformations and mappings are a little counterintuitive
66 at first. Here are some examples of transforms in action:
67 use PDL::Transform;
69 $x = rfits('m51.fits'); # Substitute path if necessary!
70 $ts = t_linear(Scale=>3); # Scaling transform
71 $w = pgwin(xs);
73 $w->imag($x);
74 ## Grow m51 by a factor of 3; origin is at lower left.
76 $y = $ts->map($x,{pix=>1}); # pix option uses direct pixel coord system
77 $w->imag($y);
78 ## Shrink m51 by a factor of 3; origin still at lower left.
80 $c = $ts->unmap($x, {pix=>1});
81 $w->imag($c);
82 ## Grow m51 by a factor of 3; origin is at scientific origin.
84 $d = $ts->map($x,$x->hdr); # FITS hdr template prevents autoscaling
85 $w->imag($d);
86 ## Shrink m51 by a factor of 3; origin is still at sci. origin.
88 $e = $ts->unmap($x,$x->hdr);
89 $w->imag($e);
90 ## A no-op: shrink m51 by a factor of 3, then autoscale back to size
92 $f = $ts->map($x); # No template causes autoscaling of output
93
95 '!'
96 The bang is a unary inversion operator. It binds exactly as tightly
97 as the normal bang operator.
98 'x'
100 By analogy to matrix multiplication, 'x' is the compose operator, so
101 these two expressions are equivalent:
102 $f->inverse()->compose($g)->compose($f) # long way
104 !$f x $g x $f # short way
105 Both of those expressions are equivalent to the mathematical
107 expression f^-1 o g o f, or f^-1(g(f(x))).
108 '**'
110 By analogy to numeric powers, you can apply an operator a positive
111 integer number of times with the ** operator:
112 $f->compose($f)->compose($f) # long way
114 $f**3 # short way
115
117 Transforms are perl hashes. Here's a list of the meaning of each key:
118 func
120 Ref to a subroutine that evaluates the transformed coordinates.
121 It's called with the input coordinate, and the "params" hash. This
122 springboarding is done via explicit ref rather than by subclassing,
123 for convenience both in coding new transforms (just add the
124 appropriate sub to the module) and in adding custom transforms at
125 run-time. Note that, if possible, new "func"s should support inplace
126 operation to save memory when the data are flagged inplace. But
127 "func" should always return its result even when flagged to compute
128 in-place.
129 "func" should treat the 0th dimension of its input as a dimensional
131 index (running 0..N-1 for R^N operation) and broadcast over all
132 other input dimensions.
133 inv
135 Ref to an inverse method that reverses the transformation. It must
136 accept the same "params" hash that the forward method accepts. This
137 key can be left undefined in cases where there is no inverse.
138 idim, odim
140 Number of useful dimensions for indexing on the input and output
141 sides (ie the order of the 0th dimension of the coordinates to be
142 fed in or that come out). If this is set to 0, then as many are
143 allocated as needed.
144 name
146 A shorthand name for the transformation (convenient for debugging).
147 You should plan on using UNIVERAL::isa to identify classes of
148 transformation, e.g. all linear transformations should be subclasses
149 of PDL::Transform::Linear. That makes it easier to add smarts to,
150 e.g., the compose() method.
151 itype
153 An array containing the name of the quantity that is expected from
154 the input ndarray for the transform, for each dimension. This field
155 is advisory, and can be left blank if there's no obvious quantity
156 associated with the transform. This is analogous to the CTYPEn
157 field used in FITS headers.
158 oname
160 Same as itype, but reporting what quantity is delivered for each
161 dimension.
162 iunit
164 The units expected on input, if a specific unit (e.g. degrees) is
165 expected. This field is advisory, and can be left blank if there's
166 no obvious unit associated with the transform.
167 ounit
169 Same as iunit, but reporting what quantity is delivered for each
170 dimension.
171 params
173 Hash ref containing relevant parameters or anything else the func
174 needs to work right.
175 is_inverse
177 Bit indicating whether the transform has been inverted. That is
178 useful for some stringifications (see the PDL::Transform::Linear
179 stringifier), and may be useful for other things.
180 Transforms should be inplace-aware where possible, to prevent excessive
182 memory usage.
183 If you define a new type of transform, consider generating a new
185 stringify method for it. Just define the sub "stringify" in the
186 subclass package. It should call SUPER::stringify to generate the
187 first line (though the PDL::Transform::Composition bends this rule by
188 tweaking the top-level line), then output (indented) additional lines
189 as necessary to fully describe the transformation.
190
192 Transforms have a mechanism for labeling the units and type of each
193 coordinate, but it is just advisory. A routine to identify and, if
194 necessary, modify units by scaling would be a good idea. Currently, it
195 just assumes that the coordinates are correct for (e.g.) FITS
196 scientific-to-pixel transformations.
197 Composition works OK but should probably be done in a more
199 sophisticated way so that, for example, linear transformations are
200 combined at the matrix level instead of just strung together pixel-to-
201 pixel.
202
204 There are both operators and constructors. The constructors are all
205 exported, all begin with "t_", and all return objects that are
206 subclasses of PDL::Transform.
207 The "apply", "invert", "map", and "unmap" methods are also exported to
209 the "PDL" package: they are both Transform methods and PDL methods.
210
212 apply
213 Signature: (data(); PDL::Transform t)
214 $out = $data->apply($t);
216 $out = $t->apply($data);
217 Apply a transformation to some input coordinates.
219 In the example, $t is a PDL::Transform and $data is a PDL to be
221 interpreted as a collection of N-vectors (with index in the 0th
222 dimension). The output is a similar but transformed PDL.
223 For convenience, this is both a PDL method and a Transform method.
225 invert
227 Signature: (data(); PDL::Transform t)
228 $out = $t->invert($data);
230 $out = $data->invert($t);
231 Apply an inverse transformation to some input coordinates.
233 In the example, $t is a PDL::Transform and $data is an ndarray to be
235 interpreted as a collection of N-vectors (with index in the 0th
236 dimension). The output is a similar ndarray.
237 For convenience this is both a PDL method and a PDL::Transform method.
239 map
241 Signature: (k0(); pdl *in; pdl *out; pdl *map; SV *boundary; SV *method;
242 long big; double blur; double sv_min; char flux; SV *bv)
243 match
245 $y = $x->match($c); # Match $c's header and size
246 $y = $x->match([100,200]); # Rescale to 100x200 pixels
247 $y = $x->match([100,200],{rect=>1}); # Rescale and remove rotation/skew.
248 Resample a scientific image to the same coordinate system as another.
250 The example above is syntactic sugar for
252 $y = $x->map(t_identity, $c, ...);
254 it resamples the input PDL with the identity transformation in
256 scientific coordinates, and matches the pixel coordinate system to $c's
257 FITS header.
258 There is one difference between match and map: match makes the
260 "rectify" option to "map" default to 0, not 1. This only affects
261 matching where autoscaling is required (i.e. the array ref example
262 above). By default, that example simply scales $x to the new size and
263 maintains any rotation or skew in its scientific-to-pixel coordinate
264 transform.
265 map
267 $y = $x->map($xform,[<template>],[\%opt]); # Distort $x with transform $xform
268 $y = $x->map(t_identity,[$pdl],[\%opt]); # rescale $x to match $pdl's dims.
269 Resample an image or N-D dataset using a coordinate transform.
271 The data are resampled so that the new pixel indices are proportional
273 to the transformed coordinates rather than the original ones.
274 The operation uses the inverse transform: each output pixel location is
276 inverse-transformed back to a location in the original dataset, and the
277 value is interpolated or sampled appropriately and copied into the
278 output domain. A variety of sampling options are available, trading
279 off speed and mathematical correctness.
280 For convenience, this is both a PDL method and a PDL::Transform method.
282 "map" is FITS-aware: if there is a FITS header in the input data, then
284 the coordinate transform acts on the scientific coordinate system
285 rather than the pixel coordinate system.
286 By default, the output coordinates are separated from pixel coordinates
288 by a single layer of indirection. You can specify the mapping between
289 output transform (scientific) coordinates to pixel coordinates using
290 the "orange" and "irange" options (see below), or by supplying a FITS
291 header in the template.
292 If you don't specify an output transform, then the output is
294 autoscaled: "map" transforms a few vectors in the forward direction to
295 generate a mapping that will put most of the data on the image plane,
296 for most transformations. The calculated mapping gets stuck in the
297 output's FITS header.
298 Autoscaling is especially useful for rescaling images -- if you specify
300 the identity transform and allow autoscaling, you duplicate the
301 functionality of rescale2d, but with more options for interpolation.
302 You can operate in pixel space, and avoid autoscaling of the output, by
304 setting the "nofits" option (see below).
305 The output has the same data type as the input. This is a feature, but
307 it can lead to strange-looking banding behaviors if you use
308 interpolation on an integer input variable.
309 The "template" can be one of:
311 • a PDL
313 The PDL and its header are copied to the output array, which is then
315 populated with data. If the PDL has a FITS header, then the FITS
316 transform is automatically applied so that $t applies to the output
317 scientific coordinates and not to the output pixel coordinates. In
318 this case the NAXIS fields of the FITS header are ignored.
319 • a FITS header stored as a hash ref
321 The FITS NAXIS fields are used to define the output array, and the
323 FITS transformation is applied to the coordinates so that $t applies
324 to the output scientific coordinates.
325 • a list ref
327 This is a list of dimensions for the output array. The code
329 estimates appropriate pixel scaling factors to fill the available
330 space. The scaling factors are placed in the output FITS header.
331 • nothing
333 In this case, the input image size is used as a template, and
335 scaling is done as with the list ref case (above).
336 OPTIONS:
338 The following options are interpreted:
340 b, bound, boundary, Boundary (default = 'truncate')
342 This is the boundary condition to be applied to the input image; it
343 is passed verbatim to range or interpND in the sampling or
344 interpolating stage. Other values are 'forbid','extend', and
345 'periodic'. You can abbreviate this to a single letter. The
346 default 'truncate' causes the entire notional space outside the
347 original image to be filled with 0.
348 pix, Pixel, nf, nofits, NoFITS (default = 0)
350 If you set this to a true value, then FITS headers and
351 interpretation are ignored; the transformation is treated as being
352 in raw pixel coordinates.
353 j, J, just, justify, Justify (default = 0)
355 If you set this to 1, then output pixels are autoscaled to have unit
356 aspect ratio in the output coordinates. If you set it to a non-1
357 value, then it is the aspect ratio between the first dimension and
358 all subsequent dimensions -- or, for a 2-D transformation, the
359 scientific pixel aspect ratio. Values less than 1 shrink the scale
360 in the first dimension compared to the other dimensions; values
361 greater than 1 enlarge it compared to the other dimensions. (This
362 is the same sense as in the PGPLOT interface.)
363 ir, irange, input_range, Input_Range
365 This is a way to modify the autoscaling. It specifies the range of
366 input scientific (not necessarily pixel) coordinates that you want
367 to be mapped to the output image. It can be either a nested array
368 ref or an ndarray. The 0th dim (outside coordinate in the array
369 ref) is dimension index in the data; the 1st dim should have order
370 2. For example, passing in either [[-1,2],[3,4]] or
371 pdl([[-1,2],[3,4]]) limites the map to the quadrilateral in input
372 space defined by the four points (-1,3), (-1,4), (2,4), and (2,3).
373 As with plain autoscaling, the quadrilateral gets sparsely sampled
375 by the autoranger, so pathological transformations can give you
376 strange results.
377 This parameter is overridden by "orange", below.
379 or, orange, output_range, Output_Range
381 This sets the window of output space that is to be sampled onto the
382 output array. It works exactly like "irange", except that it
383 specifies a quadrilateral in output space. Since the output pixel
384 array is itself a quadrilateral, you get pretty much exactly what
385 you asked for.
386 This parameter overrides "irange", if both are specified. It forces
388 rectification of the output (so that scientific axes align with the
389 pixel grid).
390 r, rect, rectify
392 This option defaults TRUE and controls how autoscaling is performed.
393 If it is true or undefined, then autoscaling adjusts so that pixel
394 coordinates in the output image are proportional to individual
395 scientific coordinates. If it is false, then autoscaling
396 automatically applies the inverse of any input FITS transformation
397 *before* autoscaling the pixels. In the special case of linear
398 transformations, this preserves the rectangular shape of the
399 original pixel grid and makes output pixel coordinate proportional
400 to input coordinate.
401 m, method, Method
403 This option controls the interpolation method to be used.
404 Interpolation greatly affects both speed and quality of output. For
405 most cases the option is directly passed to interpND for
406 interpolation. Possible options, in order from fastest to slowest,
407 are:
408 • s, sample (default for ints)
410 Pixel values in the output plane are sampled from the closest
412 data value in the input plane. This is very fast but not very
413 accurate for either magnification or decimation (shrinking). It
414 is the default for templates of integer type.
415 • l, linear (default for floats)
417 Pixel values are linearly interpolated from the closest data
419 value in the input plane. This is reasonably fast but only
420 accurate for magnification. Decimation (shrinking) of the image
421 causes aliasing and loss of photometry as features fall between
422 the samples. It is the default for floating-point templates.
423 • c, cubic
425 Pixel values are interpolated using an N-cubic scheme from a
427 4-pixel N-cube around each coordinate value. As with linear
428 interpolation, this is only accurate for magnification.
429 • f, fft
431 Pixel values are interpolated using the term coefficients of the
433 Fourier transform of the original data. This is the most
434 appropriate technique for some kinds of data, but can yield
435 undesired "ringing" for expansion of normal images. Best suited
436 to studying images with repetitive or wavelike features.
437 • h, hanning
439 Pixel values are filtered through a spatially-variable filter
441 tuned to the computed Jacobian of the transformation, with
442 hanning-window (cosine) pixel rolloff in each dimension. This
443 prevents aliasing in the case where the image is distorted or
444 shrunk, but allows small amounts of aliasing at pixel edges
445 wherever the image is enlarged.
446 • g, gaussian, j, jacobian
448 Pixel values are filtered through a spatially-variable filter
450 tuned to the computed Jacobian of the transformation, with radial
451 Gaussian rolloff. This is the most accurate resampling method,
452 in the sense of introducing the fewest artifacts into a properly
453 sampled data set. This method uses a lookup table to speed up
454 calculation of the Gaussian weighting.
455 • G
457 This method works exactly like 'g' (above), except that the
459 Gaussian values are computed explicitly for every sample -- which
460 is considerably slower.
461 blur, Blur (default = 1.0)
463 This value scales the input-space footprint of each output pixel in
464 the gaussian and hanning methods. It's retained for historical
465 reasons. Larger values yield blurrier images; values significantly
466 smaller than unity cause aliasing. The parameter has slightly
467 different meanings for Gaussian and Hanning interpolation. For
468 Hanning interpolation, numbers smaller than unity control the
469 sharpness of the border at the edge of each pixel (so that blur=>0
470 is equivalent to sampling for non-decimating transforms). For
471 Gaussian interpolation, the blur factor parameter controls the width
472 parameter of the Gaussian around the center of each pixel.
473 sv, SV (default = 1.0)
475 This value lets you set the lower limit of the transformation's
476 singular values in the hanning and gaussian methods, limiting the
477 minimum radius of influence associated with each output pixel.
478 Large numbers yield smoother interpolation in magnified parts of the
479 image but don't affect reduced parts of the image.
480 big, Big (default = 0.5)
482 This is the largest allowable input spot size which may be mapped to
483 a single output pixel by the hanning and gaussian methods, in units
484 of the largest non-broadcast input dimension. (i.e. the default
485 won't let you reduce the original image to less than 5 pixels
486 across). This places a limit on how long the processing can take
487 for pathological transformations. Smaller numbers keep the code
488 from hanging for a long time; larger numbers provide for photometric
489 accuracy in more pathological cases. Numbers larer than 1.0 are
490 silly, because they allow the entire input array to be compressed
491 into a region smaller than a single pixel.
492 Wherever an output pixel would require averaging over an area that
494 is too big in input space, it instead gets NaN or the bad value.
495 phot, photometry, Photometry
497 This lets you set the style of photometric conversion to be used in
498 the hanning or gaussian methods. You may choose:
499 • 0, s, surf, surface, Surface (default)
501 (this is the default): surface brightness is preserved over the
503 transformation, so features maintain their original intensity.
504 This is what the sampling and interpolation methods do.
505 • 1, f, flux, Flux
507 Total flux is preserved over the transformation, so that the
509 brightness integral over image regions is preserved. Parts of
510 the image that are shrunk wind up brighter; parts that are
511 enlarged end up fainter.
512 VARIABLE FILTERING:
514 The 'hanning' and 'gaussian' methods of interpolation give
516 photometrically accurate resampling of the input data for arbitrary
517 transformations. At each pixel, the code generates a linear
518 approximation to the input transformation, and uses that linearization
519 to estimate the "footprint" of the output pixel in the input space.
520 The output value is a weighted average of the appropriate input spaces.
521 A caveat about these methods is that they assume the transformation is
523 continuous. Transformations that contain discontinuities will give
524 incorrect results near the discontinuity. In particular, the 180th
525 meridian isn't handled well in lat/lon mapping transformations (see
526 PDL::Transform::Cartography) -- pixels along the 180th meridian get the
527 average value of everything along the parallel occupied by the pixel.
528 This flaw is inherent in the assumptions that underly creating a
529 Jacobian matrix. Maybe someone will write code to work around it.
530 Maybe that someone is you.
531 BAD VALUES:
533 "map()" supports bad values in the data array. Bad values in the input
535 array are propagated to the output array. The 'g' and 'h' methods will
536 do some smoothing over bad values: if more than 1/3 of the weighted
537 input-array footprint of a given output pixel is bad, then the output
538 pixel gets marked bad.
539 map does not process bad values. It will set the bad-value flag of all
541 output ndarrays if the flag is set for any of the input ndarrays.
542 unmap
544 Signature: (data(); PDL::Transform a; template(); \%opt)
545 $out_image = $in_image->unmap($t,[<options>],[<template>]);
547 $out_image = $t->unmap($in_image,[<options>],[<template>]);
548 Map an image or N-D dataset using the inverse as a coordinate
550 transform.
551 This convenience function just inverts $t and calls "map" on the
553 inverse; everything works the same otherwise. For convenience, it is
554 both a PDL method and a PDL::Transform method.
555 t_inverse
557 $t2 = t_inverse($t);
558 $t2 = $t->inverse;
559 $t2 = $t ** -1;
560 $t2 = !$t;
561 Return the inverse of a PDL::Transform. This just reverses the
563 func/inv, idim/odim, itype/otype, and iunit/ounit pairs. Note that
564 sometimes you end up with a transform that cannot be applied or mapped,
565 because either the mathematical inverse doesn't exist or the inverse
566 func isn't implemented.
567 You can invert a transform by raising it to a negative power, or by
569 negating it with '!'.
570 The inverse transform remains connected to the main transform because
572 they both point to the original parameters hash. That turns out to be
573 useful.
574 t_compose
576 $f2 = t_compose($f, $g,[...]);
577 $f2 = $f->compose($g[,$h,$i,...]);
578 $f2 = $f x $g x ...;
579 Function composition: f(g(x)), f(g(h(x))), ...
581 You can also compose transforms using the overloaded matrix-
583 multiplication (nee repeat) operator 'x'.
584 This is accomplished by inserting a splicing code ref into the "func"
586 and "inv" slots. It combines multiple compositions into a single list
587 of transforms to be executed in order, fram last to first (in keeping
588 with standard mathematical notation). If one of the functions is
589 itself a composition, it is interpolated into the list rather than left
590 separate. Ultimately, linear transformations may also be combined
591 within the list.
592 No checking is done that the itype/otype and iunit/ounit fields are
594 compatible -- that may happen later, or you can implement it yourself
595 if you like.
596 t_wrap
598 $g1fg = $f->wrap($g);
599 $g1fg = t_wrap($f,$g);
600 Shift a transform into a different space by 'wrapping' it with a
602 second.
603 This is just a convenience function for two "t_compose" calls.
605 "$x->wrap($y)" is the same as "(!$y) x $x x $y": the resulting
606 transform first hits the data with $y, then with $x, then with the
607 inverse of $y.
608 For example, to shift the origin of rotation, do this:
610 $im = rfits('m51.fits');
612 $tf = t_fits($im);
613 $tr = t_linear({rot=>30});
614 $im1 = $tr->map($tr); # Rotate around pixel origin
615 $im2 = $tr->map($tr->wrap($tf)); # Rotate round FITS scientific origin
616 t_identity
618 my $xform = t_identity
619 my $xform = new PDL::Transform;
620 Generic constructor generates the identity transform.
622 This constructor really is trivial -- it is mainly used by the other
624 transform constructors. It takes no parameters and returns the
625 identity transform.
626 t_lookup
628 $f = t_lookup($lookup, {<options>});
629 Transform by lookup into an explicit table.
631 You specify an N+1-D PDL that is interpreted as an N-D lookup table of
633 column vectors (vector index comes last). The last dimension has order
634 equal to the output dimensionality of the transform.
635 For added flexibility in data space, You can specify pre-lookup linear
637 scaling and offset of the data. Of course you can specify the
638 interpolation method to be used. The linear scaling stuff is a little
639 primitive; if you want more, try composing the linear transform with
640 this one.
641 The prescribed values in the lookup table are treated as pixel-
643 centered: that is, if your input array has N elements per row then
644 valid data exist between the locations (-0.5) and (N-0.5) in lookup
645 pixel space, because the pixels (which are numbered from 0 to N-1) are
646 centered on their locations.
647 Lookup is done using interpND, so the boundary conditions and
649 broadcasting behaviour follow from that.
650 The indexed-over dimensions come first in the table, followed by a
652 single dimension containing the column vector to be output for each set
653 of other dimensions -- ie to output 2-vectors from 2 input parameters,
654 each of which can range from 0 to 49, you want an index that has
655 dimension list (50,50,2). For the identity lookup table you could use
656 "cat(xvals(50,50),yvals(50,50))".
657 If you want to output a single value per input vector, you still need
659 that last index broadcasting dimension -- if necessary, use
660 "dummy(-1,1)".
661 The lookup index scaling is: out = lookup[ (scale * data) + offset ].
663 A simplistic table inversion routine is included. This means that you
665 can (for example) use the "map" method with "t_lookup" transformations.
666 But the table inversion is exceedingly slow, and not practical for
667 tables larger than about 100x100. The inversion table is calculated in
668 its entirety the first time it is needed, and then cached until the
669 object is destroyed.
670 Options are listed below; there are several synonyms for each.
672 s, scale, Scale
674 (default 1.0) Specifies the linear amount of scaling to be done
675 before lookup. You can feed in a scalar or an N-vector; other
676 values may cause trouble. If you want to save space in your table,
677 then specify smaller scale numbers.
678 o, offset, Offset
680 (default 0.0) Specifies the linear amount of offset before lookup.
681 This is only a scalar, because it is intended to let you switch to
682 corner-centered coordinates if you want to (just feed in o=-0.25).
683 b, bound, boundary, Boundary
685 Boundary condition to be fed to interpND
686 m, method, Method
688 Interpolation method to be fed to interpND
689 EXAMPLE
691 To scale logarithmically the Y axis of m51, try:
693 $x = float rfits('m51.fits');
695 $lookup = xvals(128,128) -> cat( 10**(yvals(128,128)/50) * 256/10**2.55 );
696 $t = t_lookup($lookup);
697 $y = $t->map($x);
698 To do the same thing but with a smaller lookup table, try:
700 $lookup = 16 * xvals(17,17)->cat(10**(yvals(17,17)/(100/16)) * 16/10**2.55);
702 $t = t_lookup($lookup,{scale=>1/16.0});
703 $y = $t->map($x);
704 (Notice that, although the lookup table coordinates are is divided by
706 16, it is a 17x17 -- so linear interpolation works right to the edge of
707 the original domain.)
708 NOTES
710 Inverses are not yet implemented -- the best way to do it might be by
712 judicious use of map() on the forward transformation.
713 the type/unit fields are ignored.
715 t_linear
717 $f = t_linear({options});
718 Linear (affine) transformations with optional offset
720 t_linear implements simple matrix multiplication with offset, also
722 known as the affine transformations.
723 You specify the linear transformation with pre-offset, a mixing matrix,
725 and a post-offset. That overspecifies the transformation, so you can
726 choose your favorite method to specify the transform you want. The
727 inverse transform is automagically generated, provided that it actually
728 exists (the transform matrix is invertible). Otherwise, the inverse
729 transform just croaks.
730 Extra dimensions in the input vector are ignored, so if you pass a 3xN
732 vector into a 3-D linear transformation, the final dimension is passed
733 through unchanged.
734 The options you can usefully pass in are:
736 s, scale, Scale
738 A scaling scalar (heh), vector, or matrix. If you specify a vector
739 it is treated as a diagonal matrix (for convenience). It gets left-
740 multiplied with the transformation matrix you specify (or the
741 identity), so that if you specify both a scale and a matrix the
742 scaling is done after the rotation or skewing or whatever.
743 r, rot, rota, rotation, Rotation
745 A rotation angle in degrees -- useful for 2-D and 3-D data only. If
746 you pass in a scalar, it specifies a rotation from the 0th axis
747 toward the 1st axis. If you pass in a 3-vector as either a PDL or
748 an array ref (as in "rot=>[3,4,5]"), then it is treated as a set of
749 Euler angles in three dimensions, and a rotation matrix is generated
750 that does the following, in order:
751 • Rotate by rot->(2) degrees from 0th to 1st axis
753 • Rotate by rot->(1) degrees from the 2nd to the 0th axis
755 • Rotate by rot->(0) degrees from the 1st to the 2nd axis
757 The rotation matrix is left-multiplied with the transformation
759 matrix you specify, so that if you specify both rotation and a
760 general matrix the rotation happens after the more general operation
761 -- though that is deprecated.
762 Of course, you can duplicate this functionality -- and get more
764 general -- by generating your own rotation matrix and feeding it in
765 with the "matrix" option.
766 m, matrix, Matrix
768 The transformation matrix. It does not even have to be square, if
769 you want to change the dimensionality of your input. If it is
770 invertible (note: must be square for that), then you automagically
771 get an inverse transform too.
772 pre, preoffset, offset, Offset
774 The vector to be added to the data before they get multiplied by the
775 matrix (equivalent of CRVAL in FITS, if you are converting from
776 scientific to pixel units).
777 post, postoffset, shift, Shift
779 The vector to be added to the data after it gets multiplied by the
780 matrix (equivalent of CRPIX-1 in FITS, if youre converting from
781 scientific to pixel units).
782 d, dim, dims, Dims
784 Most of the time it is obvious how many dimensions you want to deal
785 with: if you supply a matrix, it defines the transformation; if you
786 input offset vectors in the "pre" and "post" options, those define
787 the number of dimensions. But if you only supply scalars, there is
788 no way to tell and the default number of dimensions is 2. This
789 provides a way to do, e.g., 3-D scaling: just set
790 "{s="<scale-factor>, dims=>3}> and you are on your way.
791 NOTES
793 the type/unit fields are currently ignored by t_linear.
795 t_scale
797 $f = t_scale(<scale>)
798 Convenience interface to "t_linear".
800 t_scale produces a transform that scales around the origin by a fixed
802 amount. It acts exactly the same as "t_linear(Scale="\<scale\>)>.
803 t_offset
805 $f = t_offset(<shift>)
806 Convenience interface to "t_linear".
808 t_offset produces a transform that shifts the origin to a new location.
810 It acts exactly the same as "t_linear(Pre="\<shift\>)>.
811 t_rot
813 $f = t_rot(<rotation-in-degrees>)
814 Convenience interface to "t_linear".
816 t_rot produces a rotation transform in 2-D (scalar), 3-D (3-vector), or
818 N-D (matrix). It acts exactly the same as "t_linear(Rot="\<shift\>)>.
819 t_fits
821 $f = t_fits($fits,[option]);
822 FITS pixel-to-scientific transformation with inverse
824 You feed in a hash ref or a PDL with one of those as a header, and you
826 get back a transform that converts 0-originated, pixel-centered
827 coordinates into scientific coordinates via the transformation in the
828 FITS header. For most FITS headers, the transform is reversible, so
829 applying the inverse goes the other way. This is just a convenience
830 subclass of PDL::Transform::Linear, but with unit/type support using
831 the FITS header you supply.
832 For now, this transform is rather limited -- it really ought to accept
834 units differences and stuff like that, but they are just ignored for
835 now. Probably that would require putting units into the whole
836 transform framework.
837 This transform implements the linear transform part of the WCS FITS
839 standard outlined in Greisen & Calabata 2002 (A&A in press; find it at
840 "http://arxiv.org/abs/astro-ph/0207407").
841 As a special case, you can pass in the boolean option "ignore_rgb"
843 (default 0), and if you pass in a 3-D FITS header in which the last
844 dimension has exactly 3 elements, it will be ignored in the output
845 transformation. That turns out to be handy for handling rgb images.
846 t_code
848 $f = t_code(<func>,[<inv>],[options]);
849 Transform implementing arbitrary perl code.
851 This is a way of getting quick-and-dirty new transforms. You pass in
853 anonymous (or otherwise) code refs pointing to subroutines that
854 implement the forward and, optionally, inverse transforms. The
855 subroutines should accept a data PDL followed by a parameter hash ref,
856 and return the transformed data PDL. The parameter hash ref can be set
857 via the options, if you want to.
858 Options that are accepted are:
860 p,params
862 The parameter hash that will be passed back to your code (defaults
863 to the empty hash).
864 n,name
866 The name of the transform (defaults to "code").
867 i, idim (default 2)
869 The number of input dimensions (additional ones should be passed
870 through unchanged)
871 o, odim (default 2)
873 The number of output dimensions
874 itype
876 The type of the input dimensions, in an array ref (optional and
877 advisiory)
878 otype
880 The type of the output dimension, in an array ref (optional and
881 advisory)
882 iunit
884 The units that are expected for the input dimensions (optional and
885 advisory)
886 ounit
888 The units that are returned in the output (optional and advisory).
889 The code variables are executable perl code, either as a code ref or as
891 a string that will be eval'ed to produce code refs. If you pass in a
892 string, it gets eval'ed at call time to get a code ref. If it compiles
893 OK but does not return a code ref, then it gets re-evaluated with "sub
894 { ... }" wrapped around it, to get a code ref.
895 Note that code callbacks like this can be used to do really weird
897 things and generate equally weird results -- caveat scriptor!
898 t_cylindrical
900 "t_cylindrical" is an alias for "t_radial"
901 t_radial
903 $f = t_radial(<options>);
904 Convert Cartesian to radial/cylindrical coordinates. (2-D/3-D; with
906 inverse)
907 Converts 2-D Cartesian to radial (theta,r) coordinates. You can choose
909 direct or conformal conversion. Direct conversion preserves radial
910 distance from the origin; conformal conversion preserves local angles,
911 so that each small-enough part of the image only appears to be scaled
912 and rotated, not stretched. Conformal conversion puts the radius on a
913 logarithmic scale, so that scaling of the original image plane is
914 equivalent to a simple offset of the transformed image plane.
915 If you use three or more dimensions, the higher dimensions are ignored,
917 yielding a conversion from Cartesian to cylindrical coordinates, which
918 is why there are two aliases for the same transform. If you use higher
919 dimensionality than 2, you must manually specify the origin or you will
920 get dimension mismatch errors when you apply the transform.
921 Theta runs clockwise instead of the more usual counterclockwise; that
923 is to preserve the mirror sense of small structures.
924 OPTIONS:
926 d, direct, Direct
928 Generate (theta,r) coordinates out (this is the default);
929 incompatible with Conformal. Theta is in radians, and the radial
930 coordinate is in the units of distance in the input plane.
931 r0, c, conformal, Conformal
933 If defined, this floating-point value causes t_radial to generate
934 (theta, ln(r/r0)) coordinates out. Theta is in radians, and the
935 radial coordinate varies by 1 for each e-folding of the r0-scaled
936 distance from the input origin. The logarithmic scaling is useful
937 for viewing both large and small things at the same time, and for
938 keeping shapes of small things preserved in the image.
939 o, origin, Origin [default (0,0,0)]
941 This is the origin of the expansion. Pass in a PDL or an array ref.
942 u, unit, Unit [default 'radians']
944 This is the angular unit to be used for the azimuth.
945 EXAMPLES
947 These examples do transformations back into the same size image as they
949 started from; by suitable use of the "transform" option to "unmap" you
950 can send them to any size array you like.
951 Examine radial structure in M51: Here, we scale the output to stretch
953 2*pi radians out to the full image width in the horizontal direction,
954 and to stretch 1 radius out to a diameter in the vertical direction.
955 $x = rfits('m51.fits');
957 $ts = t_linear(s => [250/2.0/3.14159, 2]); # Scale to fill orig. image
958 $tu = t_radial(o => [130,130]); # Expand around galactic core
959 $y = $x->map($ts x $tu);
960 Examine radial structure in M51 (conformal): Here, we scale the output
962 to stretch 2*pi radians out to the full image width in the horizontal
963 direction, and scale the vertical direction by the exact same amount to
964 preserve conformality of the operation. Notice that each piece of the
965 image looks "natural" -- only scaled and not stretched.
966 $x = rfits('m51.fits')
968 $ts = t_linear(s=> 250/2.0/3.14159); # Note scalar (heh) scale.
969 $tu = t_radial(o=> [130,130], r0=>5); # 5 pix. radius -> bottom of image
970 $y = $ts->compose($tu)->unmap($x);
971 t_quadratic
973 $t = t_quadratic(<options>);
974 Quadratic scaling -- cylindrical pincushion (n-d; with inverse)
976 Quadratic scaling emulates pincushion in a cylindrical optical system:
978 separate quadratic scaling is applied to each axis. You can apply
979 separate distortion along any of the principal axes. If you want
980 different axes, use "t_wrap" and "t_linear" to rotate them to the
981 correct angle. The scaling options may be scalars or vectors; if they
982 are scalars then the expansion is isotropic.
983 The formula for the expansion is:
985 f(a) = ( <a> + <strength> * a^2/<L_0> ) / (abs(<strength>) + 1)
987 where <strength> is a scaling coefficient and <L_0> is a fundamental
989 length scale. Negative values of <strength> result in a pincushion
990 contraction.
991 Note that, because quadratic scaling does not have a strict inverse for
993 coordinate systems that cross the origin, we cheat slightly and use $x
994 * abs($x) rather than $x**2. This does the Right thing for pincushion
995 and barrel distortion, but means that t_quadratic does not behave
996 exactly like t_cubic with a null cubic strength coefficient.
997 OPTIONS
999 o,origin,Origin
1001 The origin of the pincushion. (default is the, er, origin).
1002 l,l0,length,Length,r0
1004 The fundamental scale of the transformation -- the radius that
1005 remains unchanged. (default=1)
1006 s,str,strength,Strength
1008 The relative strength of the pincushion. (default = 0.1)
1009 honest (default=0)
1011 Sets whether this is a true quadratic coordinate transform. The
1012 more common form is pincushion or cylindrical distortion, which
1013 switches branches of the square root at the origin (for symmetric
1014 expansion). Setting honest to a non-false value forces true
1015 quadratic behavior, which is not mirror-symmetric about the origin.
1016 d, dim, dims, Dims
1018 The number of dimensions to quadratically scale (default is the
1019 dimensionality of your input vectors)
1020 t_cubic
1022 $t = t_cubic(<options>);
1023 Cubic scaling - cubic pincushion (n-d; with inverse)
1025 Cubic scaling is a generalization of t_quadratic to a purely cubic
1027 expansion.
1028 The formula for the expansion is:
1030 f(a) = ( a' + st * a'^3/L_0^2 ) / (1 + abs(st)) + origin
1032 where a'=(a-origin). That is a simple pincushion expansion/contraction
1034 that is fixed at a distance of L_0 from the origin.
1035 Because there is no quadratic term the result is always invertible with
1037 one real root, and there is no mucking about with complex numbers or
1038 multivalued solutions.
1039 OPTIONS
1041 o,origin,Origin
1043 The origin of the pincushion. (default is the, er, origin).
1044 l,l0,length,Length,r0
1046 The fundamental scale of the transformation -- the radius that
1047 remains unchanged. (default=1)
1048 d, dim, dims, Dims
1050 The number of dimensions to treat (default is the dimensionality of
1051 your input vectors)
1052 t_quartic
1054 $t = t_quartic(<options>);
1055 Quartic scaling -- cylindrical pincushion (n-d; with inverse)
1057 Quartic scaling is a generalization of t_quadratic to a quartic
1059 expansion. Only even powers of the input coordinates are retained, and
1060 (as with t_quadratic) sign is preserved, making it an odd function
1061 although a true quartic transformation would be an even function.
1062 You can apply separate distortion along any of the principal axes. If
1064 you want different axes, use "t_wrap" and "t_linear" to rotate them to
1065 the correct angle. The scaling options may be scalars or vectors; if
1066 they are scalars then the expansion is isotropic.
1067 The formula for the expansion is:
1069 f(a) = ( <a> + <strength> * a^2/<L_0> ) / (abs(<strength>) + 1)
1071 where <strength> is a scaling coefficient and <L_0> is a fundamental
1073 length scale. Negative values of <strength> result in a pincushion
1074 contraction.
1075 Note that, because quadratic scaling does not have a strict inverse for
1077 coordinate systems that cross the origin, we cheat slightly and use $x
1078 * abs($x) rather than $x**2. This does the Right thing for pincushion
1079 and barrel distortion, but means that t_quadratic does not behave
1080 exactly like t_cubic with a null cubic strength coefficient.
1081 OPTIONS
1083 o,origin,Origin
1085 The origin of the pincushion. (default is the, er, origin).
1086 l,l0,length,Length,r0
1088 The fundamental scale of the transformation -- the radius that
1089 remains unchanged. (default=1)
1090 s,str,strength,Strength
1092 The relative strength of the pincushion. (default = 0.1)
1093 honest (default=0)
1095 Sets whether this is a true quadratic coordinate transform. The
1096 more common form is pincushion or cylindrical distortion, which
1097 switches branches of the square root at the origin (for symmetric
1098 expansion). Setting honest to a non-false value forces true
1099 quadratic behavior, which is not mirror-symmetric about the origin.
1100 d, dim, dims, Dims
1102 The number of dimensions to quadratically scale (default is the
1103 dimensionality of your input vectors)
1104 t_spherical
1106 $t = t_spherical(<options>);
1107 Convert Cartesian to spherical coordinates. (3-D; with inverse)
1109 Convert 3-D Cartesian to spherical (theta, phi, r) coordinates. Theta
1111 is longitude, centered on 0, and phi is latitude, also centered on 0.
1112 Unless you specify Euler angles, the pole points in the +Z direction
1113 and the prime meridian is in the +X direction. The default is for
1114 theta and phi to be in radians; you can select degrees if you want
1115 them.
1116 Just as the "t_radial" 2-D transform acts like a 3-D cylindrical
1118 transform by ignoring third and higher dimensions, Spherical acts like
1119 a hypercylindrical transform in four (or higher) dimensions. Also as
1120 with "t_radial", you must manually specify the origin if you want to
1121 use more dimensions than 3.
1122 To deal with latitude & longitude on the surface of a sphere (rather
1124 than full 3-D coordinates), see t_unit_sphere.
1125 OPTIONS:
1127 o, origin, Origin [default (0,0,0)]
1129 This is the Cartesian origin of the spherical expansion. Pass in a
1130 PDL or an array ref.
1131 e, euler, Euler [default (0,0,0)]
1133 This is a 3-vector containing Euler angles to change the angle of
1134 the pole and ordinate. The first two numbers are the (theta, phi)
1135 angles of the pole in a (+Z,+X) spherical expansion, and the last is
1136 the angle that the new prime meridian makes with the meridian of a
1137 simply tilted sphere. This is implemented by composing the output
1138 transform with a PDL::Transform::Linear object.
1139 u, unit, Unit (default radians)
1141 This option sets the angular unit to be used. Acceptable values are
1142 "degrees","radians", or reasonable substrings thereof (e.g. "deg",
1143 and "rad", but "d" and "r" are deprecated). Once genuine unit
1144 processing comes online (a la Math::Units) any angular unit should
1145 be OK.
1146 t_projective
1148 $t = t_projective(<options>);
1149 Projective transformation
1151 Projective transforms are simple quadratic, quasi-linear
1153 transformations. They are the simplest transformation that can
1154 continuously warp an image plane so that four arbitrarily chosen points
1155 exactly map to four other arbitrarily chosen points. They have the
1156 property that straight lines remain straight after transformation.
1157 You can specify your projective transformation directly in homogeneous
1159 coordinates, or (in 2 dimensions only) as a set of four unique points
1160 that are mapped one to the other by the transformation.
1161 Projective transforms are quasi-linear because they are most easily
1163 described as a linear transformation in homogeneous coordinates (e.g.
1164 (x',y',w) where w is a normalization factor: x = x'/w, etc.). In those
1165 coordinates, an N-D projective transformation is represented as simple
1166 multiplication of an N+1-vector by an N+1 x N+1 matrix, whose lower-
1167 right corner value is 1.
1168 If the bottom row of the matrix consists of all zeroes, then the
1170 transformation reduces to a linear affine transformation (as in
1171 "t_linear").
1172 If the bottom row of the matrix contains nonzero elements, then the
1174 transformed x,y,z,etc. coordinates are related to the original
1175 coordinates by a quadratic polynomial, because the normalization factor
1176 'w' allows a second factor of x,y, and/or z to enter the equations.
1177 OPTIONS:
1179 m, mat, matrix, Matrix
1181 If specified, this is the homogeneous-coordinate matrix to use. It
1182 must be N+1 x N+1, for an N-dimensional transformation.
1183 p, point, points, Points
1185 If specified, this is the set of four points that should be mapped
1186 one to the other. The homogeneous-coordinate matrix is calculated
1187 from them. You should feed in a 2x2x4 PDL, where the 0 dimension
1188 runs over coordinate, the 1 dimension runs between input and output,
1189 and the 2 dimension runs over point. For example, specifying
1190 p=> pdl([ [[0,1],[0,1]], [[5,9],[5,8]], [[9,4],[9,3]], [[0,0],[0,0]] ])
1192 maps the origin and the point (0,1) to themselves, the point (5,9)
1194 to (5,8), and the point (9,4) to (9,3).
1195 This is similar to the behavior of fitwarp2d with a quadratic
1197 polynomial.
1198
1200 Copyright 2002, 2003 Craig DeForest. There is no warranty. You are
1201 allowed to redistribute this software under certain conditions. For
1202 details, see the file COPYING in the PDL distribution. If this file is
1203 separated from the PDL distribution, the copyright notice should be
1204 included in the file.
1205perl v5.34.0 2022-02-28 Transform(3)