Mercurial > hg > orthanc-book
comparison Sphinx/source/plugins/gdcm.rst @ 415:b224cb85a96c
cont
author | Sebastien Jodogne <s.jodogne@gmail.com> |
---|---|
date | Fri, 15 May 2020 16:38:17 +0200 |
parents | 83f36bc9e725 |
children | 525d59a7c198 |
comparison
equal
deleted
inserted
replaced
414:83f36bc9e725 | 415:b224cb85a96c |
---|---|
119 simultaneously call the GDCM decoder/transcoder. This is useful to | 119 simultaneously call the GDCM decoder/transcoder. This is useful to |
120 avoid uncontrolled CPU or RAM usage if many people are connected to | 120 avoid uncontrolled CPU or RAM usage if many people are connected to |
121 the same Orthanc server. By default, no throttling is applied, and | 121 the same Orthanc server. By default, no throttling is applied, and |
122 an unrestricted number of threads can call GDCM simultaneously. | 122 an unrestricted number of threads can call GDCM simultaneously. |
123 | 123 |
124 * ``BuiltinDecoderTranscoderOrder`` is a configuration option of the | 124 * Starting with Orthanc 1.7.0, ``BuiltinDecoderTranscoderOrder`` is a |
125 Orthanc core (i.e. outside of the ``Gdcm`` section) that can be used | 125 configuration option of the Orthanc core (i.e. outside of the |
126 to control whether the built-in DCMTK decoder/transcoder is applied | 126 ``Gdcm`` section) that can be used to control whether the built-in |
127 before or after GDCM. | 127 DCMTK decoder/transcoder is applied before or after GDCM. |
128 | 128 |
129 As a complement to the ``Enable`` option, you also have the | 129 As a complement to the ``Enable`` option, you also have the |
130 possibility to restrict the GDCM decoder/transcoder to some specific | 130 possibility to restrict the GDCM decoder/transcoder to some specific |
131 `transfer syntaxes | 131 `transfer syntaxes |
132 <http://dicom.nema.org/medical/dicom/current/output/html/part05.html#chapter_10>`__ | 132 <http://dicom.nema.org/medical/dicom/current/output/html/part05.html#chapter_10>`__ |