1dcmdrle(1)                        OFFIS DCMTK                       dcmdrle(1)
2
3
4

NAME

6       dcmdrle - Decode RLE-compressed DICOM file
7
8

SYNOPSIS

10       dcmdrle [options] dcmfile-in dcmfile-out
11

DESCRIPTION

13       The  dcmdrle  utility  reads a RLE-compressed DICOM image (dcmfile-in),
14       decompresses the image data (i.e. conversion to a native DICOM transfer
15       syntax) and writes the converted image to an output file (dcmfile-out).
16

PARAMETERS

18       dcmfile-in   DICOM input filename to be converted
19
20       dcmfile-out  DICOM output filename
21

OPTIONS

23   general options
24         -h   --help
25                print this help text and exit
26
27              --version
28                print version information and exit
29
30              --arguments
31                print expanded command line arguments
32
33         -q   --quiet
34                quiet mode, print no warnings and errors
35
36         -v   --verbose
37                verbose mode, print processing details
38
39         -d   --debug
40                debug mode, print debug information
41
42         -ll  --log-level  [l]evel: string constant
43                (fatal, error, warn, info, debug, trace)
44                use level l for the logger
45
46         -lc  --log-config  [f]ilename: string
47                use config file f for the logger
48
49   input options
50       input file format:
51
52         +f   --read-file
53                read file format or data set (default)
54
55         +fo  --read-file-only
56                read file format only
57
58         -f   --read-dataset
59                read data set without file meta information
60
61         # This option allows one to decompress RLE 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
66   processing options
67       SOP Instance UID:
68
69         +ud  --uid-default
70                keep same SOP Instance UID (default)
71
72         +ua  --uid-always
73                always assign new UID
74
75       RLE byte segment order:
76
77         +bd  --byte-order-default
78                most significant byte first (default)
79
80         +br  --byte-order-reverse
81                least significant byte first
82
83         # This option allows one to decompress RLE compressed DICOM files in which
84         # the order of byte segments is encoded in incorrect order. This only affects
85         # images with more than one byte per sample.
86
87   output options
88       output file format:
89
90         +F   --write-file
91                write file format (default)
92
93         -F   --write-dataset
94                write data set without file meta information
95
96       output transfer syntax:
97
98         +te  --write-xfer-little
99                write with explicit VR little endian (default)
100
101         +tb  --write-xfer-big
102                write with explicit VR big endian TS
103
104         +ti  --write-xfer-implicit
105                write with implicit VR little endian TS
106
107       post-1993 value representations:
108
109         +u   --enable-new-vr
110                enable support for new VRs (UN/UT) (default)
111
112         -u   --disable-new-vr
113                disable support for new VRs, convert to OB
114
115       group length encoding:
116
117         +g=  --group-length-recalc
118                recalculate group lengths if present (default)
119
120         +g   --group-length-create
121                always write with group length elements
122
123         -g   --group-length-remove
124                always write without group length elements
125
126       length encoding in sequences and items:
127
128         +e   --length-explicit
129                write with explicit lengths (default)
130
131         -e   --length-undefined
132                write with undefined lengths
133
134       data set trailing padding (not with --write-dataset):
135
136         -p=  --padding-retain
137                do not change padding (default if not --write-dataset)
138
139         -p   --padding-off
140                no padding (implicit if --write-dataset)
141
142         +p   --padding-create  [f]ile-pad [i]tem-pad: integer
143                align file on multiple of f bytes
144                and items on multiple of i bytes
145

TRANSFER SYNTAXES

