1dcmdrle(1) OFFIS DCMTK dcmdrle(1)
2
6 dcmdrle - Decode RLE-compressed DICOM file
7
9 dcmdrle [options] dcmfile-in dcmfile-out
10
12 The dcmdrle utility reads a RLE-compressed DICOM image (dcmfile-in),
13 decompresses the image 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 RLE compressed DICOM objects that have
61 # been stored as dataset without meta-header. Such a thing should not exist
62 # since the transfer syntax cannot be reliably determined without meta-header,
63 # but unfortunately it does.
64 processing options
66 SOP Instance UID:
67 +ud --uid-default
69 keep same SOP Instance UID (default)
70 +ua --uid-always
72 always assign new UID
73 RLE byte segment order:
75 +bd --byte-order-default
77 most significant byte first (default)
78 +br --byte-order-reverse
80 least significant byte first
81 # This option allows to decompress RLE compressed DICOM files in which the
83 # order of byte segments is encoded in incorrect order. This only affects
84 # images with more than one byte per sample.
85 output options
87 output file format:
88 +F --write-file
90 write file format (default)
91 -F --write-dataset
93 write data set without file meta information
94 output transfer syntax:
96 +te --write-xfer-little
98 write with explicit VR little endian (default)
99 +tb --write-xfer-big
101 write with explicit VR big endian TS
102 +ti --write-xfer-implicit
104 write with implicit VR little endian TS
105 post-1993 value representations:
107 +u --enable-new-vr
109 enable support for new VRs (UN/UT) (default)
110 -u --disable-new-vr
112 disable support for new VRs, convert to OB
113 group length encoding:
115 +g= --group-length-recalc
117 recalculate group lengths if present (default)
118 +g --group-length-create
120 always write with group length elements
121 -g --group-length-remove
123 always write without group length elements
124 length encoding in sequences and items:
126 +e --length-explicit
128 write with explicit lengths (default)
129 -e --length-undefined
131 write with undefined lengths
132 data set trailing padding (not with --write-dataset):
134 -p= --padding-retain
136 do not change padding (default if not --write-dataset)
137 -p --padding-off
139 no padding (implicit if --write-dataset)
140 +p --padding-create [f]ile-pad [i]tem-pad: integer
142 align file on multiple of f bytes
143 and items on multiple of i bytes
144
146 dcmdrle supports the following transfer syntaxes for input (dcmfile-
147 in):
148 LittleEndianImplicitTransferSyntax 1.2.840.10008.1.2
150 LittleEndianExplicitTransferSyntax 1.2.840.10008.1.2.1
151 DeflatedExplicitVRLittleEndianTransferSyntax 1.2.840.10008.1.2.1.99 (*)
152 BigEndianExplicitTransferSyntax 1.2.840.10008.1.2.2
153 RLELosslessTransferSyntax 1.2.840.10008.1.2.5
154 (*) if compiled with zlib support enabled
156 dcmdrle supports the following transfer syntaxes for output (dcmfile-
158 out):
159 LittleEndianImplicitTransferSyntax 1.2.840.10008.1.2
161 LittleEndianExplicitTransferSyntax 1.2.840.10008.1.2.1
162 BigEndianExplicitTransferSyntax 1.2.840.10008.1.2.2
163
165 The level of logging output of the various command line tools and
166 underlying libraries can be specified by the user. By default, only
167 errors and warnings are written to the standard error stream. Using
168 option --verbose also informational messages like processing details
169 are reported. Option --debug can be used to get more details on the
170 internal activity, e.g. for debugging purposes. Other logging levels
171 can be selected using option --log-level. In --quiet mode only fatal
172 errors are reported. In such very severe error events, the application
173 will usually terminate. For more details on the different logging
174 levels, see documentation of module 'oflog'.
175 In case the logging output should be written to file (optionally with
177 logfile rotation), to syslog (Unix) or the event log (Windows) option
178 --log-config can be used. This configuration file also allows for
179 directing only certain messages to a particular output stream and for
180 filtering certain messages based on the module or application where
181 they are generated. An example configuration file is provided in
182 <etcdir>/logger.cfg).
183
185 All command line tools use the following notation for parameters:
186 square brackets enclose optional values (0-1), three trailing dots
187 indicate that multiple values are allowed (1-n), a combination of both
188 means 0 to n values.
189 Command line options are distinguished from parameters by a leading '+'
191 or '-' sign, respectively. Usually, order and position of command line
192 options are arbitrary (i.e. they can appear anywhere). However, if
193 options are mutually exclusive the rightmost appearance is used. This
194 behaviour conforms to the standard evaluation rules of common Unix
195 shells.
196 In addition, one or more command files can be specified using an '@'
198 sign as a prefix to the filename (e.g. @command.txt). Such a command
199 argument is replaced by the content of the corresponding text file
200 (multiple whitespaces are treated as a single separator unless they
201 appear between two quotation marks) prior to any further evaluation.
202 Please note that a command file cannot contain another command file.
203 This simple but effective approach allows to summarize common
204 combinations of options/parameters and avoids longish and confusing
205 command lines (an example is provided in file <datadir>/dumppat.txt).
206
208 The dcmdrle utility will attempt to load DICOM data dictionaries
209 specified in the DCMDICTPATH environment variable. By default, i.e. if
210 the DCMDICTPATH environment variable is not set, the file
211 <datadir>/dicom.dic will be loaded unless the dictionary is built into
212 the application (default for Windows).
213 The default behaviour should be preferred and the DCMDICTPATH
215 environment variable only used when alternative data dictionaries are
216 required. The DCMDICTPATH environment variable has the same format as
217 the Unix shell PATH variable in that a colon (':') separates entries.
218 On Windows systems, a semicolon (';') is used as a separator. The data
219 dictionary code will attempt to load each file specified in the
220 DCMDICTPATH environment variable. It is an error if no data dictionary
221 can be loaded.
222
224 dcmcrle(1)
225
227 Copyright (C) 2002-2010 by OFFIS e.V., Escherweg 2, 26121 Oldenburg,
228 Germany
229Version 3.6.0 6 Jan 2011 dcmdrle(1)