1dcmpschk(1) OFFIS DCMTK dcmpschk(1)
2
3
4
6 dcmpschk - Checking tool for presentation states
7
9 dcmpschk [options] [dcmfile-in...]
10
12 The dcmpschk utility checks DICOM Grayscale Softcopy Presentation State
13 objects for conformance with the standard. The test is performed in
14 three phases:
15
16 · Phase 1 checks the Meta-header of the DICOM file. It is tested
17 whether all required attributes are present, whether the SOP class
18 and instance UIDs match the UIDs in the main object and whether the
19 group length attribute contains a correct value. The Transfer Syntax
20 of the Meta header is also checked.
21 · Phase 2 performs a syntactic check of the values, value
22 representations and value multiplicities for each attribute in the
23 object. The values present in the object under test are compared with
24 the definitions of the DICOM data dictionary.
25 · Phase 3 performs a semantic check of the integrity of the
26 Presentation State. This phase is omitted when objects of other SOP
27 Classes are encountered. Phase 1 and 2 can also be applied to other
28 DICOM objects of arbitrary SOP class. It should be noted that
29 dcmpschk does not support Presentation States which contain the Mask
30 Module. These will be rejected with a message that the Mask Module is
31 not supported.
33 dcmfile-in presentation state file(s) to be checked
35 general options
36 -h --help
37 print this help text and exit
38
39 --version
40 print version information and exit
41
42 --arguments
43 print expanded command line arguments
44
45 -q --quiet
46 quiet mode, print no warnings and errors
47
48 -v --verbose
49 verbose mode, print processing details
50
51 -d --debug
52 debug mode, print debug information
53
54 -ll --log-level [l]evel: string constant
55 (fatal, error, warn, info, debug, trace)
56 use level l for the logger
57
58 -lc --log-config [f]ilename: string
59 use config file f for the logger
61 The level of logging output of the various command line tools and
62 underlying libraries can be specified by the user. By default, only
63 errors and warnings are written to the standard error stream. Using
64 option --verbose also informational messages like processing details
65 are reported. Option --debug can be used to get more details on the
66 internal activity, e.g. for debugging purposes. Other logging levels
67 can be selected using option --log-level. In --quiet mode only fatal
68 errors are reported. In such very severe error events, the application
69 will usually terminate. For more details on the different logging
70 levels, see documentation of module 'oflog'.
71 In case the logging output should be written to file (optionally with
72 logfile rotation), to syslog (Unix) or the event log (Windows) option
73 --log-config can be used. This configuration file also allows for
74 directing only certain messages to a particular output stream and for
75 filtering certain messages based on the module or application where
76 they are generated. An example configuration file is provided in
77 <etcdir>/logger.cfg).
79 All command line tools use the following notation for parameters:
80 square brackets enclose optional values (0-1), three trailing dots
81 indicate that multiple values are allowed (1-n), a combination of both
82 means 0 to n values.
83 Command line options are distinguished from parameters by a leading '+'
84 or '-' sign, respectively. Usually, order and position of command line
85 options are arbitrary (i.e. they can appear anywhere). However, if
86 options are mutually exclusive the rightmost appearance is used. This
87 behaviour conforms to the standard evaluation rules of common Unix
88 shells.
89 In addition, one or more command files can be specified using an '@'
90 sign as a prefix to the filename (e.g. @command.txt). Such a command
91 argument is replaced by the content of the corresponding text file
92 (multiple whitespaces are treated as a single separator unless they
93 appear between two quotation marks) prior to any further evaluation.
94 Please note that a command file cannot contain another command file.
95 This simple but effective approach allows to summarize common
96 combinations of options/parameters and avoids longish and confusing
97 command lines (an example is provided in file <datadir>/dumppat.txt).
99 The dcmpschk utility will attempt to load DICOM data dictionaries
100 specified in the DCMDICTPATH environment variable. By default, i.e. if
101 the DCMDICTPATH environment variable is not set, the file
102 <datadir>/dicom.dic will be loaded unless the dictionary is built into
103 the application (default for Windows).
104 The default behaviour should be preferred and the DCMDICTPATH
105 environment variable only used when alternative data dictionaries are
106 required. The DCMDICTPATH environment variable has the same format as
107 the Unix shell PATH variable in that a colon (':') separates entries.
108 On Windows systems, a semicolon (';') is used as a separator. The data
109 dictionary code will attempt to load each file specified in the
110 DCMDICTPATH environment variable. It is an error if no data dictionary
111 can be loaded.
113 Copyright (C) 2000-2010 by OFFIS e.V., Escherweg 2, 26121 Oldenburg,
114 Germany.
115
116
117
118Version 3.6.0 6 Jan 2011 dcmpschk(1)