1dcmdjpeg(1) OFFIS DCMTK dcmdjpeg(1)
2
6 dcmdjpeg - Decode JPEG-compressed DICOM file
7
9 dcmdjpeg [options] dcmfile-in dcmfile-out
10
12 The dcmdjpeg utility reads a JPEG-compressed DICOM image (dcmfile-in),
13 decompresses the JPEG data (i. e. conversion to a native DICOM transfer
14 syntax) and writes the converted image to an output file (dcmfile-out).
15
17 dcmfile-in DICOM input filename to be converted
18 dcmfile-out DICOM output filename
20
22 general options
23 -h --help
24 print this help text and exit
25 --version
27 print version information and exit
28 --arguments
30 print expanded command line arguments
31 -q --quiet
33 quiet mode, print no warnings and errors
34 -v --verbose
36 verbose mode, print processing details
37 -d --debug
39 debug mode, print debug information
40 -ll --log-level [l]evel: string constant
42 (fatal, error, warn, info, debug, trace)
43 use level l for the logger
44 -lc --log-config [f]ilename: string
46 use config file f for the logger
47 input options
49 input file format:
50 +f --read-file
52 read file format or data set (default)
53 +fo --read-file-only
55 read file format only
56 -f --read-dataset
58 read data set without file meta information
59 # This option allows to decompress JPEG compressed DICOM objects that
61 # have been stored as dataset without meta-header. Such a thing should
62 # not exist since the transfer syntax cannot be reliably determined,
63 # without meta-header but unfortunately it does.
64 processing options
66 color space conversion:
67 +cp --conv-photometric
69 convert if YCbCr photometric interpretation (default)
70 # If the compressed image uses YBR_FULL or YBR_FULL_422 photometric
72 # interpretation, convert to RGB during decompression.
73 +cl --conv-lossy
75 convert YCbCr to RGB if lossy JPEG
76 # If the compressed image is encoded in lossy JPEG, assume YCbCr
78 # color model and convert to RGB.
79 +cg --conv-guess
81 convert to RGB if YCbCr is guessed by library
82 # If the underlying JPEG library "guesses" the color space of the
84 # compressed image to be YCbCr, convert to RGB.
85 +cgl --conv-guess-lossy
87 convert to RGB if lossy JPEG and YCbCr is
88 guessed by the underlying JPEG library
89 # If the compressed image is encoded in lossy JPEG and the underlying
91 # JPEG library "guesses" the color space to be YCbCr, convert to RGB.
92 +ca --conv-always
94 always convert YCbCr to RGB
95 # If the compressed image is a color image, assume YCbCr color model
97 # and convert to RGB.
98 +cn --conv-never
100 never convert color space
101 # Never convert color space during decompression.
103 planar configuration:
105 +pa --planar-auto
107 automatically determine planar configuration
108 from SOP class and color space (default)
109 # If the compressed image is a color image, store in color-by-plane
111 # planar configuration if required by the SOP class and photometric
112 # interpretation. Hardcopy Color images are always stored color-by-
113 # plane, and the revised Ultrasound image objects are stored color-by-
114 # plane if the color model is YBR_FULL. Everything else is stored
115 # color-by-pixel.
116 +px --color-by-pixel
118 always store color-by-pixel
119 # If the compressed image is a color image, store in color-by-pixel
121 # planar configuration.
122 +pl --color-by-plane
124 always store color-by-plane
125 # If the compressed image is a color image, store in color-by-plane
127 # planar configuration.
128 SOP Instance UID:
130 +ud --uid-default
132 keep same SOP Instance UID (default)
133 # Never assigns a new SOP instance UID.
135 +ua --uid-always
137 always assign new UID
138 # Always assigns a new SOP instance UID.
140 workaround options for incorrect JPEG encodings:
142 +w6 --workaround-pred6
144 enable workaround for JPEG lossless images
145 with overflow in predictor 6
146 # DICOM images with 16 bits/pixel have been observed "in the wild"
148 # that are compressed with lossless JPEG and need special handling
149 # because the encoder produced an 16-bit integer overflow in predictor
150 # 6, which needs to be compensated (reproduced) during decompression.
151 # This flag enables a correct decompression of such faulty images, but
152 # at the same time will cause an incorrect decompression of correctly
153 # compressed images. Use with care.
154 output options
156 output file format:
157 +F --write-file
159 write file format (default)
160 -F --write-dataset
162 write data set without file meta information
163 output transfer syntax:
165 +te --write-xfer-little
167 write with explicit VR little endian (default)
168 +tb --write-xfer-big
170 write with explicit VR big endian TS
171 +ti --write-xfer-implicit
173 write with implicit VR little endian TS
174 post-1993 value representations:
176 +u --enable-new-vr
178 enable support for new VRs (UN/UT) (default)
179 -u --disable-new-vr
181 disable support for new VRs, convert to OB
182 group length encoding:
184 +g= --group-length-recalc
186 recalculate group lengths if present (default)
187 +g --group-length-create
189 always write with group length elements
190 -g --group-length-remove
192 always write without group length elements
193 length encoding in sequences and items:
195 +e --length-explicit
197 write with explicit lengths (default)
198 -e --length-undefined
200 write with undefined lengths
201 data set trailing padding (not with --write-dataset):
203 -p= --padding-retain
205 do not change padding (default if not --write-dataset)
206 -p --padding-off
208 no padding (implicit if --write-dataset)
209 +p --padding-create [f]ile-pad [i]tem-pad: integer
211 align file on multiple of f bytes
212 and items on multiple of i bytes
213
215 dcmdjpeg supports the following transfer syntaxes for input (dcmfile-
216 in):
217 LittleEndianImplicitTransferSyntax 1.2.840.10008.1.2
219 LittleEndianExplicitTransferSyntax 1.2.840.10008.1.2.1
220 DeflatedExplicitVRLittleEndianTransferSyntax 1.2.840.10008.1.2.1.99 (*)
221 BigEndianExplicitTransferSyntax 1.2.840.10008.1.2.2
222 JPEGProcess1TransferSyntax 1.2.840.10008.1.2.4.50
223 JPEGProcess2_4TransferSyntax 1.2.840.10008.1.2.4.51
224 JPEGProcess6_8TransferSyntax 1.2.840.10008.1.2.4.53
225 JPEGProcess10_12TransferSyntax 1.2.840.10008.1.2.4.55
226 JPEGProcess14TransferSyntax 1.2.840.10008.1.2.4.57
227 JPEGProcess14SV1TransferSyntax 1.2.840.10008.1.2.4.70
228 (*) if compiled with zlib support enabled
230 dcmdjpeg supports the following transfer syntaxes for output (dcmfile-
232 out):
233 LittleEndianImplicitTransferSyntax 1.2.840.10008.1.2
235 LittleEndianExplicitTransferSyntax 1.2.840.10008.1.2.1
236 BigEndianExplicitTransferSyntax 1.2.840.10008.1.2.2
237
239 The level of logging output of the various command line tools and
240 underlying libraries can be specified by the user. By default, only
241 errors and warnings are written to the standard error stream. Using
242 option --verbose also informational messages like processing details
243 are reported. Option --debug can be used to get more details on the
244 internal activity, e.g. for debugging purposes. Other logging levels
245 can be selected using option --log-level. In --quiet mode only fatal
246 errors are reported. In such very severe error events, the application
247 will usually terminate. For more details on the different logging
248 levels, see documentation of module 'oflog'.
249 In case the logging output should be written to file (optionally with
251 logfile rotation), to syslog (Unix) or the event log (Windows) option
252 --log-config can be used. This configuration file also allows for
253 directing only certain messages to a particular output stream and for
254 filtering certain messages based on the module or application where
255 they are generated. An example configuration file is provided in
256 <etcdir>/logger.cfg).
257
259 All command line tools use the following notation for parameters:
260 square brackets enclose optional values (0-1), three trailing dots
261 indicate that multiple values are allowed (1-n), a combination of both
262 means 0 to n values.
263 Command line options are distinguished from parameters by a leading '+'
265 or '-' sign, respectively. Usually, order and position of command line
266 options are arbitrary (i.e. they can appear anywhere). However, if
267 options are mutually exclusive the rightmost appearance is used. This
268 behaviour conforms to the standard evaluation rules of common Unix
269 shells.
270 In addition, one or more command files can be specified using an '@'
272 sign as a prefix to the filename (e.g. @command.txt). Such a command
273 argument is replaced by the content of the corresponding text file
274 (multiple whitespaces are treated as a single separator unless they
275 appear between two quotation marks) prior to any further evaluation.
276 Please note that a command file cannot contain another command file.
277 This simple but effective approach allows to summarize common
278 combinations of options/parameters and avoids longish and confusing
279 command lines (an example is provided in file <datadir>/dumppat.txt).
280
282 The dcmdjpeg utility will attempt to load DICOM data dictionaries
283 specified in the DCMDICTPATH environment variable. By default, i.e. if
284 the DCMDICTPATH environment variable is not set, the file
285 <datadir>/dicom.dic will be loaded unless the dictionary is built into
286 the application (default for Windows).
287 The default behaviour should be preferred and the DCMDICTPATH
289 environment variable only used when alternative data dictionaries are
290 required. The DCMDICTPATH environment variable has the same format as
291 the Unix shell PATH variable in that a colon (':') separates entries.
292 On Windows systems, a semicolon (';') is used as a separator. The data
293 dictionary code will attempt to load each file specified in the
294 DCMDICTPATH environment variable. It is an error if no data dictionary
295 can be loaded.
296
298 dcmcjpeg(1)
299
301 Copyright (C) 2001-2010 by OFFIS e.V., Escherweg 2, 26121 Oldenburg,
302 Germany.
303Version 3.6.0 6 Jan 2011 dcmdjpeg(1)