Posts by marcelvanherk

    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,


    can you give me help to get mysql running as easy as possible on debian. Then I can try help you out. As far as ODBC with MySql goes I only have the very old doc by Paolo Marchesi (appendix 2?). I prefer to skip odbc as far as possible. I will make the mysql download as suggested.


    Marcel

    For NATIVE mysql support (ODBC not used):


    WINDOWS: You need to use the mysql client dll of 5.022 (that what's dgate and the GUI are compiled against) even if you are using a newer mysql server . I wanted to redistribute the file but got no clear reply from the MySql representative that it was allowed. The PDF is in dicomserver1412.zip


    LINUX: your attempts look good - only I think DoubleBackslashtoDB should be 1 (minor issue). Don't know what is the problem opening the database. Any clue in the compile time messages?


    Marcel

    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

    The only manual is dgate -?. This listing is also printed in conquestpacs.pdf. For more info you will have to look at the implementation in dgate.cpp in dgate1412.zip starting at line 8386. :) Here commands sent from another 'dgate --xxxx" are processed. Around line 3585 the older commands 'dgate -x' are processed.


    Marcel

    cache is r/w
    jukebox is read only copy,
    so at one time data will be the same
    after verify cache will be deleted


    Seems like the only safe way to burn a DVD to me.


    I do not understand the other issue? We burn on a timer using a separate app that runs when disk space is low.


    Marcel

    Hi BookWorm,


    I am suprised that the hard path was a problem - that is only there for WIN32. Please mail me the changed file. Are you using 1.4.12 and mysql 5.0.22? The connect code is in odbci.cpp, have a look there.



    Marcel

    Files dropped into the conquest server will be copied to the first MAG device with enough space. Drag and drop behaves the same as a network transfer into the server. There is no way to control in which MAG device images are stored.


    Marcel

    Since there has been some discussion about the validity of the private NKI compression (see topic Conquest and Ultrasound), here are my views.


    NKI compression is an old and well tested feature of the Conquest DICOM server. We use it to store TB's of information. The compression ratio and speed are quite OK.


    It is totally transparant for clients accessing conquest over the network, guaranteed error free, and safe to use.


    Also (when set in acrnema.map) it can set as transfer syntax to transfer data from one server to another. This is OK for Conquest to Conquest transfers but should NEVER be done for transfers from Conquest to non-Conquest clients.


    The compressed data is saved in a private TAG if possible. If not, the images are not compressed and remain valid.


    Files stored by Conquest under NKI compression are NOT DICOM COMPLIANT and are unreadible for other software. Originally, it was not possible to store NKI compressed images with the .dcm extension (set with FileNameSyntax), but only with the .v2 extension (raw VR dump). That the combination of .dcm and NKI compression is now possible can actually be considered a bug - .dcm files must be DICOM compliant. Since version 1.4.12b, the nki compression is disabled for .dcm files.


    If you store data with NKI compression, you will need to keep the a version of the Conquest software running indefinitively to be able to read the data (or reuse our code in nkiqrsop.cxx).


    As David Clunie mentioned, a better way to implement NKI compression is a private transfer syntax. We will consider this change, but it has a lot of implications for the code.


    Marcel