Recent Activities

  • marcelvanherk

    Replied to the thread Update 1.4.19d1 released.
    Post
    Hi,

    you need to download dcmtk-3.6.4. It has an exceutable called dcmdrle. It will likely decompress the images correctly. Then conquest will be able to read them.

    regards

    Marcel
  • pipponasella

    Replied to the thread Update 1.4.19d1 released.
    Post
    Yes, they are old images no longer present on the tac. Can't I do anything with the dgate? How do I use dcmtk?


    I thank you for the support. You're always very kind
  • marcelvanherk

    Replied to the thread Update 1.4.19d1 released.
    Post
    Hi Pippo,

    apparantly it is an ancient bug in our RLE decoder. For now I would suggest to disable RLE lossless and transfer with another compression directly from the scanner instead. It is very rare to use RLE for CT. If they are old images can you…
  • pipponasella

    Replied to the thread Update 1.4.19d1 released.
    Post


    I use the newly released 1419d version and the Centos 6.10 operating system.
    I can't view the image with any viewer. I tried with Osirix, Radiant, IQ View but the image is always damaged. If instead the amount is directly, the image can be seen
  • marcelvanherk

    Replied to the thread Update 1.4.19d1 released.
    Post
    Hi,

    what conquest version and OS?

    I tested it. The image is correctly recognized as RLE, and goes through the RLE decoder, although conquest only has an RLE decoder for 8 bits images, and your image is 13 bits.

    With irfanview or the old K-pacs viewer…
  • pipponasella

    Replied to the thread Update 1.4.19d1 released.
    Post
    Hi Marcel,
    I did a test with the attached image and dgate corrupts the file. I tried setting the Acrnema in UN and AS but on Osirix and Radiant the images are damaged. You could verify? They are RLE images.



    activated the sop - dgatesop.lst

  • Hi,

    I will not mess with character sets in 1.4.19, it a a way too big change, and few users have run into this issue.

    Just read up but character encoding in DICOM is quite complex. As first step I did add an experimental and incomplete UTF-8 handling…
  • Thanks for the info:

    It is the 2 superscript which is encoded as 0xb2 in ISO IR 100 (Latin 1), but not in UTF8. I.e. SQL should not have been set up for UTF8. There is currently no form of character translation in Conquest, this is one of its weak…
  • So we are able to push this image to other dicom servers without any issues. Please kindly check and let us know
  • Hi. 0xb2 indicates that a high bit is set on one of the characters. I.e. the scanner is using some non ASCII encoding, Conquest doesn't modify any of the text. What encoding is shown in the image header? Marcel
  • I am able to run this query directly into PostgresSQL sql tool and able to insert data fine. and also checked conquest database on PostgresSQL has encoding as UTF8. But conquest throwing out below error while receiving this data via conquest dicom…
  • conquest71

    Post
    Got it. Thank you very much.
  • marcelvanherk

    Replied to the thread Update 1.4.19d1 released.
    Post
    Great!

    Marcel
  • alansmethers

    Replied to the thread Update 1.4.19d1 released.
    Post
    Yes, that does correct the problem as well. Thank you.
  • marcelvanherk

    Post
    Hi,

    1. For a C-MOVE you can:
    a) set the transfer syntax e.g. J2 in acrnema.map
    b) address your server as e.g. CONQUESRSRV1~J2 to ask for this compression

    In a script you can use "forward compressed as J2 to SERVER"

    2. Block ImplicitLittleEndian from…
  • marcelvanherk

    Replied to the thread Update 1.4.19d1 released.
    Post
    OK,

    I was afraid of that. For completeness can you also try the previous fix (removing yours) and use:

    #ifdef UNIX
    pdusize(4096)
    #else
    pdusize(32768)
    #endif

    Just to make sure.

    Thanks,

    Marcel
  • alansmethers

    Replied to the thread Update 1.4.19d1 released.
    Post
    Marcel, that change did not make any difference to the problem. Still got the same corruption on the same few images. I went ahead and added this code to the pdata.cxx and it does resolve the problem. Not sure if you want to use it for a fix or not.

  • conquest71

    Thread
    Hello, I have few questions regarding transferring files using Conquest 1.4.19b version.

    1. How to transfer dicom files with specific transfer syntax? I would want to transfer some files with transfer syntax JPEGBaseLine1 (1.2.840.10008.1.2.4.50).

    2.…
  • marcelvanherk

    Replied to the thread Update 1.4.19d1 released.
    Post
    Ok,

    the if statement does fix another bug (on windows). Sorry, can you try another one?

    in pdu.cxx, line 93

    #ifdef UNIX
    pdusize(8192)
    #else
    pdusize(32768)
    #endif

    I know it is a sign of weakness on my side, but if it works we will leave it like this.…