Mercurial > hg > orthanc

comparison Resources/Configuration.json @ 3045:095193bbd7b9

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
fix issue #118
author Sebastien Jodogne <s.jodogne@gmail.com>
date Thu, 20 Dec 2018 15:24:55 +0100
parents abe49ca61cd5
children b1787ba94eef
comparison
equal deleted inserted replaced
3044:1000178f94e4 3045:095193bbd7b9
410 // "7053,1003" : [ "ST", "Original Image Filename", 1, 1, "Philips PET Private Group" ] 410 // "7053,1003" : [ "ST", "Original Image Filename", 1, 1, "Philips PET Private Group" ]
411 // "2001,5f" : [ "SQ", "StackSequence", 1, 1, "Philips Imaging DD 001" ] 411 // "2001,5f" : [ "SQ", "StackSequence", 1, 1, "Philips Imaging DD 001" ]
412 }, 412 },
413 413
414 // Whether to run DICOM C-Move operations synchronously. If set to 414 // Whether to run DICOM C-Move operations synchronously. If set to
415 // "false" (the default), each incoming C-Move request results in 415 // "false" (asynchronous mode), each incoming C-Move request results
416 // creating a new background job. Up to Orthanc 1.3.2, the implicit 416 // in the creation of a new background job. Up to Orthanc 1.3.2, the
417 // behavior was to use synchronous C-Move. Between Orthanc 1.4.0 and 417 // implicit behavior was to use synchronous C-Move ("true"). Between
418 // 1.4.2, the default behavior was set to asynchronous C-Move. Since 418 // Orthanc 1.4.0 and 1.4.2, the default behavior was set to
419 // Orthanc 1.5.0, the default behavior is synchronous C-Move 419 // asynchronous C-Move ("false"). Since Orthanc 1.5.0, the default
420 // (backward compatibility with Orthanc <= 1.3.2). 420 // behavior is back to synchronous C-Move ("true", which ensures
421 // backward compatibility with Orthanc <= 1.3.2).
421 "SynchronousCMove" : true, 422 "SynchronousCMove" : true,
422 423
423 // Maximum number of completed jobs that are kept in memory. A 424 // Maximum number of completed jobs that are kept in memory. A
424 // processing job is considered as complete once it is tagged as 425 // processing job is considered as complete once it is tagged as
425 // "Success" or "Failure". Since Orthanc 1.5.0, a value of "0" 426 // "Success" or "Failure". Since Orthanc 1.5.0, a value of "0"