|
![]() |
||||||
PREV NEXT | FRAMES NO FRAMES |
This section lists some frequently asked questions by toolkit users.
1. I am running the toolkit's sample applications for the first time. The MC.initialize() method prints out an
UnsatisfiedLinkError message. What am I doing wrong?
This error happens when the toolkit fails to load the native library. The Java Virtual Machine searches for the library using the platform's normal search path. For a Windows platform, you should ensure that the library's location is specified in the path environment variable or it is in the same directory as the application executable. On Unix platforms the LD_LIBRARY_PATH setting controls this behavior.
2. It is inconvenient to set absolute paths for the various configuration options in the merge.ini and mergecom.pro files that need them. Is there a way to make these pathnames be configurable at run-time?
The toolkit allows the use of relative paths in these pathnames through a special macro. The "MC3INIDIR" macro is used to represents the directory where "merge.ini" is. It's used like an environment variable with the difference that it's automatically resolved and does not need to be set. If MERGECOM_3_PROFILE, MERGECOM_3_SERVICES, MERGECOM_3_APPLICATIONS LOG_FILE, DICTIONARY_FILE, MSG_INFO_FILE or TEMP_FILE_DIRECTORY settings contain relative paths and use "MC3INIDIR", the toolkit considers the path relative to the location of the "merge.ini" file.
3. I am testing the sample applications for the first time and cannot get the client (SCU) application to connect to the server (SCP) for any of the sample applications. The MCapplication::requestAssociation method is throwing an exception. It appears as though the connection is opening, but it is quickly dropped. Why is this happening?
As a security measure, the MCassociation::startListening method used in SCPs attempts to determine the hostname of SCUs connecting to it. If it cannot determine the remote hostname, it will drop the connection. The startListening method uses the local system’s host file or its configured domain name server to translate the SCU's IP address into its hostname. By configuring the SCU's hostname in your local hosts file, this problem will be eliminated. Also, the ACCEPT_ANY_HOSTNAME configuration value in the mergecom.pro file disables this checking.
4. What can be done to reduce the memory requirements of the Merge DICOM Toolkit?
The Memory Management And Performance topic describes various options to reduce native memory consumption.
5. What can be done to increase the performance of the Merge DICOM Toolkit?
The Memory Management And Performance topic describes various options to increase the performance of an application using the toolkit.
6. I am sending 8-bit images with Merge DICOM toolkit, however, after sending the data to another system, the pixel data is byte swapped incorrectly. What is causing this problem?
The Transfer Syntax And Byte Ordering topic describes this problem. This is typically only a problem on Big Endian machines. To summarize the problem, on big endian machines, the toolkit expects 8-bit data to be byte swapped. The toolkit does not look at the bits allocated and bits stored tags to determine that the pixel data itself is 8-bit data, it always treats pixel data (7fe0,0010) as OW.
7. I recently upgraded to a new release of the Merge DICOM Toolkit. Since this upgrade, exceptions are being thrown by the MCattributeSet encoding methods. This code worked before the upgrade. What is causing these problems?
The Merge DICOM data dictionary changes from release to release. In some cases, the identification number for a particular message type changes. When upgrading, if you do not change all of the data dictionary files, this error will occur. The following files should be upgraded with each release: mergecom.srv, mrgcom3.msg and mrgcom3.dct.
|
Copyright © 2023 Merge Healthcare Solutions Inc. All Rights Reserved. | ||||||
PREV NEXT | FRAMES NO FRAMES |