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

NAME

6       dcmdjpls - Decode JPEG-LS compressed DICOM file
7
8

SYNOPSIS

10       dcmdjpls [options] dcmfile-in dcmfile-out
11

DESCRIPTION

13       The  dcmdjpls  utility reads a JPEG-ls compressed DICOM image (dcmfile-
14       in), decompresses the JPEG-LS data (i. e. conversion to a native  DICOM
15       transfer  syntax)  and  writes  the  converted  image to an output file
16       (dcmfile-out).
17

PARAMETERS

19       dcmfile-in   DICOM input filename to be converted
20
21       dcmfile-out  DICOM output filename
22

OPTIONS

24   general options
25         -h   --help
26                print this help text and exit
27
28              --version
29                print version information and exit
30
31              --arguments
32                print expanded command line arguments
33
34         -q   --quiet
35                quiet mode, print no warnings and errors
36
37         -v   --verbose
38                verbose mode, print processing details
39
40         -d   --debug
41                debug mode, print debug information
42
43         -ll  --log-level  [l]evel: string constant
44                (fatal, error, warn, info, debug, trace)
45                use level l for the logger
46
47         -lc  --log-config  [f]ilename: string
48                use config file f for the logger
49
50   input options
51       input file format:
52
53         +f   --read-file
54                read file format or data set (default)
55
56         +fo  --read-file-only
57                read file format only
58
59         -f   --read-dataset
60                read data set without file meta information
61
62         # This option allows one to decompress JPEG-LS compressed DICOM objects that have
63         # been stored as dataset without meta-header. Such a thing should not exist
64         # since the transfer syntax cannot be reliably determined without meta-header,
65         # but unfortunately it does.
66
67   processing options
68       planar configuration:
69
70         +pr  --planar-restore
71                restore original planar configuration (default)
72
73         # If the compressed image is a color image, restore the planar
74         # configuration as described in the Planar Configuration attribute.
75
76         +pa  --planar-auto
77                automatically determine planar configuration
78                from SOP class and color space
79
80         # If the compressed image is a color image, store in color-by-plane
81         # planar configuration if required by the SOP class and photometric
82         # interpretation. Hardcopy Color images are always stored color-by-
83         # plane, and the revised Ultrasound image objects are stored color-by-
84         # plane if the color model is YBR_FULL.  Everything else is stored
85         # color-by-pixel.
86
87         +px  --color-by-pixel
88                always store color-by-pixel
89
90         # If the compressed image is a color image, store in color-by-pixel
91         # planar configuration.
92
93         +pl  --color-by-plane
94                always store color-by-plane
95
96         # If the compressed image is a color image, store in color-by-plane
97         # planar configuration.
98
99       SOP Instance UID:
100
101         +ud  --uid-default
102                keep same SOP Instance UID (default)
103
104         #  Never assigns a new SOP instance UID.
105
106         +ua  --uid-always
107                always assign new UID
108
109         # Always assigns a new SOP instance UID.
110
111       other processing options:
112
113         +io  --ignore-offsettable
114                ignore offset table when decompressing
115
116   output options
117       output file format:
118
119         +F   --write-file
120                write file format (default)
121
122         -F   --write-dataset
123                write data set without file meta information
124
125       output transfer syntax:
126
127         +te  --write-xfer-little
128                write with explicit VR little endian (default)
129
130         +tb  --write-xfer-big
131                write with explicit VR big endian TS
132
133         +ti  --write-xfer-implicit
134                write with implicit VR little endian TS
135
136       post-1993 value representations:
137
138         +u   --enable-new-vr
139                enable support for new VRs (UN/UT) (default)
140
141         -u   --disable-new-vr
142                disable support for new VRs, convert to OB
143
144       group length encoding:
145
146         +g=  --group-length-recalc
147                recalculate group lengths if present (default)
148
149         +g   --group-length-create
150                always write with group length elements
151
152         -g   --group-length-remove
153                always write without group length elements
154
155       length encoding in sequences and items:
156
157         +e   --length-explicit
158                write with explicit lengths (default)
159
160         -e   --length-undefined
161                write with undefined lengths
162
163       data set trailing padding (not with --write-dataset):
164
165         -p=  --padding-retain
166                do not change padding (default if not --write-dataset)
167
168         -p   --padding-off
169                no padding (implicit if --write-dataset)
170
171         +p   --padding-create  [f]ile-pad [i]tem-pad: integer
172                align file on multiple of f bytes
173                and items on multiple of i bytes
174

TRANSFER SYNTAXES

