Mercurial > hg > orthanc-book

comparison Sphinx/source/faq/features.rst @ 25:669ea65ba7fb

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
fix links
author Sebastien Jodogne <s.jodogne@gmail.com>
date Wed, 20 Jul 2016 09:26:08 +0200
parents 901e8961f46e
children d6bd1dd820e5
comparison
equal deleted inserted replaced
24:25fa874803ab 25:669ea65ba7fb
62 62
63 If your disk space is limited, besides :ref:`recycling`, you should 63 If your disk space is limited, besides :ref:`recycling`, you should
64 also consider using **disk space compression**. When compression is 64 also consider using **disk space compression**. When compression is
65 enabled, Orthanc compresses the incoming DICOM instances on-the-fly 65 enabled, Orthanc compresses the incoming DICOM instances on-the-fly
66 before writing them to the filesystem, using `zlib 66 before writing them to the filesystem, using `zlib
67 <http://en.wikipedia.org/wiki/Zlib>`_. This is useful, because the 67 <https://en.wikipedia.org/wiki/Zlib>`_. This is useful, because the
68 images are often stored as raw, uncompressed arrays in DICOM 68 images are often stored as raw, uncompressed arrays in DICOM
69 instances: The size of a typical DICOM instance can hopefully be 69 instances: The size of a typical DICOM instance can hopefully be
70 divided by a factor 2 through lossless compression. This compression 70 divided by a factor 2 through lossless compression. This compression
71 process is transparent to the user, as Orthanc automatically 71 process is transparent to the user, as Orthanc automatically
72 decompresses the file before sending it back to the external world. 72 decompresses the file before sending it back to the external world.