1drtdump(1) OFFIS DCMTK drtdump(1)
2
6 drtdump - Dump DICOM RT file and data set
7
10 drtdump [options] drtfile-in...
11
13 The drtdump utility dumps the contents of a DICOM Radiation Therapy
14 (RT) object (file format or raw data set) to stdout in textual form.
15 The output consists of essential information on the RT object in a
16 format that is probably easier to read than the more generic one from
17 dcmdump.
18 If drtdump reads a raw data set (DICOM data without a file format meta-
20 header) it will attempt to guess the transfer syntax by examining the
21 first few bytes of the file. It is not always possible to correctly
22 guess the transfer syntax and it is better to convert a data set to a
23 file format whenever possible (using the dcmconv utility). It is also
24 possible to use the -f and -t[ieb] options to force drtdump to read a
25 dataset with a particular transfer syntax.
26
28 drtfile-in DICOM RT input filename to be dumped
29
31 general options
32 -h --help
33 print this help text and exit
34 --version
36 print version information and exit
37 --arguments
39 print expanded command line arguments
40 -q --quiet
42 quiet mode, print no warnings and errors
43 -v --verbose
45 verbose mode, print processing details
46 -d --debug
48 debug mode, print debug information
49 -ll --log-level [l]evel: string constant
51 (fatal, error, warn, info, debug, trace)
52 use level l for the logger
53 -lc --log-config [f]ilename: string
55 use config file f for the logger
56 input options
58 input file format:
59 +f --read-file
61 read file format or data set (default)
62 +fo --read-file-only
64 read file format only
65 -f --read-dataset
67 read data set without file meta information
68 input transfer syntax:
70 -t= --read-xfer-auto
72 use TS recognition (default)
73 -td --read-xfer-detect
75 ignore TS specified in the file meta header
76 -te --read-xfer-little
78 read with explicit VR little endian TS
79 -tb --read-xfer-big
81 read with explicit VR big endian TS
82 -ti --read-xfer-implicit
84 read with implicit VR little endian TS
85 output options
87 printing:
88 +Pf --print-filename
90 print header with filename for each input file
91
93 DICOM Conformance
94 The drtdump utility supports the following SOP Classes:
95 RTImageStorage 1.2.840.10008.5.1.4.1.1.481.1
97 RTDoseStorage 1.2.840.10008.5.1.4.1.1.481.2
98 RTStructureSetStorage 1.2.840.10008.5.1.4.1.1.481.3
99 RTPlanStorage 1.2.840.10008.5.1.4.1.1.481.5
100 RTTreatmentSummaryRecordStorage 1.2.840.10008.5.1.4.1.1.481.7
101 RTIonPlanStorage 1.2.840.10008.5.1.4.1.1.481.8
102 RTIonBeamsTreatmentRecordStorage 1.2.840.10008.5.1.4.1.1.481.9
103
105 The level of logging output of the various command line tools and
106 underlying libraries can be specified by the user. By default, only
107 errors and warnings are written to the standard error stream. Using
108 option --verbose also informational messages like processing details
109 are reported. Option --debug can be used to get more details on the
110 internal activity, e.g. for debugging purposes. Other logging levels
111 can be selected using option --log-level. In --quiet mode only fatal
112 errors are reported. In such very severe error events, the application
113 will usually terminate. For more details on the different logging
114 levels, see documentation of module 'oflog'.
115 In case the logging output should be written to file (optionally with
117 logfile rotation), to syslog (Unix) or the event log (Windows) option
118 --log-config can be used. This configuration file also allows for
119 directing only certain messages to a particular output stream and for
120 filtering certain messages based on the module or application where
121 they are generated. An example configuration file is provided in
122 <etcdir>/logger.cfg.
123
125 All command line tools use the following notation for parameters:
126 square brackets enclose optional values (0-1), three trailing dots
127 indicate that multiple values are allowed (1-n), a combination of both
128 means 0 to n values.
129 Command line options are distinguished from parameters by a leading '+'
131 or '-' sign, respectively. Usually, order and position of command line
132 options are arbitrary (i.e. they can appear anywhere). However, if
133 options are mutually exclusive the rightmost appearance is used. This
134 behavior conforms to the standard evaluation rules of common Unix
135 shells.
136 In addition, one or more command files can be specified using an '@'
138 sign as a prefix to the filename (e.g. @command.txt). Such a command
139 argument is replaced by the content of the corresponding text file
140 (multiple whitespaces are treated as a single separator unless they
141 appear between two quotation marks) prior to any further evaluation.
142 Please note that a command file cannot contain another command file.
143 This simple but effective approach allows one to summarize common
144 combinations of options/parameters and avoids longish and confusing
145 command lines (an example is provided in file <datadir>/dumppat.txt).
146
148 The drtdump utility will attempt to load DICOM data dictionaries
149 specified in the DCMDICTPATH environment variable. By default, i.e. if
150 the DCMDICTPATH environment variable is not set, the file
151 <datadir>/dicom.dic will be loaded unless the dictionary is built into
152 the application (default for Windows).
153 The default behavior should be preferred and the DCMDICTPATH
155 environment variable only used when alternative data dictionaries are
156 required. The DCMDICTPATH environment variable has the same format as
157 the Unix shell PATH variable in that a colon (':') separates entries.
158 On Windows systems, a semicolon (';') is used as a separator. The data
159 dictionary code will attempt to load each file specified in the
160 DCMDICTPATH environment variable. It is an error if no data dictionary
161 can be loaded.
162
164 dcmconv(1), dcmdump(1)
165
167 Copyright (C) 2010-2014 by OFFIS e.V. and ICSMED AG, Escherweg 2, 26121
168 Oldenburg, Germany.
169Version 3.6.4 Thu Nov 29 2018 drtdump(1)