Conquest and Ultrasound

  • Just tested the US sequence with image 11 a cine. Works fine (uncompressed or NKI compressed) in conquest14.12 with kpacs0.9.5.1. Probably the viewers don't like series with mixed stills and cine and mixed RGB with MONO


    Marcel

  • Hi jcisrisen,

    Quote

    Here are the logs for the two different options I tried:
    http://rapidshare.com/files/11844276/Server_Experiments.zip


    The +B (bit-preserving) option seems to work fine. Currently iQ-View does not support it, because dataset will not be read by the server but just dumped to disc and that's why the database dll will not get any information but I already updated the server. I could send you a Beta-Version of iQ-View 2.0.2 that supports bit-preserving if you are interested


    Regards,
    Andreas

  • Hello All.


    We had a similar problem several years ago and spent hours and hours on it.


    In short...We had a professional DICOM analyst look at images sent from the ACUSON system to GE Radstore(that removes patient name from the header, this is a research site), from there to GE Centricity archive and from the archive to the OFFIS DCMTK STORESCP. The conclusion from the DICOM specialist was that the still images were OK. The multiframe images how ever claimed to be YBR_FULL_422 but actually were RGB images.


    Our workaround was to send the images from ACUSON to RADSTORE to CENTRICITY to RADSTORE to "wherever we need them" and then all is OK.


    It seems that the CENTRICITY archive VERSION we have at the research site somehow does not do a proper job when "decompressing or what ever" when it sends the images away, but GE RADWORKS understands it and "fixes" it.


    BTW. I use Conquest archive with US machines from Toshiba, Philips/ATL, and Acuson. And it works quite well, except for the ACUSON where I had some problems with multiframe images, but it was a long time ago, the customer did not care (did not use MF) and I never investigated it.

  • Hi,


    by disabling JPEG support you force Acuson to send images uncompressed. So decompression is probably the culprit of the problem. You could try enabling JPEG support again and setting UseBuiltInDecompressor in dicom.ini to 0: this will force use of the Offis libraries for decompression - see if they can handle these images (maybe also you need a fixed dgate1412). If this works, you can also try setting IncomingCompression to "as": this will leave incoming JPEG images as is and only decompress them when transferring to another server.


    Also, if someone can reproduce the problem by dragging and dropping a compressed acuson object that would be great - and/or get us a copy of the object (before send to conquest) and the broken one (in conquest).


    Marcel

  • Hi, Maurak,


    very useful data. However, the results indicate that you did not enable JPEG support (i.e., tell acuson that you support jpeg) in dgatesop.lst. Otherwise "as" should be small. It may also be that the acuson transfer syntax is never enabled. You can try to find what it is (the log of the server should list it) and enable it in dgatesop.lst. Normally, with enabled jpeg support. it should show these lines:


    #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


    Marcel

  • hi,


    this is just a warning. Things should work fine. Be aware that the cine images are transferred uncompressed - they may be big. This is a 'feature' of conquest: only one transfer syntax is selected per client, e.g., default images are all sent uncompressed to a client.


    Marcel

Participate now!

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