147       dcmdrle  supports  the  following transfer syntaxes for input (dcmfile-
148       in):
149
150       LittleEndianImplicitTransferSyntax             1.2.840.10008.1.2
151       LittleEndianExplicitTransferSyntax             1.2.840.10008.1.2.1
152       DeflatedExplicitVRLittleEndianTransferSyntax   1.2.840.10008.1.2.1.99 (*)
153       BigEndianExplicitTransferSyntax                1.2.840.10008.1.2.2
154       RLELosslessTransferSyntax                      1.2.840.10008.1.2.5
155
156       (*) if compiled with zlib support enabled
157
158       dcmdrle supports the following transfer syntaxes for  output  (dcmfile-
159       out):
160
161       LittleEndianImplicitTransferSyntax             1.2.840.10008.1.2
162       LittleEndianExplicitTransferSyntax             1.2.840.10008.1.2.1
163       BigEndianExplicitTransferSyntax                1.2.840.10008.1.2.2
164

LOGGING

166       The  level  of  logging  output  of  the various command line tools and
167       underlying libraries can be specified by the  user.  By  default,  only
168       errors  and  warnings  are  written to the standard error stream. Using
169       option --verbose also informational messages  like  processing  details
170       are  reported.  Option  --debug  can be used to get more details on the
171       internal activity, e.g. for debugging purposes.  Other  logging  levels
172       can  be  selected  using option --log-level. In --quiet mode only fatal
173       errors are reported. In such very severe error events, the  application
174       will  usually  terminate.  For  more  details  on the different logging
175       levels, see documentation of module 'oflog'.
176
177       In case the logging output should be written to file  (optionally  with
178       logfile  rotation),  to syslog (Unix) or the event log (Windows) option
179       --log-config can be used.  This  configuration  file  also  allows  for
180       directing  only  certain messages to a particular output stream and for
181       filtering certain messages based on the  module  or  application  where
182       they  are  generated.  An  example  configuration  file  is provided in
183       <etcdir>/logger.cfg.
184

COMMAND LINE

186       All command line tools  use  the  following  notation  for  parameters:
187       square  brackets  enclose  optional  values  (0-1), three trailing dots
188       indicate that multiple values are allowed (1-n), a combination of  both
189       means 0 to n values.
190
191       Command line options are distinguished from parameters by a leading '+'
192       or '-' sign, respectively. Usually, order and position of command  line
193       options  are  arbitrary  (i.e.  they  can appear anywhere). However, if
194       options are mutually exclusive the rightmost appearance is  used.  This
195       behavior  conforms  to  the  standard  evaluation  rules of common Unix
196       shells.
197
198       In addition, one or more command files can be specified  using  an  '@'
199       sign  as  a  prefix to the filename (e.g. @command.txt). Such a command
200       argument is replaced by the content  of  the  corresponding  text  file
201       (multiple  whitespaces  are  treated  as a single separator unless they
202       appear between two quotation marks) prior to  any  further  evaluation.
203       Please  note  that  a command file cannot contain another command file.
204       This simple but effective  approach  allows  one  to  summarize  common
205       combinations  of  options/parameters  and  avoids longish and confusing
206       command lines (an example is provided in file <datadir>/dumppat.txt).
207

ENVIRONMENT

209       The dcmdrle utility  will  attempt  to  load  DICOM  data  dictionaries
210       specified  in the DCMDICTPATH environment variable. By default, i.e. if
211       the  DCMDICTPATH  environment   variable   is   not   set,   the   file
212       <datadir>/dicom.dic  will be loaded unless the dictionary is built into
213       the application (default for Windows).
214
215       The  default  behavior  should  be  preferred   and   the   DCMDICTPATH
216       environment  variable  only used when alternative data dictionaries are
217       required. The DCMDICTPATH environment variable has the same  format  as
218       the  Unix  shell PATH variable in that a colon (':') separates entries.
219       On Windows systems, a semicolon (';') is used as a separator. The  data
220       dictionary  code  will  attempt  to  load  each  file  specified in the
221       DCMDICTPATH environment variable. It is an error if no data  dictionary
222       can be loaded.
223

SEE ALSO

225       dcmcrle(1)
226
228       Copyright  (C)  2002-2014  by OFFIS e.V., Escherweg 2, 26121 Oldenburg,
229       Germany
230
231
232
233Version 3.6.2                   Fri Jul 14 2017                     dcmdrle(1)
Impressum