Файл настроек логгера для dicom storage
На этой странице представлены видеоролики, которые помогут быстрее разобраться в программе.
Для лучшего восприятия советуем разворачивать фильм на весь экран.
Полная версия руководства: находится здесь.
EXIT CODES
The dcmsend utility uses the following exit codes when terminating. This enables the user to check for the reason why the application terminated.
The storescu application implements a Service Class User (SCU) for the Storage Service Class. For each DICOM file on the command line it sends a C-STORE message to a Storage Service Class Provider (SCP) and waits for a response. The application can be used to transmit DICOM images and other DICOM composite objects.
При неполадках в программе:
Typical Usage
A typical use case of dcmsend is to send arbitrary SOP instances that are stored as DICOM files to a storage SCP. The following command does exactly this:
If the DICOM files are stored in a hierarchy of directories below the directory "IMAGES", the following command can be used:
It is also possible to specify multiple directories and to combine the aforementioned approaches (using both file and directory names):
If the SOP instances are referenced from a DICOMDIR file, option –read-from-dicomdir (or +rd) can be used to send all referenced DICOM files without loading them already for the association negotiation:
And again, all of the above approaches can be combined like this:
The default option –read-file-only makes sure that only DICOM files (i.e. the ones with meta-header and magic word "DICM" after the preamble) are processed. Usually, if processing a whole bunch of files, it is also a good idea not to halt on the first invalid input file or if an unsuccessful store was encountered. This can be accomplished by using option –no-halt. Please note, however, that "unsuccessful store" does not mean that the DIMSE status of the C-STORE response indicates an error. It means that the C-STORE request could not be sent to the storage SCP.
If more than 128 presentation contexts are needed, which is the maximum number allowed according to the DICOM standard, a new association is started after the previous one has been completed. In cases where this behavior is unwanted, it can be disabled using option –single-association. In addition, whether only lossless compressed data sets are decompressed (if needed), which is the default, or also lossy compressed data sets can be specified using the –decompress-xxx options.
In order to get both an overview and detailed information on the transfer of the DICOM SOP instances, option –create-report-file can be used to create a corresponding text file. However, this file is only created as a final step if the application did not terminate before (with an error).
Обработка изображений в Vidar Dicom Viewer
Основные, базовые методы обработки изображений в VDV, более сложные будут представлены в соответствующих видео.
output options
network options
COMMAND LINE
All command line tools use the following notation for parameters: square brackets enclose optional values (0-1), three trailing dots indicate that multiple values are allowed (1-n), a combination of both means 0 to n values.
Command line options are distinguished from parameters by a leading '+' or '-' sign, respectively. Usually, order and position of command line options are arbitrary (i.e. they can appear anywhere). However, if options are mutually exclusive the rightmost appearance is used. This behaviour conforms to the standard evaluation rules of common Unix shells.
In addition, one or more command files can be specified using an '@' sign as a prefix to the filename (e.g. @command.txt). Such a command argument is replaced by the content of the corresponding text file (multiple whitespaces are treated as a single separator unless they appear between two quotation marks) prior to any further evaluation. Please note that a command file cannot contain another command file. This simple but effective approach allows to summarize common combinations of options/parameters and avoids longish and confusing command lines (an example is provided in file /dumppat.txt).
DICOM Conformance
Basically, the dcmsend application supports all Storage SOP Classes as an SCU, including private ones. By default, the application checks the SOP Class UID of the DICOM file in order to make sure that only valid SOP instances are sent. With option –no-uid-checks this check can be disabled.
The dcmsend application also supports all Transfer Syntaxes that are defined in the DICOM standard. Private transfer syntaxes can only be used if the UID check is disabled with option –no-uid-checks. Please note, however, that only a limited number of transfer syntaxes are supported for converting them to the default transfer syntax (Implicit VR Little Endian). With option –list-decoders the transfer syntaxes supported natively or by decoders are listed. The output typically looks like the following:
Since dcmsend tries to be as simple as possible for the user, by default presentation contexts might be proposed to the SCP that are strictly speaking "illegal". This is because, according to the DICOM standard, the SCU always has to propose the default transfer syntax in at least one presentation context associated with each abstract syntax (i.e. SOP class). This requirement is waived if the SCU only has access to the SOP instance in lossy compressed form or if the decompressed pixel data would be too large to be encoded. With option –no-illegal-proposal the strict DICOM-conformant behavior can be enforced, i.e. no possibly illegal presentation context will be proposed but the corresponding SOP instance will be rejected (if needed). Please note, however, that the size of the decompressed pixel data is not checked.
The default transfer syntax for "Lossless JPEG Compression", "Lossy JPEG Compression" and so on are not always proposed as also required by the DICOM standard. The same limitation applies to other compression schemes. See DICOM PS 3.5 section 10 for details.
The level of logging output of the various command line tools and underlying libraries can be specified by the user. By default, only errors and warnings are written to the standard error stream. Using option –verbose also informational messages like processing details are reported. Option –debug can be used to get more details on the internal activity, e.g. for debugging purposes. Other logging levels can be selected using option –log-level. In –quiet mode only fatal errors are reported. In such very severe error events, the application will usually terminate. For more details on the different logging levels, see documentation of module "oflog".
In case the logging output should be written to file (optionally with logfile rotation), to syslog (Unix) or the event log (Windows) option –log-config can be used. This configuration file also allows for directing only certain messages to a particular output stream and for filtering certain messages based on the module or application where they are generated. An example configuration file is provided in /logger.cfg.
All command line tools use the following notation for parameters: square brackets enclose optional values (0-1), three trailing dots indicate that multiple values are allowed (1-n), a combination of both means 0 to n values.
Command line options are distinguished from parameters by a leading '+' or '-' sign, respectively. Usually, order and position of command line options are arbitrary (i.e. they can appear anywhere). However, if options are mutually exclusive the rightmost appearance is used. This behavior conforms to the standard evaluation rules of common Unix shells.
In addition, one or more command files can be specified using an '@' sign as a prefix to the filename (e.g. @command.txt). Such a command argument is replaced by the content of the corresponding text file (multiple whitespaces are treated as a single separator unless they appear between two quotation marks) prior to any further evaluation. Please note that a command file cannot contain another command file. This simple but effective approach allows one to summarize common combinations of options/parameters and avoids longish and confusing command lines (an example is provided in file /dumppat.txt).
The dcmsend utility uses the following exit codes when terminating. This enables the user to check for the reason why the application terminated.
Scanning Directories
Adding directories as a parameter to the command line only makes sense if option –scan-directories is also given. If the files in the provided directories should be selected according to a specific name pattern (e.g. using wildcard matching), option –scan-pattern has to be used. Please note that this file pattern only applies to the files within the scanned directories, and, if any other patterns are specified on the command line outside the –scan-pattern option (e.g. in order to select further files), these do not apply to the specified directories.
Thus, the third of the above examples will recurse over directories IMAGES_1 and IMAGES_2 and transmit files that are contained in these two folders and all their subfolders (due to option +r). Additionally, dcmsend will transfer "test.img" and all files with extension "dcm" from the current working folder. Note that providing directory names without enabling option +sd does not make sense.
general options
Редактирование данных исследования в Vidar Dicom Viewer
Удаление исследования и снимков в VDV, анонимизация, создание копий исследований.
Association Negotiation Profiles and Configuration Files
storescu supports a flexible mechanism for specifying the DICOM network association negotiation behavior, based on so-called "association negotiation profiles" which may be read from a configuration file. The format and semantics of this configuration file are documented in asconfig.txt.
The level of logging output of the various command line tools and underlying libraries can be specified by the user. By default, only errors and warnings are written to the standard error stream. Using option –verbose also informational messages like processing details are reported. Option –debug can be used to get more details on the internal activity, e.g. for debugging purposes. Other logging levels can be selected using option –log-level. In –quiet mode only fatal errors are reported. In such very severe error events, the application will usually terminate. For more details on the different logging levels, see documentation of module "oflog".
In case the logging output should be written to file (optionally with logfile rotation), to syslog (Unix) or the event log (Windows) option –log-config can be used. This configuration file also allows for directing only certain messages to a particular output stream and for filtering certain messages based on the module or application where they are generated. An example configuration file is provided in /logger.cfg.
All command line tools use the following notation for parameters: square brackets enclose optional values (0-1), three trailing dots indicate that multiple values are allowed (1-n), a combination of both means 0 to n values.
Command line options are distinguished from parameters by a leading '+' or '-' sign, respectively. Usually, order and position of command line options are arbitrary (i.e. they can appear anywhere). However, if options are mutually exclusive the rightmost appearance is used. This behavior conforms to the standard evaluation rules of common Unix shells.
In addition, one or more command files can be specified using an '@' sign as a prefix to the filename (e.g. @command.txt). Such a command argument is replaced by the content of the corresponding text file (multiple whitespaces are treated as a single separator unless they appear between two quotation marks) prior to any further evaluation. Please note that a command file cannot contain another command file. This simple but effective approach allows one to summarize common combinations of options/parameters and avoids longish and confusing command lines (an example is provided in file /dumppat.txt).
The storescu utility will attempt to load DICOM data dictionaries specified in the DCMDICTPATH environment variable. By default, i.e. if the DCMDICTPATH environment variable is not set, the file /dicom.dic will be loaded unless the dictionary is built into the application (default for Windows).
The default behavior should be preferred and the DCMDICTPATH environment variable only used when alternative data dictionaries are required. The DCMDICTPATH environment variable has the same format as the Unix shell PATH variable in that a colon (":") separates entries. On Windows systems, a semicolon (";") is used as a separator. The data dictionary code will attempt to load each file specified in the DCMDICTPATH environment variable. It is an error if no data dictionary can be loaded.
/asconfig.txt - configuration file documentation
/storescu.cfg - example association negotiation profile
Copyright (C) 1996-2022 by OFFIS e.V., Escherweg 2, 26121 Oldenburg, Germany.
Generated on Thu Apr 28 2022 for DCMTK Version 3.6.7 by Doxygen 1.9.1
Щелкните по кнопке в правом нижнем углу окна настроек. Появится окно дополнительных настроек
Запись исследований в Vidar Dicom Viewer
Это видео показывает, как записать исследования на CD/DVD, жесткий диск и USB-диск в VDV.
general
Кодировки
Ассоциации
Щелкните на кнопке Ассоциировать с файлами Dicom для текущего пользователя, чтобы зарегистрировать программу как обработчик *.dcm - файлов (для текущего пользователя)
Стоматологическая программа - Ортопантомограмма
Программа Ортопантомограмма предназначена для анализа патологических изменений со стороны альвеолярных отростков челюстей, зубов, околоносовых пазух, нижнечелюстных каналов, височно-нижнечелюстных суставов, планирования операций в челюстно-лицевой хирургии, хирургической стоматологии и оториноларингологии, с отображением в различных (включая произвольные) плоскостях и 3D, с возможностью регулирования толщины выделенного слоя.
network errors
(*) Actually, these codes are currently not used by dcmsend but serve as a placeholder for the corresponding group of exit codes.
The dcmsend utility will attempt to load DICOM data dictionaries specified in the DCMDICTPATH environment variable. By default, i.e. if the DCMDICTPATH environment variable is not set, the file /dicom.dic will be loaded unless the dictionary is built into the application (default for Windows).
The default behavior should be preferred and the DCMDICTPATH environment variable only used when alternative data dictionaries are required. The DCMDICTPATH environment variable has the same format as the Unix shell PATH variable in that a colon (":") separates entries. On Windows systems, a semicolon (";") is used as a separator. The data dictionary code will attempt to load each file specified in the DCMDICTPATH environment variable. It is an error if no data dictionary can be loaded.
dcmrecv(1), storescu(1), storescp(1)
Copyright (C) 2011-2022 by OFFIS e.V., Escherweg 2, 26121 Oldenburg, Germany.
Generated on Thu Apr 28 2022 for DCMTK Version 3.6.7 by Doxygen 1.9.1
A typical use case of dcmsend is to send arbitrary SOP instances that are stored as DICOM files to a storage SCP. The following command does exactly this:
If the DICOM files are stored in a hierarchy of directories below the directory "IMAGES", the following command can be used:
It is also possible to specify multiple directories and to combine the aforementioned approaches (using both file and directory names):
If the SOP instances are referenced from a DICOMDIR file, option --read-from-dicomdir (or +rd) can be used to send all referenced DICOM files without loading them already for the association negotiation:
And again, all of the above approaches can be combined like this:
The default option --read-file-only makes sure that only DICOM files (i.e. the ones with meta-header and magic word "DICM" after the preamble) are processed. Usually, if processing a whole bunch of files, it is also a good idea not to halt on the first invalid input file or if an unsuccessful store was encountered. This can be accomplished by using option --no-halt. Please note, however, that "unsuccessful store" does not mean that the DIMSE status of the C-STORE response indicates an error. It means that the C-STORE request could not be sent to the storage SCP.
If more than 128 presentation contexts are needed, which is the maximum number allowed according to the DICOM standard, a new association is started after the previous one has been completed. In cases where this behaviour is unwanted, it can be disabled using option --single-association. In addition, whether only lossless compressed data sets are decompressed (if needed), which is the default, or also lossy compressed data sets can be specified using the --decompress-xxx options.
In order to get both an overview and detailed information on the transfer of the DICOM SOP instances, option --create-report-file can be used to create a corresponding text file. However, this file is only created as a final step if the application did not terminate before (with an error).
network options
Сохранение снимков и фрагментов для экспорта в Vidar Dicom Viewer
Это видео показывает, как экспортировать из Vidar Dicom Viewer в другие программы, или сохранить в файлы стандартных изображений для использования их в презентациях, стандартных документах и т.д.
processing options
DICOM Conformance
Basically, the dcmsend application supports all Storage SOP Classes as an SCU, including private ones. By default, the application checks the SOP Class UID of the DICOM file in order to make sure that only valid SOP instances are sent. With option --no-uid-checks this check can be disabled.
The dcmsend application also supports all Transfer Syntaxes that are defined in the DICOM standard. Private transfer syntaxes can only be used if the UID check is disabled with option --no-uid-checks. Please note, however, that only a limited number of transfer syntaxes are supported for converting them to the default transfer syntax (Implicit VR Little Endian). With option --list-decoders the transfer syntaxes supported natively or by decoders are listed. The output typically looks like the following:
Since dcmsend tries to be as simple as possible for the user, by default presentation contexts might be proposed to the SCP that are strictly speaking "illegal". This is because, according to the DICOM standard, the SCU always has to propose the default transfer syntax in at least one presentation context associated with each abstract syntax (i.e. SOP class). This requirement is waived when the SCU only has access to the SOP instance in lossy compressed form. With option --no-illegal-proposal the strict DICOM-conformant behaviour can be enforced, i.e. no possibly illegal presentation context will be proposed but the corresponding SOP instance will be rejected (if needed).
Please note, however, that the default transfer syntax for "Lossless JPEG Compression", "Lossy JPEG Compression" and so on are not always proposed as also required by the DICOM standard. The same limitation applies to other compression schemes. See DICOM PS 3.5 section 10 for details.
Измерения в Vidar Dicom Viewer. Фильм третий
Проведение измерений в программе Vidar Dicom Viewer.
Показаны измерения: 3D-отрезок, 3D-кривая, измерения плотностей как простой, так и сферической “пипетками”.
Установка режима отладки
- Щелкните на кнопке
- Щелкните на пункте "Режим отладки: DEBUG" в появившемся списке
- Щелкните на кнопке "ОК", затем - на кнопке "Сохранить" в главном окне Настроек программы, перезапустите программу
Примечание:
Если, в целях отладки программы, устанавливается режим DEBUG, не забудьте вернуть на "Отладка отключена" после завершения сбора информации!
В противном случае, объем файла логирования будет очень большим.
general options
Scanning Directories
Adding directories as a parameter to the command line only makes sense if option –scan-directories is also given. If the files in the provided directories should be selected according to a specific name pattern (e.g. using wildcard matching), option –scan-pattern has to be used. Please note that this file pattern only applies to the files within the scanned directories, and, if any other patterns are specified on the command line outside the –scan-pattern option (e.g. in order to select further files), these do not apply to the specified directories.
Вывод исследований на экран в Vidar Dicom Viewer
Как расположить загруженные в программу Vidar Dicom Viewer исследования на экране программы.
Сохранить положение окон
Запоминает положение и размеры всех окон в программе аналогично Настройке размеров и положения окон.
Сочетание клавиш Ctrl+Alt+Shift+L + + + .
Измерения в Vidar Dicom Viewer. Фильм первый
Основы проведения измерений в программе. Показаны основы построения измерений, принятых в лучевой диагностике, в Vidar Dicom Viewer.
input options
Импорт исследований в Vidar Dicom Viewer
Мы начинаем цикл видеороликов, посвященных работе в Vidar Dicom Viewer.
Первый ролик посвящен добавлению исследований в Vidar Dicom Viewer из разных источников. Это видео показывает, как загрузить исследования с CD/DVD, жесткого диска и USB-диска в программу.
DICOM Conformance
The storescu application supports the following Storage SOP Classes as an SCU:
The default behavior of storescu is to propose two presentation contexts for each supported SOP class (abstract syntax) - one with the preferred transfer syntax and one with all other uncompressed transfer syntaxes. The default preferred transfer syntax is explicit VR with byte ordering corresponding to the local byte ordering of the machine on which storescu is running. This behavior can be changed with the –propose, –combine and –required options, see above. Depending on these options, the following transfer syntaxes are supported:
Additional Storage SOP Classes and Transfer Syntaxes can be used with the so-called "association negotiation profiles" (see below).
The storescu application does not support extended negotiation by default. However, using an appropriate association negotiation profile (see below) the optional support for extended negotiation can be added to particular SOP classes.
Ручное редактирование основного файла Настроек программы
Логирование
Измерения в Vidar Dicom Viewer. Фильм второй
Проведение измерений в программе Vidar Dicom Viewer.
Показаны измерения: кардиоторакальный индекс, продольное плоскостопие, ацетабулярный угол, угол Кобба, измерение укорочения конечностей.
input options
Синхронизация серий в компьютерной томографии
Это видео показывает, как исправлять ошибки автоматической синхронизации в VDV: при смещении пациента, дыхании, ошибках лаборантов.
transport layer security (TLS) options
Измерения в Vidar Dicom Viewer. Фильм четвертый
Ручное измерение объемов Vidar Dicom Viewer.
Показано ручное измерение объемов сложной конфигурации путем построения замкнутых областей.
The dcmsend application implements a Service Class User (SCU) for the Storage Service Class. In contrast to the well-known storescu utility, dcmsend has less options and is, therefore, easier to use - this also explains the term "simple" in the title. The main purpose of this application is to send a whole bunch of DICOM files to a Storage Service Class Provider (SCP). dcmsend supports both multiple associations (one after the other) and decompression of DICOM SOP instances if needed to transfer them.
Перенос настроек на другой компьютер
- Щелкните на кнопке Экспорт
- Оставьте галочки нужных для переноса настроек
- Щелкните на кнопке Ok и укажите место сохранения файла настроек
- Перенесите файл настроек на другой компьютер
- Запустите ВДВ на другом компьютере, откройте Настройки/Дополнительно
- Щелкните на кнопке Импорт, укажите файл Настроек
- Настройки из файла будут загружены в программу на другом компьютере
Наложение изображений в Vidar Dicom Viewer
Наложение изображений в Vidar Dicom Viewer с функциями суммации и вычитания (Fusion, Subtraction), наложение 2Д-изображений из файлов.
LOGGING
The level of logging output of the various command line tools and underlying libraries can be specified by the user. By default, only errors and warnings are written to the standard error stream. Using option --verbose also informational messages like processing details are reported. Option --debug can be used to get more details on the internal activity, e.g. for debugging purposes. Other logging levels can be selected using option --log-level. In --quiet mode only fatal errors are reported. In such very severe error events, the application will usually terminate. For more details on the different logging levels, see documentation of module "oflog".
In case the logging output should be written to file (optionally with logfile rotation), to syslog (Unix) or the event log (Windows) option --log-config can be used. This configuration file also allows for directing only certain messages to a particular output stream and for filtering certain messages based on the module or application where they are generated. An example configuration file is provided in /logger.cfg).
input file errors
output file errors
Настройки
Показывает расположение всех файлов Настроек программы, открывает проводник с каталогом Настроек.
При обновлении программы предыдущие Настройки сохраняются и импортируются автоматически
Функции принудительного импорта/экспорта Настроек удобны для переноса настроек с компьютера на компьютер.
Например, настройки пленочных принтеров или оверлея
Scanning Directories
Adding directories as a parameter to the command line only makes sense if option --scan-directories is also given. If the files in the provided directories should be selected according to a specific name pattern (e.g. using wildcard matching), option --scan-pattern has to be used. Please note that this file pattern only applies to the files within the scanned directories, and, if any other patterns are specified on the command line outside the --scan-pattern option (e.g. in order to select further files), these do not apply to the specified directories.
Thus, the third of the above examples will recurse over directories IMAGES_1 and IMAGES_2 and transmit files that are contained in these two folders and all their subfolders (due to option +r). Additionally, dcmsend will transfer "test.img" and all files with extension "dcm" from the current working folder. Note that providing directory names without enabling option +sd does not make sense.
Читайте также: