1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
|
/*!
\if MANPAGES
\page dcmmkcrv Add 2D curve data to image
\else
\page dcmmkcrv dcmmkcrv: Add 2D curve data to image
\endif
\section synopsis SYNOPSIS
\verbatim
dcmmkcrv [options] dcmimg-in curvedata-in dcmimg-out
\endverbatim
\section description DESCRIPTION
The \b dcmmkcrv utility allows to create DICOM images containing curve data.
Since curve data is hardly used by vendors today, this is intended as a
means to test implementations that can read curve data. The utility reads an
existing DICOM image and a text file containing the curve data in textual
form. A DICOM curve data repeating group is created according to the
options specified on the command line, added to the existing image and
written back to file. The output file is encoded with the same transfer
syntax used for the input file. This utility only supports the creation of
two-dimensional curves.
\section parameters PARAMETERS
\verbatim
dcmimg-in DICOM input image file
curvedata-in curve data input file (text)
dcmimg-out DICOM output filename
\endverbatim
\section options OPTIONS
\subsection general_options general options
\verbatim
-h --help
print this help text and exit
--version
print version information and exit
-v --verbose
verbose mode, print processing details
-d --debug
debug mode, print debug information
\endverbatim
\subsection curve_creation_options curve creation options
\verbatim
curve type:
-r --poly
create as POLY curve (default)
+r --roi
create as ROI curve
curve value representation:
+v --data-vr [n]umber: integer 0..4 (default: 4)
select curve data VR: 0=US, 1=SS, 2=FL, 3=FD, 4=SL
-c --curve-vr [n]umber: integer 0..2 (default: 0)
select VR with which the Curve Data element is written
0=VR according to --data-vr, 1=OB, 2=OW
repeating group:
-g --group [n]umber: integer 0..15 (default: 0)
select repeating group: 0=0x5000, 1=0x5002 etc.
curve description:
-l --label s: string
set Curve Label to s (default: absent)
+d --description s: string
set Curve Description to s (default: absent)
-a --axis x: string, y: string
set Axis Units to x\y (default: absent)
\endverbatim
\section notes NOTES
\subsection syntax_data_file Syntax of the Curve Data File
The curve data file is expected to be a plain ASCII text file containing
numbers (integer or floating point) comprising the values of the point
coordinates. Numbers must be separated by whitespace. No checking of the
value range or value range conversion is performed. Example:
\verbatim
256.451947 1.000000
477.689863 128.822080
128.822080 477.689863
35.310137 128.822080
256.451947 1.000000
\endverbatim
\section command_line COMMAND LINE
All command line tools use the following notation for parameters: square
brackets enclose optional values (0-1), three trailing dots indicate that
multiple values are allowed (1-n), a combination of both means 0 to n values.
Command line options are distinguished from parameters by a leading '+' or '-'
sign, respectively. Usually, order and position of command line options are
arbitrary (i.e. they can appear anywhere). However, if options are mutually
exclusive the rightmost appearance is used. This behaviour conforms to the
standard evaluation rules of common Unix shells.
In addition, one or more command files can be specified using an '@' sign as a
prefix to the filename (e.g. <em>\@command.txt</em>). Such a command argument
is replaced by the content of the corresponding text file (multiple
whitespaces are treated as a single separator) prior to any further
evaluation. Please note that a command file cannot contain another command
file. This simple but effective approach allows to summarize common
combinations of options/parameters and avoids longish and confusing command
lines (an example is provided in file <em>share/data/dumppat.txt</em>).
\section environment ENVIRONMENT
The \b dcmmkcrv utility will attempt to load DICOM data dictionaries specified
in the \e DCMDICTPATH environment variable. By default, i.e. if the
\e DCMDICTPATH environment variable is not set, the file
<em>\<PREFIX\>/lib/dicom.dic</em> will be loaded unless the dictionary is built
into the application (default for Windows).
The default behaviour should be preferred and the \e DCMDICTPATH environment
variable only used when alternative data dictionaries are required. The
\e DCMDICTPATH environment variable has the same format as the Unix shell
\e PATH variable in that a colon (":") separates entries. The data dictionary
code will attempt to load each file specified in the \e DCMDICTPATH
environment variable. It is an error if no data dictionary can be loaded.
\section copyright COPYRIGHT
Copyright (C) 1998-2004 by Kuratorium OFFIS e.V., Escherweg 2, 26121 Oldenburg,
Germany.
*/
|
