Mercurial > hg > orthanc-book
changeset 338:93581ca92c6a
merge
| author | Alain Mazy <alain@mazy.be> |
|---|---|
| date | Thu, 19 Mar 2020 09:46:02 +0100 |
| parents | 85524c571277 (current diff) a5f7fc9fb611 (diff) |
| children | c0a3cd1cabff |
| files | |
| diffstat | 14 files changed, 24 insertions(+), 24 deletions(-) [+] |
line wrap: on
line diff
--- a/Sphinx/source/developers/creating-plugins.rst Thu Mar 19 09:45:51 2020 +0100 +++ b/Sphinx/source/developers/creating-plugins.rst Thu Mar 19 09:46:02 2020 +0100 @@ -73,7 +73,7 @@ that is part of the Orthanc source distribution: * `Plugins/Include/orthanc/OrthancCPlugin.h - <https://bitbucket.org/sjodogne/orthanc/src/Orthanc-1.5.8/Plugins/Include/orthanc/OrthancCPlugin.h>`__ + <https://bitbucket.org/sjodogne/orthanc/src/Orthanc-1.6.0/Plugins/Include/orthanc/OrthancCPlugin.h>`__ `Online documentation <http://sdk.orthanc-server.com/>`__ for this C header is available, as generated by `Doxygen @@ -87,8 +87,8 @@ ``HAS_ORTHANC_EXCEPTION`` is set to ``0``: * `Plugins/Samples/Common/OrthanPluginCppWrapper.h - <https://bitbucket.org/sjodogne/orthanc/src/Orthanc-1.5.8/Plugins/Samples/Common/OrthancPluginCppWrapper.h>`__ + <https://bitbucket.org/sjodogne/orthanc/src/Orthanc-1.6.0/Plugins/Samples/Common/OrthancPluginCppWrapper.h>`__ * `Plugins/Samples/Common/OrthanPluginCppWrapper.cpp - <https://bitbucket.org/sjodogne/orthanc/src/Orthanc-1.5.8/Plugins/Samples/Common/OrthancPluginCppWrapper.cpp>`__ + <https://bitbucket.org/sjodogne/orthanc/src/Orthanc-1.6.0/Plugins/Samples/Common/OrthancPluginCppWrapper.cpp>`__ * `Plugins/Samples/Common/OrthanPluginException.h - <https://bitbucket.org/sjodogne/orthanc/src/Orthanc-1.5.8/Plugins/Samples/Common/OrthancPluginException.h>`__ + <https://bitbucket.org/sjodogne/orthanc/src/Orthanc-1.6.0/Plugins/Samples/Common/OrthancPluginException.h>`__
--- a/Sphinx/source/developers/db-versioning.rst Thu Mar 19 09:45:51 2020 +0100 +++ b/Sphinx/source/developers/db-versioning.rst Thu Mar 19 09:46:02 2020 +0100 @@ -26,7 +26,7 @@ Version DB v2 DB v3 DB v4 DB v5 DB v6 =============================== ===== ===== ===== ===== ===== Mainline u u u x -Orthanc 0.9.5 - Orthanc 1.5.8 u u u x +Orthanc 0.9.5 - Orthanc 1.6.0 u u u x Orthanc 0.8.5 - Orthanc 0.9.4 u u x Orthanc 0.7.3 - Orthanc 0.8.4 u x Orthanc 0.4.0 - Orthanc 0.7.2 x
--- a/Sphinx/source/faq/crash.rst Thu Mar 19 09:45:51 2020 +0100 +++ b/Sphinx/source/faq/crash.rst Thu Mar 19 09:46:02 2020 +0100 @@ -64,13 +64,13 @@ above <segfault-plugin>` is available as the ``crash.cpp`` file, here is a sample debug session:: - $ wget http://lsb.orthanc-server.com/orthanc/debug/1.5.8/Orthanc + $ wget http://lsb.orthanc-server.com/orthanc/debug/1.6.0/Orthanc $ chmod +x ./Orthanc $ gcc -fPIC -shared ./crash.cpp -I ~/orthanc/Plugins/Include -o crash.so $ ulimit -c unlimited $ echo '{ "Plugins" : ["crash.so"] }' > Configuration.json $ rm -f core ; ./Orthanc Configuration.json - W0427 15:43:24.215783 main.cpp:1436] Orthanc version: 1.5.8 + W0427 15:43:24.215783 main.cpp:1436] Orthanc version: 1.6.0 W0427 15:43:24.215910 main.cpp:1279] Performance warning: Non-release build, runtime debug assertions are turned on W0427 15:43:24.217585 OrthancConfiguration.cpp:61] Reading the configuration from: "Configuration.json" W0427 15:43:24.254733 main.cpp:700] Loading plugin(s) from: crash.so
--- a/Sphinx/source/faq/debugging.rst Thu Mar 19 09:45:51 2020 +0100 +++ b/Sphinx/source/faq/debugging.rst Thu Mar 19 09:46:02 2020 +0100 @@ -45,13 +45,13 @@ to debug Orthanc without compiling from sources. Here is a sample debug session:: - $ wget http://lsb.orthanc-server.com/orthanc/debug/1.5.8/Orthanc + $ wget http://lsb.orthanc-server.com/orthanc/debug/1.6.0/Orthanc $ chmod +x ./Orthanc $ gdb ./Orthanc Configuration.json (gdb) catch throw Catchpoint 1 (throw) (gdb) run - W0513 15:24:42.374349 main.cpp:1436] Orthanc version: 1.5.8 + W0513 15:24:42.374349 main.cpp:1436] Orthanc version: 1.6.0 ---> Reproduce your error case <--- Thread 15 "Orthanc" hit Catchpoint 1 (exception thrown), 0x00007ffff6de68bd in __cxa_throw () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 (gdb) backtrace
--- a/Sphinx/source/faq/dicom.rst Thu Mar 19 09:45:51 2020 +0100 +++ b/Sphinx/source/faq/dicom.rst Thu Mar 19 09:46:02 2020 +0100 @@ -12,7 +12,7 @@ * Turn off all the firewalls on the two computers (especially on Microsoft Windows). * Make sure the remote computer has `DICOM TLS encryption <https://www.dicomstandard.org/using/security/>`__ turned off (this - feature is not supported yet as of Orthanc 1.5.8). + feature is not supported yet as of Orthanc 1.6.0). * Write down on a paper the following information about each modality: * its IP address (avoid using symbolic names if possible to troubleshot any DNS problem),
--- a/Sphinx/source/faq/log.rst Thu Mar 19 09:45:51 2020 +0100 +++ b/Sphinx/source/faq/log.rst Thu Mar 19 09:46:02 2020 +0100 @@ -49,7 +49,7 @@ 2. Stop the Orthanc service. The actual process depends on your version of Windows. -3. Copy the just-downloaded ``Orthanc-1.5.8-Release.exe`` together +3. Copy the just-downloaded ``Orthanc-1.6.0-Release.exe`` together with your configuration file (that is by default located in ``C:\Orthanc\Configuration.json``) into the same folder (e.g. ``C:\Temp``). @@ -58,7 +58,7 @@ ``Orthanc.log`` file:: $ cd C:\Temp - $ Orthanc-1.5.8-Release.exe --verbose Configuration.json > Orthanc.log 2<&1 + $ Orthanc-1.6.0-Release.exe --verbose Configuration.json > Orthanc.log 2<&1 5. Once the log has been generated (by default, it is available as ``C:\Temp\Orthanc.log``), stop Orthanc and possibly restart the
--- a/Sphinx/source/faq/orthanc-storage.rst Thu Mar 19 09:45:51 2020 +0100 +++ b/Sphinx/source/faq/orthanc-storage.rst Thu Mar 19 09:46:02 2020 +0100 @@ -59,9 +59,9 @@ database schema is kept as simple as possible, and can be found in the following two files of the source code of Orthanc: `PrepareDatabase.sql -<https://bitbucket.org/sjodogne/orthanc/src/Orthanc-1.5.8/OrthancServer/Database/PrepareDatabase.sql>`__ +<https://bitbucket.org/sjodogne/orthanc/src/Orthanc-1.6.0/OrthancServer/Database/PrepareDatabase.sql>`__ and `InstallTrackAttachmentsSize.sql -<https://bitbucket.org/sjodogne/orthanc/src/Orthanc-1.5.8/OrthancServer/Database/InstallTrackAttachmentsSize.sql>`__. +<https://bitbucket.org/sjodogne/orthanc/src/Orthanc-1.6.0/OrthancServer/Database/InstallTrackAttachmentsSize.sql>`__. Direct access
--- a/Sphinx/source/faq/scalability.rst Thu Mar 19 09:45:51 2020 +0100 +++ b/Sphinx/source/faq/scalability.rst Thu Mar 19 09:46:02 2020 +0100 @@ -43,7 +43,7 @@ Here is a generic setup that should provide best performance in the presence of large databases: -* Make sure to use the latest release of Orthanc (1.5.8 at the time of +* Make sure to use the latest release of Orthanc (1.6.0 at the time of writing). * We suggest to use the latest release of the :ref:`PostgreSQL plugin
--- a/Sphinx/source/faq/security.rst Thu Mar 19 09:45:51 2020 +0100 +++ b/Sphinx/source/faq/security.rst Thu Mar 19 09:46:02 2020 +0100 @@ -187,7 +187,7 @@ configuration of remote modalities. -**Remark:** As of Orthanc 1.5.8, `DICOM TLS encryption +**Remark:** As of Orthanc 1.6.0, `DICOM TLS encryption <https://www.dicomstandard.org/using/security/>`__ is not supported yet. We are looking for :ref:`an industrial sponsor <contributing>` to get this feature implemented, as it is useful in enterprise and cloud
--- a/Sphinx/source/faq/transcoding.rst Thu Mar 19 09:45:51 2020 +0100 +++ b/Sphinx/source/faq/transcoding.rst Thu Mar 19 09:46:02 2020 +0100 @@ -6,7 +6,7 @@ General information ------------------- -As of release 1.5.8, Orthanc does not feature support for transcoding +As of release 1.6.0, Orthanc does not feature support for transcoding DICOM instances yet. In other words, the Orthanc core never changes the :ref:`transfer syntax <dicom-pixel-data>` of some DICOM instance when it has to send it to another modality using the DICOM protocol.
--- a/Sphinx/source/plugins/postgresql.rst Thu Mar 19 09:45:51 2020 +0100 +++ b/Sphinx/source/plugins/postgresql.rst Thu Mar 19 09:46:02 2020 +0100 @@ -247,7 +247,7 @@ between several instances of Orthanc that would simultaneously write to the database. -As a consequence, as of Orthanc 1.5.8, when connecting multiple +As a consequence, as of Orthanc 1.6.0, when connecting multiple Orthanc to a single database by setting ``Lock`` to ``false``, there should only be one instance of Orthanc acting as a writer and all the other instances of Orthanc acting as readers only. Be careful to set
--- a/Sphinx/source/users/advanced-rest.rst Thu Mar 19 09:45:51 2020 +0100 +++ b/Sphinx/source/users/advanced-rest.rst Thu Mar 19 09:46:02 2020 +0100 @@ -128,7 +128,7 @@ ``ErrorCode`` and ``ErrorDescription`` fields for more information. * ``Paused``: The job has been paused. * ``Retry``: The job has failed internally, and has been scheduled for - re-submission after a delay. As of Orthanc 1.5.8, this feature is not + re-submission after a delay. As of Orthanc 1.6.0, this feature is not used by any type of job. In order to wait for the end of an asynchronous call, the caller will @@ -150,7 +150,7 @@ * Retry a job in ``Failed`` state by POST-ing to ``/jobs/.../resubmit``. The related state machine is depicted in the `implementation notes -<https://bitbucket.org/sjodogne/orthanc/raw/Orthanc-1.5.8/Resources/ImplementationNotes/JobsEngineStates.pdf>`__. +<https://bitbucket.org/sjodogne/orthanc/raw/Orthanc-1.6.0/Resources/ImplementationNotes/JobsEngineStates.pdf>`__.
--- a/Sphinx/source/users/configuration.rst Thu Mar 19 09:45:51 2020 +0100 +++ b/Sphinx/source/users/configuration.rst Thu Mar 19 09:46:02 2020 +0100 @@ -7,7 +7,7 @@ Configuring Orthanc simply consists in providing a configuration file. Orthanc has numerous configuration that are documented in the `default configuration file -<https://bitbucket.org/sjodogne/orthanc/raw/Orthanc-1.5.8/Resources/Configuration.json>`_. This +<https://bitbucket.org/sjodogne/orthanc/raw/Orthanc-1.6.0/Resources/Configuration.json>`_. This file is in the `JSON <https://en.wikipedia.org/wiki/JSON>`_ file format. You can generate this file file with the following call::
--- a/Sphinx/source/users/docker.rst Thu Mar 19 09:45:51 2020 +0100 +++ b/Sphinx/source/users/docker.rst Thu Mar 19 09:46:02 2020 +0100 @@ -66,7 +66,7 @@ If more stability is required, you can select the official release of Orthanc to be run:: - $ sudo docker run -p 4242:4242 -p 8042:8042 --rm jodogne/orthanc:1.5.8 + $ sudo docker run -p 4242:4242 -p 8042:8042 --rm jodogne/orthanc:1.6.0 Passing additional command-line options (e.g. to make Orthanc verbose) can be done as follows (note the ``/etc/orthanc`` option that is @@ -115,7 +115,7 @@ container to some path in the filesystem of your Linux host, e.g.:: $ mkdir /tmp/orthanc-db - $ sudo docker run -p 4242:4242 -p 8042:8042 --rm -v /tmp/orthanc-db/:/var/lib/orthanc/db/ jodogne/orthanc:1.5.8 + $ sudo docker run -p 4242:4242 -p 8042:8042 --rm -v /tmp/orthanc-db/:/var/lib/orthanc/db/ jodogne/orthanc:1.6.0 Whole-slide imaging support @@ -236,4 +236,4 @@ * The build artifacts can be found in folder ``/root/orthanc/Build``. * This command launches the mainline version. To start a released version, - use e.g. ``jodogne/orthanc-debug:1.5.8``. + use e.g. ``jodogne/orthanc-debug:1.6.0``.