1dcmdjpls(1) OFFIS DCMTK dcmdjpls(1)
2
6 dcmdjpls - Decode JPEG-LS compressed DICOM file
7
9 dcmdjpls [options] dcmfile-in dcmfile-out
10
12 The dcmdjpls utility reads a JPEG-ls compressed DICOM image (dcmfile-
13 in), decompresses the JPEG-LS data (i. e. conversion to a native DICOM
14 transfer syntax) and writes the converted image to an output file
15 (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 to decompress JPEG-LS compressed DICOM objects that have
62 # been stored as dataset without meta-header. Such a thing should not exist
63 # since the transfer syntax cannot be reliably determined without meta-header,
64 # but unfortunately it does.
65 processing options
67 planar configuration:
68 +pr --planar-restore
70 restore original planar configuration (default)
71 # If the compressed image is a color image, restore the planar
73 # configuration as described in the Planar Configuration attribute.
74 +pa --planar-auto
76 automatically determine planar configuration
77 from SOP class and color space
78 # If the compressed image is a color image, store in color-by-plane
80 # planar configuration if required by the SOP class and photometric
81 # interpretation. Hardcopy Color images are always stored color-by-
82 # plane, and the revised Ultrasound image objects are stored color-by-
83 # plane if the color model is YBR_FULL. Everything else is stored
84 # color-by-pixel.
85 +px --color-by-pixel
87 always store color-by-pixel
88 # If the compressed image is a color image, store in color-by-pixel
90 # planar configuration.
91 +pl --color-by-plane
93 always store color-by-plane
94 # If the compressed image is a color image, store in color-by-plane
96 # planar configuration.
97 SOP Instance UID:
99 +ud --uid-default
101 keep same SOP Instance UID (default)
102 # Never assigns a new SOP instance UID.
104 +ua --uid-always
106 always assign new UID
107 # Always assigns a new SOP instance UID.
109 other processing options:
111 +io --ignore-offsettable
113 ignore offset table when decompressing
114 output options
116 output file format:
117 +F --write-file
119 write file format (default)
120 -F --write-dataset
122 write data set without file meta information
123 output transfer syntax:
125 +te --write-xfer-little
127 write with explicit VR little endian (default)
128 +tb --write-xfer-big
130 write with explicit VR big endian TS
131 +ti --write-xfer-implicit
133 write with implicit VR little endian TS
134 post-1993 value representations:
136 +u --enable-new-vr
138 enable support for new VRs (UN/UT) (default)
139 -u --disable-new-vr
141 disable support for new VRs, convert to OB
142 group length encoding:
144 +g= --group-length-recalc
146 recalculate group lengths if present (default)
147 +g --group-length-create
149 always write with group length elements
150 -g --group-length-remove
152 always write without group length elements
153 length encoding in sequences and items:
155 +e --length-explicit
157 write with explicit lengths (default)
158 -e --length-undefined
160 write with undefined lengths
161 data set trailing padding (not with --write-dataset):
163 -p= --padding-retain
165 do not change padding (default if not --write-dataset)
166 -p --padding-off
168 no padding (implicit if --write-dataset)
169 +p --padding-create [f]ile-pad [i]tem-pad: integer
171 align file on multiple of f bytes
172 and items on multiple of i bytes
173
175 dcmdjpls supports the following transfer syntaxes for input (dcmfile-
176 in):
177 LittleEndianImplicitTransferSyntax 1.2.840.10008.1.2
179 LittleEndianExplicitTransferSyntax 1.2.840.10008.1.2.1
180 DeflatedExplicitVRLittleEndianTransferSyntax 1.2.840.10008.1.2.1.99 (*)
181 BigEndianExplicitTransferSyntax 1.2.840.10008.1.2.2
182 JPEGLSLosslessTransferSyntax 1.2.840.10008.1.2.4.80
183 JPEGLSLossyTransferSyntax 1.2.840.10008.1.2.4.81
184 (*) if compiled with zlib support enabled
186 dcmdjpls supports the following transfer syntaxes for output (dcmfile-
188 out):
189 LittleEndianImplicitTransferSyntax 1.2.840.10008.1.2
191 LittleEndianExplicitTransferSyntax 1.2.840.10008.1.2.1
192 BigEndianExplicitTransferSyntax 1.2.840.10008.1.2.2
193
195 The level of logging output of the various command line tools and
196 underlying libraries can be specified by the user. By default, only
197 errors and warnings are written to the standard error stream. Using
198 option --verbose also informational messages like processing details
199 are reported. Option --debug can be used to get more details on the
200 internal activity, e.g. for debugging purposes. Other logging levels
201 can be selected using option --log-level. In --quiet mode only fatal
202 errors are reported. In such very severe error events, the application
203 will usually terminate. For more details on the different logging
204 levels, see documentation of module 'oflog'.
205 In case the logging output should be written to file (optionally with
207 logfile rotation), to syslog (Unix) or the event log (Windows) option
208 --log-config can be used. This configuration file also allows for
209 directing only certain messages to a particular output stream and for
210 filtering certain messages based on the module or application where
211 they are generated. An example configuration file is provided in
212 <etcdir>/logger.cfg).
213
215 All command line tools use the following notation for parameters:
216 square brackets enclose optional values (0-1), three trailing dots
217 indicate that multiple values are allowed (1-n), a combination of both
218 means 0 to n values.
219 Command line options are distinguished from parameters by a leading '+'
221 or '-' sign, respectively. Usually, order and position of command line
222 options are arbitrary (i.e. they can appear anywhere). However, if
223 options are mutually exclusive the rightmost appearance is used. This
224 behaviour conforms to the standard evaluation rules of common Unix
225 shells.
226 In addition, one or more command files can be specified using an '@'
228 sign as a prefix to the filename (e.g. @command.txt). Such a command
229 argument is replaced by the content of the corresponding text file
230 (multiple whitespaces are treated as a single separator unless they
231 appear between two quotation marks) prior to any further evaluation.
232 Please note that a command file cannot contain another command file.
233 This simple but effective approach allows to summarize common
234 combinations of options/parameters and avoids longish and confusing
235 command lines (an example is provided in file <datadir>/dumppat.txt).
236
238 The dcmdjpls utility will attempt to load DICOM data dictionaries
239 specified in the DCMDICTPATH environment variable. By default, i.e. if
240 the DCMDICTPATH environment variable is not set, the file
241 <datadir>/dicom.dic will be loaded unless the dictionary is built into
242 the application (default for Windows).
243 The default behaviour should be preferred and the DCMDICTPATH
245 environment variable only used when alternative data dictionaries are
246 required. The DCMDICTPATH environment variable has the same format as
247 the Unix shell PATH variable in that a colon (':') separates entries.
248 On Windows systems, a semicolon (';') is used as a separator. The data
249 dictionary code will attempt to load each file specified in the
250 DCMDICTPATH environment variable. It is an error if no data dictionary
251 can be loaded.
252
254 dcmcjpls(1)
255
257 Copyright (C) 2009-2010 by OFFIS e.V., Escherweg 2, 26121 Oldenburg,
258 Germany.
259Version 3.6.0 6 Jan 2011 dcmdjpls(1)