1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
|
.TH "dcmmklut" 1 "Fri Apr 22 2022" "Version 3.6.7" "OFFIS DCMTK" \" -*- nroff -*-
.nh
.SH NAME
dcmmklut \- Create DICOM look-up tables
.SH "SYNOPSIS"
.PP
.PP
.nf
dcmmklut [options] dcmimg-out
.fi
.PP
.SH "DESCRIPTION"
.PP
The \fBdcmmklut\fP utility allows one to create a variety of DICOM Modality, Presentation and VOI look-up tables (LUT) and is intended for the creation of test images\&. The utility is able to read an existing DICOM image file, create a look up table according to the command line options, and write the new object back to file\&. It is also possible to create a new object containing the specified LUT without reading an existing DICOM image file\&. This is e\&.g\&. useful to simply store different look-up tables in a DICOM-like structure\&. As a default the output file is encoded with the same transfer syntax used for the input file, but the transfer syntax can also be specified as a command line option\&.
.PP
The LUT data can be derived from the shape of a gamma curve (default for the gamma factor is 1) or imported from a file (currently the MAP format from Ulead's PhotoImpact and a simple text format are supported)\&. The input and output width of the LUT can also be specified in the range allowed by the DICOM standard\&. The interpolation of the input range is done by a polynomial curve fitting algorithm\&.
.PP
In addition to the DICOM output file the LUT data can also be exported to a tabbed text file which allows the easy visualization of the curves with a common spread sheet application (e\&.g\&. Microsoft Excel)\&.
.SH "PARAMETERS"
.PP
.PP
.nf
dcmimg-out DICOM output filename
.fi
.PP
.SH "OPTIONS"
.PP
.SS "general options"
.PP
.nf
-h --help
print this help text and exit
--version
print version information and exit
--arguments
print expanded command line arguments
-q --quiet
quiet mode, print no warnings and errors
-v --verbose
verbose mode, print processing details
-d --debug
debug mode, print debug information
-ll --log-level [l]evel: string constant
(fatal, error, warn, info, debug, trace)
use level l for the logger
-lc --log-config [f]ilename: string
use config file f for the logger
.fi
.PP
.SS "LUT creation options"
.PP
.nf
LUT type:
+Tm --modality
create as Modality LUT
+Tp --presentation
create as Presentation LUT
+Tv --voi
create as VOI LUT (default)
LUT placement:
+Pa --add
add to existing transform
(default for and only with --voi)
+Pr --replace
replace existing transform
(default for --modality and --presentation)
LUT content:
+Cg --gamma [g]amma: float
use gamma value (default: 1.0)
+Cm --map-file [f]ilename: string
read input data from MAP file
+Ct --text-file [f]ilename: string
read input data from text file
LUT options:
+Og --inverse-gsdf
apply inverse GSDF (print presentation LUT in OD)
--min-density [v]alue: integer (0..65535, default: 20)
set min density to v (in hundreds of OD)
--max-density [v]alue: integer (0..65535, default: 300)
set max density to v (in hundreds of OD)
+Oi --illumination [v]alue: integer (0..65535, default: 2000)
set illumination to v (in cd/m^2)
+Or --reflection [v]alue: integer (0..65535, default: 10)
set reflected ambient light to v (in cd/m^2)
LUT structure:
-b --bits [n]umber: integer
create LUT with n bit values (8..16, default: 16)
-e --entries [n]umber: integer
create LUT with n entries (1..65536, default: 256)
-f --first-mapped [n]umber: integer
first input value mapped (-31768..65535, default: 0)
-r --random [n]umber: unsigned integer
perform n randomly selected permutations on the LUT
-rs --random-seed [n]umber: unsigned integer
initialize the random-number generator with n
(default: 0, for reproducible results)
-o --order [n]umber: integer
use polynomial curve fitting algorithm with order n
(0..99, default: 5)
-E --explanation [n]ame: string
LUT explanation (default: automatically created)
LUT data alignment:
-a --byte-align
create byte-aligned LUT
(default for and only with 8 bit values)
+a --word-align
create word-aligned LUT
(default for 9-16 bit values)
LUT data VR:
+Dw --data-ow
write LUT Data as OW (default)
+Du --data-us
write LUT Data as US
+Ds --data-ss
write LUT Data as SS (minimal support)
.fi
.PP
.SS "file options"
.PP
.nf
+Fi --dicom-input [f]ilename: string
read dataset from DICOM file f
+Fo --text-output [f]ilename: string
write LUT data to tabbed text file f
.fi
.PP
.SH "NOTES"
.PP
Please check the DICOM standard for further restrictions on the look-up table structure\&. Especially the number of bits per table entry might be restricted in particular IODs\&.
.SH "LOGGING"
.PP
The level of logging output of the various command line tools and underlying libraries can be specified by the user\&. By default, only errors and warnings are written to the standard error stream\&. Using option \fI--verbose\fP also informational messages like processing details are reported\&. Option \fI--debug\fP can be used to get more details on the internal activity, e\&.g\&. for debugging purposes\&. Other logging levels can be selected using option \fI--log-level\fP\&. In \fI--quiet\fP mode only fatal errors are reported\&. In such very severe error events, the application will usually terminate\&. For more details on the different logging levels, see documentation of module 'oflog'\&.
.PP
In case the logging output should be written to file (optionally with logfile rotation), to syslog (Unix) or the event log (Windows) option \fI--log-config\fP can be used\&. This configuration file also allows for directing only certain messages to a particular output stream and for filtering certain messages based on the module or application where they are generated\&. An example configuration file is provided in \fI<etcdir>/logger\&.cfg\fP\&.
.SH "COMMAND LINE"
.PP
All command line tools use the following notation for parameters: square brackets enclose optional values (0-1), three trailing dots indicate that multiple values are allowed (1-n), a combination of both means 0 to n values\&.
.PP
Command line options are distinguished from parameters by a leading '+' or '-' sign, respectively\&. Usually, order and position of command line options are arbitrary (i\&.e\&. they can appear anywhere)\&. However, if options are mutually exclusive the rightmost appearance is used\&. This behavior conforms to the standard evaluation rules of common Unix shells\&.
.PP
In addition, one or more command files can be specified using an '@' sign as a prefix to the filename (e\&.g\&. \fI@command\&.txt\fP)\&. Such a command argument is replaced by the content of the corresponding text file (multiple whitespaces are treated as a single separator unless they appear between two quotation marks) prior to any further evaluation\&. Please note that a command file cannot contain another command file\&. This simple but effective approach allows one to summarize common combinations of options/parameters and avoids longish and confusing command lines (an example is provided in file \fI<datadir>/dumppat\&.txt\fP)\&.
.SH "ENVIRONMENT"
.PP
The \fBdcmmklut\fP utility will attempt to load DICOM data dictionaries specified in the \fIDCMDICTPATH\fP environment variable\&. By default, i\&.e\&. if the \fIDCMDICTPATH\fP environment variable is not set, the file \fI<datadir>/dicom\&.dic\fP will be loaded unless the dictionary is built into the application (default for Windows)\&.
.PP
The default behavior should be preferred and the \fIDCMDICTPATH\fP environment variable only used when alternative data dictionaries are required\&. The \fIDCMDICTPATH\fP environment variable has the same format as the Unix shell \fIPATH\fP variable in that a colon (':') separates entries\&. On Windows systems, a semicolon (';') is used as a separator\&. The data dictionary code will attempt to load each file specified in the \fIDCMDICTPATH\fP environment variable\&. It is an error if no data dictionary can be loaded\&.
.SH "FILES"
.PP
\fI<datadir>/philips\&.lut\fP - sample LUT in text format
.SH "COPYRIGHT"
.PP
Copyright (C) 1998-2022 by OFFIS e\&.V\&., Escherweg 2, 26121 Oldenburg, Germany\&.
|
