Mercurial > hg > orthanc

comparison Resources/Configuration.json @ 2625:5469dda691cd jobs

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
new configuration option: SynchronousCMove
author Sebastien Jodogne <s.jodogne@gmail.com>
date Fri, 25 May 2018 10:54:33 +0200
parents 1232922c8793
children 6801f99bbc2f
comparison
equal deleted inserted replaced
2624:714dcddeb65f 2625:5469dda691cd
377 // "00e1,10c2" : [ "UI", "PET-CT Multi Modality Name", 1, 1, "ELSCINT1" ] 377 // "00e1,10c2" : [ "UI", "PET-CT Multi Modality Name", 1, 1, "ELSCINT1" ]
378 // "7053,1003" : [ "ST", "Original Image Filename", 1, 1, "Philips PET Private Group" ] 378 // "7053,1003" : [ "ST", "Original Image Filename", 1, 1, "Philips PET Private Group" ]
379 // "2001,5f" : [ "SQ", "StackSequence", 1, 1, "Philips Imaging DD 001" ] 379 // "2001,5f" : [ "SQ", "StackSequence", 1, 1, "Philips Imaging DD 001" ]
380 }, 380 },
381 381
382 // Whether to run DICOM C-Move operations synchronously. If set to
383 // "false" (the default), each incoming C-Move request results in
384 // creating a new background job. Until Orthanc 1.3.2, the default
385 // behavior was to use synchronous C-Move.
386 "SynchronousCMove" : false,
387
382 // Maximum number of completed jobs that are kept in memory. A 388 // Maximum number of completed jobs that are kept in memory. A
383 // processing job is considered as complete once it is tagged as 389 // processing job is considered as complete once it is tagged as
384 // "Success" or "Failure". 390 // "Success" or "Failure".
385 "JobsHistorySize" : 10 391 "JobsHistorySize" : 10
386 } 392 }