176       dcmdjpls supports the following transfer syntaxes for  input  (dcmfile-
177       in):
178
179       LittleEndianImplicitTransferSyntax             1.2.840.10008.1.2
180       LittleEndianExplicitTransferSyntax             1.2.840.10008.1.2.1
181       DeflatedExplicitVRLittleEndianTransferSyntax   1.2.840.10008.1.2.1.99 (*)
182       BigEndianExplicitTransferSyntax                1.2.840.10008.1.2.2
183       JPEGLSLosslessTransferSyntax                   1.2.840.10008.1.2.4.80
184       JPEGLSLossyTransferSyntax                      1.2.840.10008.1.2.4.81
185
186       (*) if compiled with zlib support enabled
187
188       dcmdjpls  supports the following transfer syntaxes for output (dcmfile-
189       out):
190
191       LittleEndianImplicitTransferSyntax             1.2.840.10008.1.2
192       LittleEndianExplicitTransferSyntax             1.2.840.10008.1.2.1
193       BigEndianExplicitTransferSyntax                1.2.840.10008.1.2.2
194

LOGGING

196       The level of logging output of  the  various  command  line  tools  and
197       underlying  libraries  can  be  specified by the user. By default, only
198       errors and warnings are written to the  standard  error  stream.  Using
199       option  --verbose  also  informational messages like processing details
200       are reported. Option --debug can be used to get  more  details  on  the
201       internal  activity,  e.g.  for debugging purposes. Other logging levels
202       can be selected using option --log-level. In --quiet  mode  only  fatal
203       errors  are reported. In such very severe error events, the application
204       will usually terminate. For  more  details  on  the  different  logging
205       levels, see documentation of module 'oflog'.
206
207       In  case  the logging output should be written to file (optionally with
208       logfile rotation), to syslog (Unix) or the event log  (Windows)  option
209       --log-config  can  be  used.  This  configuration  file also allows for
210       directing only certain messages to a particular output stream  and  for
211       filtering  certain  messages  based  on the module or application where
212       they are generated.  An  example  configuration  file  is  provided  in
213       <etcdir>/logger.cfg.
214

COMMAND LINE

216       All  command  line  tools  use  the  following notation for parameters:
217       square brackets enclose optional  values  (0-1),  three  trailing  dots
218       indicate  that multiple values are allowed (1-n), a combination of both
219       means 0 to n values.
220
221       Command line options are distinguished from parameters by a leading '+'
222       or  '-' sign, respectively. Usually, order and position of command line
223       options are arbitrary (i.e. they  can  appear  anywhere).  However,  if
224       options  are  mutually exclusive the rightmost appearance is used. This
225       behavior conforms to the  standard  evaluation  rules  of  common  Unix
226       shells.
227
228       In  addition,  one  or more command files can be specified using an '@'
229       sign as a prefix to the filename (e.g. @command.txt).  Such  a  command
230       argument  is  replaced  by  the  content of the corresponding text file
231       (multiple whitespaces are treated as a  single  separator  unless  they
232       appear  between  two  quotation marks) prior to any further evaluation.
233       Please note that a command file cannot contain  another  command  file.
234       This  simple  but  effective  approach  allows  one to summarize common
235       combinations of options/parameters and  avoids  longish  and  confusing
236       command lines (an example is provided in file <datadir>/dumppat.txt).
237

ENVIRONMENT

239       The  dcmdjpls  utility  will  attempt  to  load DICOM data dictionaries
240       specified in the DCMDICTPATH environment variable. By default, i.e.  if
241       the   DCMDICTPATH   environment   variable   is   not   set,  the  file
242       <datadir>/dicom.dic will be loaded unless the dictionary is built  into
243       the application (default for Windows).
244
245       The   default   behavior   should  be  preferred  and  the  DCMDICTPATH
246       environment variable only used when alternative data  dictionaries  are
247       required.  The  DCMDICTPATH environment variable has the same format as
248       the Unix shell PATH variable in that a colon (':')  separates  entries.
249       On  Windows systems, a semicolon (';') is used as a separator. The data
250       dictionary code will  attempt  to  load  each  file  specified  in  the
251       DCMDICTPATH  environment variable. It is an error if no data dictionary
252       can be loaded.
253

SEE ALSO

255       dcmcjpls(1)
256
258       Copyright (C) 2009-2014 by OFFIS e.V., Escherweg  2,  26121  Oldenburg,
259       Germany.
260
261
262
263Version 3.6.4                   Thu Nov 29 2018                    dcmdjpls(1)
Impressum