1dcmdjpeg(1) OFFIS DCMTK dcmdjpeg(1)
2
6 dcmdjpeg - Decode JPEG-compressed DICOM file
7
10 dcmdjpeg [options] dcmfile-in dcmfile-out
11
13 The dcmdjpeg utility reads a JPEG-compressed DICOM image (dcmfile-in),
14 decompresses the JPEG data (i. e. conversion to a native DICOM transfer
15 syntax) and writes the converted image to an output file (dcmfile-out).
16
18 dcmfile-in DICOM input filename to be converted
19 dcmfile-out DICOM output filename
21
23 general options
24 -h --help
25 print this help text and exit
26 --version
28 print version information and exit
29 --arguments
31 print expanded command line arguments
32 -q --quiet
34 quiet mode, print no warnings and errors
35 -v --verbose
37 verbose mode, print processing details
38 -d --debug
40 debug mode, print debug information
41 -ll --log-level [l]evel: string constant
43 (fatal, error, warn, info, debug, trace)
44 use level l for the logger
45 -lc --log-config [f]ilename: string
47 use config file f for the logger
48 input options
50 input file format:
51 +f --read-file
53 read file format or data set (default)
54 +fo --read-file-only
56 read file format only
57 -f --read-dataset
59 read data set without file meta information
60 # This option allows one to decompress JPEG compressed DICOM objects that
62 # have been stored as dataset without meta-header. Such a thing should
63 # not exist since the transfer syntax cannot be reliably determined,
64 # without meta-header but unfortunately it does.
65 processing options
67 color space conversion:
68 +cp --conv-photometric
70 convert if YCbCr photometric interpretation (default)
71 # If the compressed image uses YBR_FULL or YBR_FULL_422 photometric
73 # interpretation, convert to RGB during decompression.
74 +cl --conv-lossy
76 convert YCbCr to RGB if lossy JPEG
77 # If the compressed image is encoded in lossy JPEG, assume YCbCr
79 # color model and convert to RGB.
80 +cg --conv-guess
82 convert to RGB if YCbCr is guessed by library
83 # If the underlying JPEG library "guesses" the color space of the
85 # compressed image to be YCbCr, convert to RGB.
86 +cgl --conv-guess-lossy
88 convert to RGB if lossy JPEG and YCbCr is
89 guessed by the underlying JPEG library
90 # If the compressed image is encoded in lossy JPEG and the underlying
92 # JPEG library "guesses" the color space to be YCbCr, convert to RGB.
93 +ca --conv-always
95 always convert YCbCr to RGB
96 # If the compressed image is a color image, assume YCbCr color model
98 # and convert to RGB.
99 +cn --conv-never
101 never convert color space
102 # Never convert color space during decompression.
104 planar configuration:
106 +pa --planar-auto
108 automatically determine planar configuration
109 from SOP class and color space (default)
110 # If the compressed image is a color image, store in color-by-plane
112 # planar configuration if required by the SOP class and photometric
113 # interpretation. Hardcopy Color images are always stored color-by-
114 # plane, and the revised Ultrasound image objects are stored color-by-
115 # plane if the color model is YBR_FULL. Everything else is stored
116 # color-by-pixel.
117 +px --color-by-pixel
119 always store color-by-pixel
120 # If the compressed image is a color image, store in color-by-pixel
122 # planar configuration.
123 +pl --color-by-plane
125 always store color-by-plane
126 # If the compressed image is a color image, store in color-by-plane
128 # planar configuration.
129 SOP Instance UID:
131 +ud --uid-default
133 keep same SOP Instance UID (default)
134 # Never assigns a new SOP instance UID.
136 +ua --uid-always
138 always assign new UID
139 # Always assigns a new SOP instance UID.
141 workaround options for incorrect JPEG encodings:
143 +w6 --workaround-pred6
145 enable workaround for JPEG lossless images
146 with overflow in predictor 6
147 # DICOM images with 16 bits/pixel have been observed "in the wild"
149 # that are compressed with lossless JPEG and need special handling
150 # because the encoder produced an 16-bit integer overflow in predictor
151 # 6, which needs to be compensated (reproduced) during decompression.
152 # This flag enables a correct decompression of such faulty images, but
153 # at the same time will cause an incorrect decompression of correctly
154 # compressed images. Use with care.
155 +wi --workaround-incpl
157 enable workaround for incomplete JPEG data
158 # This option causes dcmjpeg to ignore incomplete JPEG data
160 # at the end of a compressed fragment and to start decompressing
161 # the next frame from the next fragment (if any). This permits
162 # images with incomplete JPEG data to be decoded..fi
163 output options
165 output file format:
166 +F --write-file
168 write file format (default)
169 -F --write-dataset
171 write data set without file meta information
172 output transfer syntax:
174 +te --write-xfer-little
176 write with explicit VR little endian (default)
177 +tb --write-xfer-big
179 write with explicit VR big endian TS
180 +ti --write-xfer-implicit
182 write with implicit VR little endian TS
183 post-1993 value representations:
185 +u --enable-new-vr
187 enable support for new VRs (UN/UT) (default)
188 -u --disable-new-vr
190 disable support for new VRs, convert to OB
191 group length encoding:
193 +g= --group-length-recalc
195 recalculate group lengths if present (default)
196 +g --group-length-create
198 always write with group length elements
199 -g --group-length-remove
201 always write without group length elements
202 length encoding in sequences and items:
204 +e --length-explicit
206 write with explicit lengths (default)
207 -e --length-undefined
209 write with undefined lengths
210 data set trailing padding (not with --write-dataset):
212 -p= --padding-retain
214 do not change padding (default if not --write-dataset)
215 -p --padding-off
217 no padding (implicit if --write-dataset)
218 +p --padding-create [f]ile-pad [i]tem-pad: integer
220 align file on multiple of f bytes
221 and items on multiple of i bytes
222
224 dcmdjpeg supports the following transfer syntaxes for input (dcmfile-
225 in):
226 LittleEndianImplicitTransferSyntax 1.2.840.10008.1.2
228 LittleEndianExplicitTransferSyntax 1.2.840.10008.1.2.1
229 DeflatedExplicitVRLittleEndianTransferSyntax 1.2.840.10008.1.2.1.99 (*)
230 BigEndianExplicitTransferSyntax 1.2.840.10008.1.2.2
231 JPEGProcess1TransferSyntax 1.2.840.10008.1.2.4.50
232 JPEGProcess2_4TransferSyntax 1.2.840.10008.1.2.4.51
233 JPEGProcess6_8TransferSyntax 1.2.840.10008.1.2.4.53
234 JPEGProcess10_12TransferSyntax 1.2.840.10008.1.2.4.55
235 JPEGProcess14TransferSyntax 1.2.840.10008.1.2.4.57
236 JPEGProcess14SV1TransferSyntax 1.2.840.10008.1.2.4.70
237 (*) if compiled with zlib support enabled
239 dcmdjpeg supports the following transfer syntaxes for output (dcmfile-
241 out):
242 LittleEndianImplicitTransferSyntax 1.2.840.10008.1.2
244 LittleEndianExplicitTransferSyntax 1.2.840.10008.1.2.1
245 BigEndianExplicitTransferSyntax 1.2.840.10008.1.2.2
246
248 The level of logging output of the various command line tools and
249 underlying libraries can be specified by the user. By default, only
250 errors and warnings are written to the standard error stream. Using
251 option --verbose also informational messages like processing details
252 are reported. Option --debug can be used to get more details on the
253 internal activity, e.g. for debugging purposes. Other logging levels
254 can be selected using option --log-level. In --quiet mode only fatal
255 errors are reported. In such very severe error events, the application
256 will usually terminate. For more details on the different logging
257 levels, see documentation of module 'oflog'.
258 In case the logging output should be written to file (optionally with
260 logfile rotation), to syslog (Unix) or the event log (Windows) option
261 --log-config can be used. This configuration file also allows for
262 directing only certain messages to a particular output stream and for
263 filtering certain messages based on the module or application where
264 they are generated. An example configuration file is provided in
265 <etcdir>/logger.cfg.
266
268 All command line tools use the following notation for parameters:
269 square brackets enclose optional values (0-1), three trailing dots
270 indicate that multiple values are allowed (1-n), a combination of both
271 means 0 to n values.
272 Command line options are distinguished from parameters by a leading '+'
274 or '-' sign, respectively. Usually, order and position of command line
275 options are arbitrary (i.e. they can appear anywhere). However, if
276 options are mutually exclusive the rightmost appearance is used. This
277 behavior conforms to the standard evaluation rules of common Unix
278 shells.
279 In addition, one or more command files can be specified using an '@'
281 sign as a prefix to the filename (e.g. @command.txt). Such a command
282 argument is replaced by the content of the corresponding text file
283 (multiple whitespaces are treated as a single separator unless they
284 appear between two quotation marks) prior to any further evaluation.
285 Please note that a command file cannot contain another command file.
286 This simple but effective approach allows one to summarize common
287 combinations of options/parameters and avoids longish and confusing
288 command lines (an example is provided in file <datadir>/dumppat.txt).
289
291 The dcmdjpeg utility will attempt to load DICOM data dictionaries
292 specified in the DCMDICTPATH environment variable. By default, i.e. if
293 the DCMDICTPATH environment variable is not set, the file
294 <datadir>/dicom.dic will be loaded unless the dictionary is built into
295 the application (default for Windows).
296 The default behavior should be preferred and the DCMDICTPATH
298 environment variable only used when alternative data dictionaries are
299 required. The DCMDICTPATH environment variable has the same format as
300 the Unix shell PATH variable in that a colon (':') separates entries.
301 On Windows systems, a semicolon (';') is used as a separator. The data
302 dictionary code will attempt to load each file specified in the
303 DCMDICTPATH environment variable. It is an error if no data dictionary
304 can be loaded.
305
307 dcmcjpeg(1)
308
310 Copyright (C) 2001-2016 by OFFIS e.V., Escherweg 2, 26121 Oldenburg,
311 Germany.
312Version 3.6.2 Fri Jul 14 2017 dcmdjpeg(1)