1Pamundice User Manual(0)                              Pamundice User Manual(0)
2
3
4

NAME

6       pamundice - combine grid of images (tiles) into one
7
8

EXAMPLE

10           $ pamdice myimage.ppm -outstem=myimage_part -width=10 -height=8
11           $ pamundice myimage_part_%1d_%1a.ppm -across=10 -down=8 >myimage.ppm
12
13           $ pamundice myimage.ppm myimage_part_%2a -across=13 -hoverlap=9
14
15
16

SYNOPSIS

18       pamundice
19
20       [-across=n]
21
22       [-down=n]
23
24       [-hoverlap=pixels]
25
26       [-voverlap=pixels]
27
28       [-verbose]
29
30       input_filename_pattern
31
32       You  can  use  the minimum unique abbreviation of the options.  You can
33       use two hyphens instead of one.  You can separate an option  name  from
34       its value with white space instead of an equals sign.
35
36

DESCRIPTION

38       This program is part of Netpbm(1).
39
40       pamundice  reads a bunch of Netpbm images as input and combines them as
41       a grid of tiles into a single output image of the same kind on Standard
42       Output.
43
44       You can optionally make the pieces overlap.
45
46       See  the  input_filename_pattern  argument for information on naming of
47       the input files.
48
49       The input images must all have the same format (PAM,  PPM,  etc.)   and
50       maxval  and  for  PAM must have the same depth and tuple type.  All the
51       images in a rank (horizontal row of tiles) must have the  same  height.
52       All  the images in a file (vertical column of tiles) must have the same
53       width.  But it is not required that every rank have the same height  or
54       every file have the same width.
55
56       pamdice is the inverse of pamundice.  You can use pamundice to reassem‐
57       ble an image sliced up by pamdice.  You can use pamdice to recreate the
58       tiles  of  an  image  created by pamundice, but to do this the original
59       ranks must all have been the same height except for the bottom one  and
60       the  original  files must all have been the same width except the right
61       one.
62
63       One use for this is to make pieces that take  less  computer  resources
64       than  the whole image to process.  For example, you might have an image
65       so large that an image editor can't read it all  into  memory  or  pro‐
66       cesses  it  very  slowly.   You  can  split it into smaller pieces with
67       pamdice, edit one at a time, and then reassemble them with pamundice.
68
69       An alternative to join images in a single direction (i.e. a single rank
70       or  a  single  file) is pnmcat.  pnmcat gives you more flexibility than
71       pamundice in identifying the input images: you can supply them on Stan‐
72       dard Input or as a list of arbitrarily named files.
73
74       To  join  piecewise  photographs,  use  pnmstitch instead of pamundice,
75       because it figures out where the pieces overlap,  even  if  they  don't
76       overlap exactly vertically or horizontally.
77
78       To create an image of the same tile repeated in a grid, that's pnmtile.
79
80       pnmindex  does  a  similar  thing  to pamundice: it combines a bunch of
81       small images in a grid into a big one.  But its purpose is to produce a
82       an  index  image  of the input images.  So it leaves space between them
83       and has labels for them, for example.
84
85

ARGUMENTS

87       There is one non-option argument,  and  it  is  mandatory:  input_file‐
88       name_pattern.  This tells pamundice what files contain the input tiles.
89
90       pamundice reads the input images from files which are named with a pat‐
91       tern that indicates their positions in the combined image.   For  exam‐
92       ple,  tile_00_05.ppm  could be the 6th tile over in the 1st rank, while
93       tile_04_01 is the 2nd tile over in the 5th rank.
94
95       You cannot supply any of the data on Standard Input, and the files must
96       be the kind that pamundice can close and reopen and read the same image
97       a second time (e.g. a regular file is fine; a named  pipe  is  probably
98       not).
99
100       input_filename_pattern  is a printf-style pattern.  (See the standard C
101       library printf  subroutine).   For  the  example  above,  it  would  be
102       tile_%2d_%2a.ppm.  The only possible conversion specifiers are:
103
104
105
106
107       d      "down": The rank (row) number, starting with 0.
108
109
110       a      "across": The file (column) number, starting with 0.
111
112
113       %      The per cent character (%).
114
115
116
117       The  number between the % and the conversion specifier is the precision
118       and is required.  It says how many characters  of  the  file  name  are
119       described  by  that conversion.  The rank or file number is filled with
120       leading zeroes as necessary.
121
122       So the example tile_%2d_%2a.ppm means to get the name of the file  that
123       contains the tile at Rank 0, File 5, you:
124
125
126
127
128       ·      replace  the  "%2d"  with  the rank number, as a 2 digit decimal
129              number: "00"
130
131
132       ·      Replace the "%2a" with the file number, as  a  2  digit  decimal
133              number: "05"
134
135
136       Note  that  this  pattern  describes  file names that pamdice produces,
137       except that the precision may be more or less.  (pamdice  uses  however
138       many digits are required for the highest numbered image).
139
140
141

OPTIONS

143       -across=N
144              This  is the number of tiles across in the grid, i.e. the number
145              of tiles in each rank, or the number of files.
146
147              Default is 1.
148
149
150
151       -down=N
152              This is the number of tiles up and down in the  grid,  i.e.  the
153              number of tiles in each file, or the number of ranks.
154
155              Default is 1.
156
157
158       -hoverlap=pixels
159              This  is the amount in pixels to overlap the tiles horizontally.
160              pamundice clips this much off  the  right  edge  of  every  tile
161              before joining it to the adjacent image to the right.  The tiles
162              along the right edge remain whole.
163
164              There must not be any input image narrower than this.
165
166              Note that this undoes the effect of the same -hoverlap option of
167              pamdice.
168
169              Default is zero -- no overlap.
170
171
172       -voverlap=pixels
173              This  is  analogous to -hoverlap, but pamundice clips the bottom
174              edge of each image before joining it to the one below.
175
176
177       -verbose
178              Print information about the processing to Standard Error.
179
180
181
182

HISTORY

184       pamundice was new in Netpbm 10.39 (June 2007).  Before that, pnmcat  is
185       the best substitute.
186
187
188

SEE ALSO

190       pamdice(1), pnmcat(1), pnmindex(1), pnmtile(1), pnm(1) pam(1)
191

DOCUMENT SOURCE

193       This  manual  page was generated by the Netpbm tool 'makeman' from HTML
194       source.  The master documentation is at
195
196              http://netpbm.sourceforge.net/doc/pamundice.html
197
198netpbm documentation             1 April 2007         Pamundice User Manual(0)
Impressum