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

NAME

6       dcmpschk - Checking tool for presentation states
7
8

SYNOPSIS

10       dcmpschk [options] [dcmfile-in...]
11

DESCRIPTION

13       The dcmpschk utility checks DICOM Grayscale Softcopy Presentation State
14       objects for conformance with the standard. The  test  is  performed  in
15       three phases:
16
17       • Phase  1  checks  the  Meta-header  of  the  DICOM file. It is tested
18         whether all required attributes are present, whether  the  SOP  class
19         and  instance  UIDs match the UIDs in the main object and whether the
20         group length attribute contains a correct value. The Transfer  Syntax
21         of the Meta header is also checked.
22       • Phase   2   performs   a   syntactic   check  of  the  values,  value
23         representations and value multiplicities for each  attribute  in  the
24         object. The values present in the object under test are compared with
25         the definitions of the DICOM data dictionary.
26       • Phase  3  performs  a  semantic  check  of  the  integrity   of   the
27         Presentation  State.  This phase is omitted when objects of other SOP
28         Classes are encountered. Phase 1 and 2 can also be applied  to  other
29         DICOM  objects  of  arbitrary  SOP  class.  It  should  be noted that
30         dcmpschk does not support Presentation States which contain the  Mask
31         Module. These will be rejected with a message that the Mask Module is
32         not supported.

PARAMETERS

34       dcmfile-in  presentation state file(s) to be checked

OPTIONS

36   general options
37         -h   --help
38                print this help text and exit
39
40              --version
41                print version information and exit
42
43              --arguments
44                print expanded command line arguments
45
46         -q   --quiet
47                quiet mode, print no warnings and errors
48
49         -v   --verbose
50                verbose mode, print processing details
51
52         -d   --debug
53                debug mode, print debug information
54
55         -ll  --log-level  [l]evel: string constant
56                (fatal, error, warn, info, debug, trace)
57                use level l for the logger
58
59         -lc  --log-config  [f]ilename: string
60                use config file f for the logger

LOGGING

62       The level of logging output of  the  various  command  line  tools  and
63       underlying  libraries  can  be  specified by the user. By default, only
64       errors and warnings are written to the  standard  error  stream.  Using
65       option  --verbose  also  informational messages like processing details
66       are reported. Option --debug can be used to get  more  details  on  the
67       internal  activity,  e.g.  for debugging purposes. Other logging levels
68       can be selected using option --log-level. In --quiet  mode  only  fatal
69       errors  are reported. In such very severe error events, the application
70       will usually terminate. For  more  details  on  the  different  logging
71       levels, see documentation of module 'oflog'.
72       In  case  the logging output should be written to file (optionally with
73       logfile rotation), to syslog (Unix) or the event log  (Windows)  option
74       --log-config  can  be  used.  This  configuration  file also allows for
75       directing only certain messages to a particular output stream  and  for
76       filtering  certain  messages  based  on the module or application where
77       they are generated.  An  example  configuration  file  is  provided  in
78       <etcdir>/logger.cfg.

COMMAND LINE

80       All  command  line  tools  use  the  following notation for parameters:
81       square brackets enclose optional  values  (0-1),  three  trailing  dots
82       indicate  that multiple values are allowed (1-n), a combination of both
83       means 0 to n values.
84       Command line options are distinguished from parameters by a leading '+'
85       or  '-' sign, respectively. Usually, order and position of command line
86       options are arbitrary (i.e. they  can  appear  anywhere).  However,  if
87       options  are  mutually exclusive the rightmost appearance is used. This
88       behavior conforms to the  standard  evaluation  rules  of  common  Unix
89       shells.
90       In  addition,  one  or more command files can be specified using an '@'
91       sign as a prefix to the filename (e.g. @command.txt).  Such  a  command
92       argument  is  replaced  by  the  content of the corresponding text file
93       (multiple whitespaces are treated as a  single  separator  unless  they
94       appear  between  two  quotation marks) prior to any further evaluation.
95       Please note that a command file cannot contain  another  command  file.
96       This  simple  but  effective  approach  allows  one to summarize common
97       combinations of options/parameters and  avoids  longish  and  confusing
98       command lines (an example is provided in file <datadir>/dumppat.txt).

ENVIRONMENT

100       The  dcmpschk  utility  will  attempt  to  load DICOM data dictionaries
101       specified in the DCMDICTPATH environment variable. By default, i.e.  if
102       the   DCMDICTPATH   environment   variable   is   not   set,  the  file
103       <datadir>/dicom.dic will be loaded unless the dictionary is built  into
104       the application (default for Windows).
105       The   default   behavior   should  be  preferred  and  the  DCMDICTPATH
106       environment variable only used when alternative data  dictionaries  are
107       required.  The  DCMDICTPATH environment variable has the same format as
108       the Unix shell PATH variable in that a colon (':')  separates  entries.
109       On  Windows systems, a semicolon (';') is used as a separator. The data
110       dictionary code will  attempt  to  load  each  file  specified  in  the
111       DCMDICTPATH  environment variable. It is an error if no data dictionary
112       can be loaded.
114       Copyright (C) 2000-2014 by OFFIS e.V., Escherweg  2,  26121  Oldenburg,
115       Germany.
116
117
118
119Version 3.6.4                   Thu Nov 29 2018                    dcmpschk(1)
Impressum