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

NAME

6       dcmmkcrv - Add 2D curve data to image
7
8

SYNOPSIS

10       dcmmkcrv [options] dcmfile-in curvedata-in dcmfile-out
11

DESCRIPTION

13       The dcmmkcrv utility allows one to create DICOM images containing curve
14       data. Since curve data  is  hardly  used  by  vendors  today,  this  is
15       intended  as  a means to test implementations that can read curve data.
16       The utility reads an existing DICOM image and a  text  file  containing
17       the  curve  data in textual form. A DICOM curve data repeating group is
18       created according to the options specified on the command  line,  added
19       to  the  existing  image  and  written back to file. The output file is
20       encoded with the same transfer syntax used for  the  input  file.  This
21       utility only supports the creation of two-dimensional curves.
22

PARAMETERS

24       dcmfile-in    DICOM input image file
25
26       curvedata-in  curve data input file (text)
27
28       dcmfile-out   DICOM output filename
29

OPTIONS

31   general options
32         -h   --help
33                print this help text and exit
34
35              --version
36                print version information and exit
37
38              --arguments
39                print expanded command line arguments
40
41         -q   --quiet
42                quiet mode, print no warnings and errors
43
44         -v   --verbose
45                verbose mode, print processing details
46
47         -d   --debug
48                debug mode, print debug information
49
50         -ll  --log-level  [l]evel: string constant
51                (fatal, error, warn, info, debug, trace)
52                use level l for the logger
53
54         -lc  --log-config  [f]ilename: string
55                use config file f for the logger
56
57   curve creation options
58       curve type:
59
60         -r  --poly
61               create as POLY curve (default)
62
63         +r  --roi
64               create as ROI curve
65
66       curve value representation:
67
68         +v  --data-vr  [n]umber: integer 0..4 (default: 4)
69               select curve data VR: 0=US, 1=SS, 2=FL, 3=FD, 4=SL
70
71         -c  --curve-vr  [n]umber: integer 0..2 (default: 0)
72               select VR with which the Curve Data element is written
73               0=VR according to --data-vr, 1=OB, 2=OW
74
75       repeating group:
76
77         -g  --group  [n]umber: integer 0..15 (default: 0)
78               select repeating group: 0=0x5000, 1=0x5002 etc.
79
80       curve description:
81
82         -l  --label  s: string
83               set Curve Label to s (default: absent)
84
85         +d  --description  s: string
86               set Curve Description to s (default: absent)
87
88         -a  --axis  x: string, y: string
89               set Axis Units to xy (default: absent)
90

NOTES

92   Syntax of the Curve Data File
93       The  curve  data  file  is  expected  to  be  a  plain  ASCII text file
94       containing numbers (integer or floating point) comprising the values of
95       the  point  coordinates.  Numbers  must  be separated by whitespace. No
96       checking of the value range or value  range  conversion  is  performed.
97       Example:
98
99        256.451947    1.000000
100        477.689863  128.822080
101        128.822080  477.689863
102         35.310137  128.822080
103        256.451947    1.000000
104

LOGGING

106       The  level  of  logging  output  of  the various command line tools and
107       underlying libraries can be specified by the  user.  By  default,  only
108       errors  and  warnings  are  written to the standard error stream. Using
109       option --verbose also informational messages  like  processing  details
110       are  reported.  Option  --debug  can be used to get more details on the
111       internal activity, e.g. for debugging purposes.  Other  logging  levels
112       can  be  selected  using option --log-level. In --quiet mode only fatal
113       errors are reported. In such very severe error events, the  application
114       will  usually  terminate.  For  more  details  on the different logging
115       levels, see documentation of module 'oflog'.
116
117       In case the logging output should be written to file  (optionally  with
118       logfile  rotation),  to syslog (Unix) or the event log (Windows) option
119       --log-config can be used.  This  configuration  file  also  allows  for
120       directing  only  certain messages to a particular output stream and for
121       filtering certain messages based on the  module  or  application  where
122       they  are  generated.  An  example  configuration  file  is provided in
123       <etcdir>/logger.cfg.
124

COMMAND LINE

126       All command line tools  use  the  following  notation  for  parameters:
127       square  brackets  enclose  optional  values  (0-1), three trailing dots
128       indicate that multiple values are allowed (1-n), a combination of  both
129       means 0 to n values.
130
131       Command line options are distinguished from parameters by a leading '+'
132       or '-' sign, respectively. Usually, order and position of command  line
133       options  are  arbitrary  (i.e.  they  can appear anywhere). However, if
134       options are mutually exclusive the rightmost appearance is  used.  This
135       behavior  conforms  to  the  standard  evaluation  rules of common Unix
136       shells.
137
138       In addition, one or more command files can be specified  using  an  '@'
139       sign  as  a  prefix to the filename (e.g. @command.txt). Such a command
140       argument is replaced by the content  of  the  corresponding  text  file
141       (multiple  whitespaces  are  treated  as a single separator unless they
142       appear between two quotation marks) prior to  any  further  evaluation.
143       Please  note  that  a command file cannot contain another command file.
144       This simple but effective  approach  allows  one  to  summarize  common
145       combinations  of  options/parameters  and  avoids longish and confusing
146       command lines (an example is provided in file <datadir>/dumppat.txt).
147

ENVIRONMENT

149       The dcmmkcrv utility will  attempt  to  load  DICOM  data  dictionaries
150       specified  in the DCMDICTPATH environment variable. By default, i.e. if
151       the  DCMDICTPATH  environment   variable   is   not   set,   the   file
152       <datadir>/dicom.dic  will be loaded unless the dictionary is built into
153       the application (default for Windows).
154
155       The  default  behavior  should  be  preferred   and   the   DCMDICTPATH
156       environment  variable  only used when alternative data dictionaries are
157       required. The DCMDICTPATH environment variable has the same  format  as
158       the  Unix  shell PATH variable in that a colon (':') separates entries.
159       On Windows systems, a semicolon (';') is used as a separator. The  data
160       dictionary  code  will  attempt  to  load  each  file  specified in the
161       DCMDICTPATH environment variable. It is an error if no data  dictionary
162       can be loaded.
163
165       Copyright  (C)  1998-2022  by OFFIS e.V., Escherweg 2, 26121 Oldenburg,
166       Germany.
167
168
169
170Version 3.6.7                   Fri Apr 22 2022                    dcmmkcrv(1)
Impressum