Dicom server 1.4.16(k) released !

  • Marcel,


    I changed the uncompressing to uj in known dicom providers but it still runs out of memory for our files.


    [CONQUEST] Sending file : D:\dicom\dicomserver\data\PT02-005\1.2.840.113663.1500.1.313595446.2.1.20110427.112409.718_0000_000026_13073763080125.v2
    [CONQUEST] ***VR:ReAlloc out of memory allocating 442080000 bytes
    [CONQUEST] ***A fatal error occurred (out of memory) - closing server


    I do see when I "browse databse" that images are big - the viewer shows "Large file not displayed 55.4 MB"
    Is there any way to extend allocated memory to accommodate this types of images?


    Thank you,
    Elizabeth

  • Hi Elizabeth,


    maybe the receiving end does not accept JPEG comprressed images? It is trying to uncompress the image; it asks for 9 times more memory as the 55.4 MB stated in your log. To fix this; make sure you can send JPEG data to the receiver; or run conquest on a 64 bit machine.


    Marcel

  • Hi Marcel.


    Perhaps i've missed some posts but I have an issue with the ConquestUpdate1416c.zip work in progress version.
    By using the serverside viewer I can view correctly the thumbs but when I try to "view" the images theese appears to have the same resolution of the thumbs but magnified up to "size" value (default 560 pixel). Doesn't matter what kind of image is viewed, this is constant in my system.


    This issue happen with che ConquestUpdate1416c only so I think isn't my configuration fault.


    Thanks in advance for your help.


    Davide.

  • Hi marcel, congrats for the great project you are running here.Just a question.


    I am trying to use Conquest web server to connect to a open source viewer, Weasis, but after digging aroud, i found out that Conquest cant respond to WADO requests like this one: contentType=application%2Fdicom.


    but when requesting using other protocol, like contentType=image/gif Conquest Web server is able to provide the images. So my question is, will Conquest be able to respond to Dicom WADO requests in a future build? it would be very helpfull


    Thanx in advance

  • hi, here it is the log file:


    [CONQUESTS1] Connected by address: 0100007f
    [CONQUESTS1] Testing transfer: '1.2.840.10008.1.2' against list #0 = '1.2.840.10008.1.2'
    [CONQUESTS1] 0000,0002 18 UI AffectedSOPClassUID "1.2.840.10008.1.1"
    [CONQUESTS1] 0000,0100 2 US CommandField 48
    [CONQUESTS1] 0000,0110 2 US MessageID 1
    [CONQUESTS1] 0000,0800 2 US DataSetType 257
    [CONQUESTS1] 0002,0010 17 UI TransferSyntaxUID "1.2.840.10008.1.2"
    [CONQUESTS1] 9999,0400 104 LO ConquestConsoleComma "wadorequest:\\\\1.3.12.2.1107.5.2.6.14044.30000005122107122404600000031,0/0/0/0,0/0,,application/dicom,,,"
    [CONQUESTS1] Connected by address: 0100007f
    [CONQUESTS1] Connected by address: 0100007f
    [CONQUESTS1] Testing transfer: '1.2.840.10008.1.2' against list #0 = '1.2.840.10008.1.2'
    [CONQUESTS1] 0000,0002 18 UI AffectedSOPClassUID "1.2.840.10008.1.1"
    [CONQUESTS1] 0000,0100 2 US CommandField 48
    [CONQUESTS1] 0000,0110 2 US MessageID 1
    [CONQUESTS1] 0000,0800 2 US DataSetType 257
    [CONQUESTS1] 0002,0010 17 UI TransferSyntaxUID "1.2.840.10008.1.2"
    [CONQUESTS1] 9999,0400 102 LO ConquestConsoleComma "wadorequest:\\\\1.3.12.2.1107.5.2.6.14044.30000005122107122404600000031,0/0/0/70,256/256,,image/jpeg,,,"
    [CONQUESTS1] Connected by address: 0100007f
    [CONQUESTS1] Testing transfer: '1.2.840.10008.1.2' against list #0 = '1.2.840.10008.1.2'
    [CONQUESTS1] 0000,0002 18 UI AffectedSOPClassUID "1.2.840.10008.1.1"
    [CONQUESTS1] 0000,0100 2 US CommandField 48
    [CONQUESTS1] 0000,0110 2 US MessageID 1
    [CONQUESTS1] 0000,0800 2 US DataSetType 257
    [CONQUESTS1] 0002,0010 17 UI TransferSyntaxUID "1.2.840.10008.1.2"
    [CONQUESTS1] 9999,0400 104 LO ConquestConsoleComma "wadorequest:\\\\1.3.12.2.1107.5.2.6.14044.30000005122107122404600000024,0/0/0/0,0/0,,application/dicom,,,"
    [CONQUESTS1] Testing transfer: '1.2.840.10008.1.2' against list #0 = '1.2.840.10008.1.2'
    [CONQUESTS1] 0000,0002 18 UI AffectedSOPClassUID "1.2.840.10008.1.1"
    [CONQUESTS1] 0000,0100 2 US CommandField 48
    [CONQUESTS1] 0000,0110 2 US MessageID 1
    [CONQUESTS1] 0000,0800 2 US DataSetType 257
    [CONQUESTS1] 0002,0010 17 UI TransferSyntaxUID "1.2.840.10008.1.2"
    [CONQUESTS1] 9999,0400 104 LO ConquestConsoleComma "wadorequest:\\\\1.3.12.2.1107.5.2.6.14044.30000005122107122404600000025,0/0/0/0,0/0,,application/dicom,,,"


    and here is the log file from the Weasis web viewer whe the errors ocur:


    30.06.2011 13:20:52.671 *INFO* [pool-1-thread-1] org.weasis.dicom.explorer.wado.DownloadManager Downloading WADO references: http://localhost:8080/weasis/wado_query.xml
    30.06.2011 13:20:53.030 *INFO* [pool-1-thread-1] org.weasis.dicom.explorer.wado.DownloadManager [Validate with XSD schema] wado_query is valid
    30.06.2011 13:20:53.045 *INFO* [pool-1-thread-1] org.weasis.dicom.explorer.wado.DownloadManager Adding new patient: xxxxxxx
    30.06.2011 13:20:53.076 *INFO* [pool-2-thread-3] org.weasis.dicom.explorer.wado.LoadSeries Downloading series of xxxx[1.3.12.2.1107.5.2.6.14044.30000005122107122404600000021]
    30.06.2011 13:20:53.146 *ERROR* [pool-4-thread-2] org.weasis.dicom.explorer.wado.LoadSeries Http Response error 500 for http://localhost/cgi-bin/dgate…tType=application%2Fdicom
    30.06.2011 13:20:53.255 *INFO* [AWT-EventQueue-0] org.weasis.dicom.explorer.DicomExplorer Add series: 1.3.12.2.1107.5.2.6.14044.30000005122107122404600000021
    30.06.2011 13:20:53.289 *ERROR* [pool-4-thread-1] org.weasis.dicom.explorer.wado.LoadSeries Http Response error 500 for http://localhost/cgi-bin/dgate…tType=application%2Fdicom
    30.06.2011 13:20:53.368 *ERROR* [pool-4-thread-3] org.weasis.dicom.explorer.wado.LoadSeries Http Response error 500 for http://localhost/cgi-bin/dgate…tType=application%2Fdicom
    30.06.2011 13:20:53.404 *INFO* [AWT-EventQueue-0] org.weasis.dicom.explorer.DicomModel Remove Patient: xxx
    30.06.2011 13:20:53.404 *INFO* [AWT-EventQueue-0] org.weasis.dicom.explorer.DicomModel Remove Study: 20/12/2005

  • hi again marcel.


    A few questions then...So when are you thinking in launching version 1.4.16d ?


    And if in this version will it be possible to create, to only one conquest PACS, several unique AE titles?


    And finally, if it is possible to register in the database the AE titles that sent studies to the conqust PACS.

  • I will try to release 1.4.16d today.


    Will it be possible to create, to only one conquest PACS, several unique AE titles?


    This is already possible - conquest will respond to any AE title, and scripts can use it to do their things.


    And finally, if it is possible to register in the database the AE titles that sent studies to the conqust PACS.


    Yes, in principle. The problem is then that only that server can query the database (as sender is also sent with each query). What you can do is write the sender using an importconverter in a private tag, and add that tag to the database.


    Marcel

  • hi marcel.
    Thank you for your support. The issue we talked about was resolved :D


    But something happend when we connected weasis with the conquest PACS when reading images of the type XA (angiography) and US (ultrasound) from the followin site: http://www.rubomed.com/dicomfiles/index.html


    Initially i had some dificulties, because Conquest rejected this types of images being necessary to add to the dgatesop.lst file the following lines:


    LittleEndianImplicit 1.2.840.10008.1.2 transfer
    JPEGLossless 1.2.840.10008.1.2.4.70 transfer LittleEndianExplicit
    JPEGLS_Lossless 1.2.840.10008.1.2.4.80 transfer LittleEndianExplicit
    JPEGLS_Lossy 1.2.840.10008.1.2.4.81 transfer LittleEndianExplicit
    RLELossless 1.2.840.10008.1.2.5 transfer LittleEndianExplicit
    LittleEndianExplicitDeflated 1.2.840.10008.1.2.1.99 transfer LittleEndianExplicit


    BigEndianExplicit 1.2.840.10008.1.2.2 transfer
    JPEGBaseLine1 1.2.840.10008.1.2.4.50 transfer LittleEndianExplicit
    JPEGExtended2and4 1.2.840.10008.1.2.4.51 transfer LittleEndianExplicit
    JPEGExtended3and5 1.2.840.10008.1.2.4.52 transfer LittleEndianExplicit
    JPEGSpectralNH6and8 1.2.840.10008.1.2.4.53 transfer LittleEndianExplicit
    JPEGSpectralNH7and9 1.2.840.10008.1.2.4.54 transfer LittleEndianExplicit
    JPEGFulllNH10and12 1.2.840.10008.1.2.4.55 transfer LittleEndianExplicit
    JPEGFulllNH11and13 1.2.840.10008.1.2.4.56 transfer LittleEndianExplicit
    JPEGLosslessNH14 1.2.840.10008.1.2.4.57 transfer LittleEndianExplicit


    Now conquest was able to arquive images of the type XA and US and oppening them in the viewer, except the US image (demo image 0020 of the previous link) that crashes the conquest server being required to reboot it. The error log is :



    [CONQUESTSRV1] Connected by address: 0100007f
    [CONQUESTSRV1] 0000,0002 18 UI AffectedSOPClassUID "1.2.840.10008.1.1"
    [CONQUESTSRV1] 0000,0100 2 US CommandField 48
    [CONQUESTSRV1] 0000,0110 2 US MessageID 1
    [CONQUESTSRV1] 0000,0800 2 US DataSetType 257
    [CONQUESTSRV1] 0002,0010 17 UI TransferSyntaxUID "1.2.840.10008.1.2"
    [CONQUESTSRV1] 9999,0400 108 LO ConquestConsoleComma "wadorequest:999.999.3859744\\999.999.94827453\\999.999.133.1996.1.1800.1.6.29,0/0/0/70,256/256,,image/jpeg,,,"
    [CONQUESTSRV1] Testing transfer: '1.2.840.10008.1.2' against list #0 = '1.2.840.10008.1.2'
    [CONQUESTSRV1] Query Tables: DICOMImages
    [CONQUESTSRV1] Columns : ObjectFile, DeviceName
    [CONQUESTSRV1] Where : SOPInstanc = '999.999.133.1996.1.1800.1.6.29' AND SeriesInst = '999.999.94827453'
    [CONQUESTSRV1] Order : (null)
    [CONQUESTSRV1] Locating file:MAG0 123-45-6789\999.999.94827453_5829_000028_13107260010000.dcm
    [CONQUESTSRV1] Found Palette Color, depalatizing.
    [CONQUESTSRV1] Palette table size = 256, Minimum value = 0 in 16 bytes.
    [CONQUESTSRV1] 3 components in standard palette(s).
    [CONQUESTSRV1] Output data is bytes in the
    [CONQUESTSRV1] MSB from
    [CONQUESTSRV1] 8 bits in.
    [CONQUESTSRV1] 0000,0002 18 UI AffectedSOPClassUID "1.2.840.10008.1.1"
    [CONQUESTSRV1] 0000,0100 2 US CommandField 48
    [CONQUESTSRV1] 0000,0110 2 US MessageID 1
    [CONQUESTSRV1] 0000,0800 2 US DataSetType 257
    [CONQUESTSRV1] 0002,0010 17 UI TransferSyntaxUID "1.2.840.10008.1.2"
    [CONQUESTSRV1] 9999,0400 110 LO ConquestConsoleComma "wadorequest:999.999.3859744\\999.999.94827453\\999.999.133.1996.1.1800.1.6.29,0/0/0/0,0/0,,application/dicom,,,"
    [CONQUESTSRV1] Query Tables: DICOMImages
    [CONQUESTSRV1] Columns : ObjectFile, DeviceName
    [CONQUESTSRV1] Where : SOPInstanc = '999.999.133.1996.1.1800.1.6.29' AND SeriesInst = '999.999.94827453'
    [CONQUESTSRV1] Order : (null)
    [CONQUESTSRV1] Locating file:MAG0 123-45-6789\999.999.94827453_5829_000028_13107260010000.dcm
    [CONQUESTSRV1] Recompress: cannot rewrite jpeg/rle image in v2 format


    so...any ideas? :D


    thank you in advance

  • Hi,


    how did you load the images into the server? And you seem to have enabled transfer syntaxes that the server does not support. You need to limit yourself to those set by "enable jpeg support".


    Having said that, the crash should not occur. I will add it to the buglist.


    Marcel

  • Quote from marcelvanherk

    Hi,


    just released version 1.4.16d


    Marcel


    Hi Marcel.
    I've just tested the new release and It appears to work perfectly.
    Unfortunately I'm a very mindless user so I have no idea about how to write the zip.cq script in order to download the selected study directly from the web interface.
    Actually when I try to push the selected study to a ZIP file taking a look in the Conquest log window I can see a message for each image that say:


    [CONQUEST]*** Importconverter-1.0 script not found: zip.cq


    I know I sould have the informations to write my zip.cq exportconverter file but I have no idea, I'm sorry.
    Can you suggest me something please ?


    Thanks for reading this and have a nice holidays.


    Davidone.

  • I'm testing the latest version of the DICOM server (1.4.16D) I noticed that if I try to resend study an existent study the system erases everything from the archive.
    I mistaken something in configuration?
    thanks

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!