1dcmdjpls(1) OFFIS DCMTK dcmdjpls(1)
2
6 dcmdjpls - Decode JPEG-LS compressed DICOM file
7
10 dcmdjpls [options] dcmfile-in dcmfile-out
11
13 The dcmdjpls utility reads a JPEG-ls compressed DICOM image (dcmfile-
14 in), decompresses the JPEG-LS data (i. e. conversion to a native DICOM
15 transfer syntax) and writes the converted image to an output file
16 (dcmfile-out).
17
19 dcmfile-in DICOM input filename to be converted
20 dcmfile-out DICOM output filename
22
24 general options
25 -h --help
26 print this help text and exit
27 --version
29 print version information and exit
30 --arguments
32 print expanded command line arguments
33 -q --quiet
35 quiet mode, print no warnings and errors
36 -v --verbose
38 verbose mode, print processing details
39 -d --debug
41 debug mode, print debug information
42 -ll --log-level [l]evel: string constant
44 (fatal, error, warn, info, debug, trace)
45 use level l for the logger
46 -lc --log-config [f]ilename: string
48 use config file f for the logger
49 input options
51 input file format:
52 +f --read-file
54 read file format or data set (default)
55 +fo --read-file-only
57 read file format only
58 -f --read-dataset
60 read data set without file meta information
61 # This option allows one to decompress JPEG-LS compressed DICOM objects that have
63 # been stored as dataset without meta-header. Such a thing should not exist
64 # since the transfer syntax cannot be reliably determined without meta-header,
65 # but unfortunately it does.
66 processing options
68 planar configuration:
69 +pr --planar-restore
71 restore original planar configuration (default)
72 # If the compressed image is a color image, restore the planar
74 # configuration as described in the Planar Configuration attribute.
75 +pa --planar-auto
77 automatically determine planar configuration
78 from SOP class and color space
79 # If the compressed image is a color image, store in color-by-plane
81 # planar configuration if required by the SOP class and photometric
82 # interpretation. Hardcopy Color images are always stored color-by-
83 # plane, and the revised Ultrasound image objects are stored color-by-
84 # plane if the color model is YBR_FULL. Everything else is stored
85 # color-by-pixel.
86 +px --color-by-pixel
88 always store color-by-pixel
89 # If the compressed image is a color image, store in color-by-pixel
91 # planar configuration.
92 +pl --color-by-plane
94 always store color-by-plane
95 # If the compressed image is a color image, store in color-by-plane
97 # planar configuration.
98 SOP Instance UID:
100 +ud --uid-default
102 keep same SOP Instance UID (default)
103 # Never assigns a new SOP instance UID.
105 +ua --uid-always
107 always assign new UID
108 # Always assigns a new SOP instance UID.
110 workaround options for incorrect JPEG-LS encodings:
112 +wi --workaround-incpl
114 enable workaround for incomplete JPEG-LS data
115 other processing options:
117 +io --ignore-offsettable
119 ignore offset table when decompressing
120 output options
122 output file format:
123 +F --write-file
125 write file format (default)
126 -F --write-dataset
128 write data set without file meta information
129 output transfer syntax:
131 +te --write-xfer-little
133 write with explicit VR little endian (default)
134 +tb --write-xfer-big
136 write with explicit VR big endian TS
137 +ti --write-xfer-implicit
139 write with implicit VR little endian TS
140 post-1993 value representations:
142 +u --enable-new-vr
144 enable support for new VRs (UN/UT) (default)
145 -u --disable-new-vr
147 disable support for new VRs, convert to OB
148 group length encoding:
150 +g= --group-length-recalc
152 recalculate group lengths if present (default)
153 +g --group-length-create
155 always write with group length elements
156 -g --group-length-remove
158 always write without group length elements
159 length encoding in sequences and items:
161 +e --length-explicit
163 write with explicit lengths (default)
164 -e --length-undefined
166 write with undefined lengths
167 data set trailing padding (not with --write-dataset):
169 -p= --padding-retain
171 do not change padding (default if not --write-dataset)
172 -p --padding-off
174 no padding (implicit if --write-dataset)
175 +p --padding-create [f]ile-pad [i]tem-pad: integer
177 align file on multiple of f bytes
178 and items on multiple of i bytes
179
181 dcmdjpls supports the following transfer syntaxes for input (dcmfile-
182 in):
183 LittleEndianImplicitTransferSyntax 1.2.840.10008.1.2
185 LittleEndianExplicitTransferSyntax 1.2.840.10008.1.2.1
186 DeflatedExplicitVRLittleEndianTransferSyntax 1.2.840.10008.1.2.1.99 (*)
187 BigEndianExplicitTransferSyntax 1.2.840.10008.1.2.2
188 JPEGLSLosslessTransferSyntax 1.2.840.10008.1.2.4.80
189 JPEGLSLossyTransferSyntax 1.2.840.10008.1.2.4.81
190 (*) if compiled with zlib support enabled
192 dcmdjpls supports the following transfer syntaxes for output (dcmfile-
194 out):
195 LittleEndianImplicitTransferSyntax 1.2.840.10008.1.2
197 LittleEndianExplicitTransferSyntax 1.2.840.10008.1.2.1
198 BigEndianExplicitTransferSyntax 1.2.840.10008.1.2.2
199
201 The level of logging output of the various command line tools and
202 underlying libraries can be specified by the user. By default, only
203 errors and warnings are written to the standard error stream. Using
204 option --verbose also informational messages like processing details
205 are reported. Option --debug can be used to get more details on the
206 internal activity, e.g. for debugging purposes. Other logging levels
207 can be selected using option --log-level. In --quiet mode only fatal
208 errors are reported. In such very severe error events, the application
209 will usually terminate. For more details on the different logging
210 levels, see documentation of module 'oflog'.
211 In case the logging output should be written to file (optionally with
213 logfile rotation), to syslog (Unix) or the event log (Windows) option
214 --log-config can be used. This configuration file also allows for
215 directing only certain messages to a particular output stream and for
216 filtering certain messages based on the module or application where
217 they are generated. An example configuration file is provided in
218 <etcdir>/logger.cfg.
219
221 All command line tools use the following notation for parameters:
222 square brackets enclose optional values (0-1), three trailing dots
223 indicate that multiple values are allowed (1-n), a combination of both
224 means 0 to n values.
225 Command line options are distinguished from parameters by a leading '+'
227 or '-' sign, respectively. Usually, order and position of command line
228 options are arbitrary (i.e. they can appear anywhere). However, if
229 options are mutually exclusive the rightmost appearance is used. This
230 behavior conforms to the standard evaluation rules of common Unix
231 shells.
232 In addition, one or more command files can be specified using an '@'
234 sign as a prefix to the filename (e.g. @command.txt). Such a command
235 argument is replaced by the content of the corresponding text file
236 (multiple whitespaces are treated as a single separator unless they
237 appear between two quotation marks) prior to any further evaluation.
238 Please note that a command file cannot contain another command file.
239 This simple but effective approach allows one to summarize common
240 combinations of options/parameters and avoids longish and confusing
241 command lines (an example is provided in file <datadir>/dumppat.txt).
242
244 The dcmdjpls utility will attempt to load DICOM data dictionaries
245 specified in the DCMDICTPATH environment variable. By default, i.e. if
246 the DCMDICTPATH environment variable is not set, the file
247 <datadir>/dicom.dic will be loaded unless the dictionary is built into
248 the application (default for Windows).
249 The default behavior should be preferred and the DCMDICTPATH
251 environment variable only used when alternative data dictionaries are
252 required. The DCMDICTPATH environment variable has the same format as
253 the Unix shell PATH variable in that a colon (':') separates entries.
254 On Windows systems, a semicolon (';') is used as a separator. The data
255 dictionary code will attempt to load each file specified in the
256 DCMDICTPATH environment variable. It is an error if no data dictionary
257 can be loaded.
258
260 dcmcjpls(1)
261
263 Copyright (C) 2009-2022 by OFFIS e.V., Escherweg 2, 26121 Oldenburg,
264 Germany.
265Version 3.6.7 Fri Apr 22 2022 dcmdjpls(1)