Debian Codegraph @

upstream/debian-unstable/man1/pamtopfm.1

raw
1 \
2 .\" This man page was generated by the Netpbm tool 'makeman' from HTML source.
3 .\" Do not hand-hack it! If you have bug fixes or improvements, please find
4 .\" the corresponding HTML page on the Netpbm website, generate a patch
5 .\" against that, and send it to the Netpbm maintainer.
6 .TH "Pamtopfm User Manual" 1 "10 April 2004" "netpbm documentation"
7
8 .SH NAME
9 pamtopfm - Convert Netpbm image to PFM (Portable Float Map)
10
11 .UN synopsis
12 .SH SYNOPSIS
13 \fBpamtopfm\fP
14 [\fB-endian=\fP{\fBbig\fP|\fBlittle\fP}]
15 [\fB-scale=\fP\fIfloat\fP]
16 [\fIimagefile\fP]
17 .PP
18 All options can be abbreviated to their shortest unique prefix.
19 You may use two hyphens instead of one. You may separate an option
20 name and its value with white space instead of an equals sign.
21
22 .UN description
23 .SH DESCRIPTION
24 .PP
25 This program is part of
26 .BR "Netpbm" (1)\c
27 \&.
28 .PP
29 \fBpamtopfm\fP reads a Netpbm image (PNM or PAM) and converts it
30 to a PFM (Portable Float Map) image.
31 .PP
32 The PFM (Portable Float Map) image format is a lot like PPM, but uses
33 floating point numbers with no maxval to achieve a High Dynamic Range
34 (HDR) format. That means it doesn't have a concept of absolute color
35 and it can represent generic light intensity information rather than
36 just visual information like PPM does. For example, two pixels that
37 are so close in intensity that the human eye cannot tell them apart
38 are not visually distinct, so a visual image format such as PPM would
39 have no reason to use different sample values for them. But an HDR format
40 would.
41 .PP
42 There are details of the PFM format in the
43 .BR "PFM
44 Format Description" (1)\c
45 \&.
46 .PP
47 .UR https://vgl.ict.usc.edu/HDRShop/
48 USC's HDRShop program
49 .UE
50 \& and a program called Lefty use it.
51
52 \fBpamtopfm\fP creates a color PFM image if its input is RGB (PPM)
53 and a non-color PFM otherwise.
54 .PP
55 Use
56 .BR "\fBpfmtopam\fP" (1)\c
57 \& to convert a PFM
58 image to Netpbm format.
59
60
61 .UN options
62 .SH OPTIONS
63 .PP
64 In addition to the options common to all programs based on libnetpbm
65 (most notably \fB-quiet\fP, see
66 .UR index.html#commonoptions
67 Common Options
68 .UE
69 \&), \fBpamtopfm\fP recognizes the following
70 command line options:
71
72
73 .TP
74 \fB-scale=\fP\fIfloat\fP
75 .sp
76 This specifies the scale factor of the PFM image.
77 Scale factor is a component of the PFM format.
78 Default is 1.0.
79
80 .TP
81 \fB-endian=\fP{\fBbig\fP|\fBlittle\fP}
82 .sp
83 This specifies the endianness of the PFM image. The samples
84 in the raster of a PFM image are 4 byte IEEE floating point
85 numbers. A parameter of the IEEE format, and therefore the PFM
86 format, is endianness, i.e. whether the specified bytes are
87 ordered from low addresses to high addresses or vice versa.
88 .sp
89 \fBbig\fP means big endian -- the natural ordering;
90 \fBlittle\fP means little-endian, the Intel-friendly ordering.
91 .sp
92 Default is whichever endianness the machine on which \fBpamtopfm\fP
93 runs uses internally, which results in the faster execution.
94
95
96
97 .UN seealso
98 .SH SEE ALSO
99 .BR "Netpbm" (1)\c
100 \&,
101 .BR "pfmtopam" (1)\c
102 \&,
103 .BR "pam" (1)\c
104 \&
105
106 .UN history
107 .SH HISTORY
108 .PP
109 \fBpamtopfm\fP was added to Netpbm in Release 10.22 (April 2004).
110 .SH DOCUMENT SOURCE
111 This manual page was generated by the Netpbm tool 'makeman' from HTML
112 source. The master documentation is at
113 .IP
114 .B http://netpbm.sourceforge.net/doc/pamtopfm.html
115 .PP