1dcmmkcrv(1) OFFIS DCMTK dcmmkcrv(1)
2
6 dcmmkcrv - Add 2D curve data to image
7
9 dcmmkcrv [options] dcmfile-in curvedata-in dcmfile-out
10
12 The dcmmkcrv utility allows to create DICOM images containing curve
13 data. Since curve data is hardly used by vendors today, this is
14 intended as a means to test implementations that can read curve data.
15 The utility reads an existing DICOM image and a text file containing
16 the curve data in textual form. A DICOM curve data repeating group is
17 created according to the options specified on the command line, added
18 to the existing image and written back to file. The output file is
19 encoded with the same transfer syntax used for the input file. This
20 utility only supports the creation of two-dimensional curves.
21
23 dcmfile-in DICOM input image file
24 curvedata-in curve data input file (text)
26 dcmfile-out DICOM output filename
28
30 general options
31 -h --help
32 print this help text and exit
33 --version
35 print version information and exit
36 --arguments
38 print expanded command line arguments
39 -q --quiet
41 quiet mode, print no warnings and errors
42 -v --verbose
44 verbose mode, print processing details
45 -d --debug
47 debug mode, print debug information
48 -ll --log-level [l]evel: string constant
50 (fatal, error, warn, info, debug, trace)
51 use level l for the logger
52 -lc --log-config [f]ilename: string
54 use config file f for the logger
55 curve creation options
57 curve type:
58 -r --poly
60 create as POLY curve (default)
61 +r --roi
63 create as ROI curve
64 curve value representation:
66 +v --data-vr [n]umber: integer 0..4 (default: 4)
68 select curve data VR: 0=US, 1=SS, 2=FL, 3=FD, 4=SL
69 -c --curve-vr [n]umber: integer 0..2 (default: 0)
71 select VR with which the Curve Data element is written
72 0=VR according to --data-vr, 1=OB, 2=OW
73 repeating group:
75 -g --group [n]umber: integer 0..15 (default: 0)
77 select repeating group: 0=0x5000, 1=0x5002 etc.
78 curve description:
80 -l --label s: string
82 set Curve Label to s (default: absent)
83 +d --description s: string
85 set Curve Description to s (default: absent)
86 -a --axis x: string, y: string
88 set Axis Units to xy (default: absent)
89
91 Syntax of the Curve Data File
92 The curve data file is expected to be a plain ASCII text file
93 containing numbers (integer or floating point) comprising the values of
94 the point coordinates. Numbers must be separated by whitespace. No
95 checking of the value range or value range conversion is performed.
96 Example:
97 256.451947 1.000000
99 477.689863 128.822080
100 128.822080 477.689863
101 35.310137 128.822080
102 256.451947 1.000000
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 behaviour 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 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 dcmmkcrv 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 behaviour 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 Copyright (C) 1998-2010 by OFFIS e.V., Escherweg 2, 26121 Oldenburg,
165 Germany.
166Version 3.6.0 6 Jan 2011 dcmmkcrv(1)