Posts by jweste

    Hi, Marcel

    I build OHIF to use the extensions in runtime as 'umd' bundle.

    But RTStruct is not working as you already know.

    I added all extensions.

    The only way I had success to all works is building as PWA, using "yarn build".

    But, it generate many chunks in dist folder. IMHO, I don't see it as a problem
    But all extensions work wonderfull.

    Just deploy the dist folder



    great to hear. the API supports it, but the app I distribute with conquest does not have this feature. I am looking for a single json packaged version of the current OHIF (like in the app/ohif folder), but I cannot find it or directions how to make it. The offcial build instructions create quite a large folder.


    Hi, Marcel

    I sent you a message in your wall about it.

    Regards, Luiz

    I have seen you created a new function "wadoparse" to make easier wado call.

    And you did a great work in your php qido/wado webapi.

    Hi, Marcel

    This function works almost all times, but fail to conquest image "HEAD EXP2"

    [CONQUESTSRV1] Sending file : F:\Programas\AppProg\dicom150bteste\Data\0009703828\
    [CONQUESTSRV1] Image Loaded from Read Ahead Thread, returning TRUE
    [CONQUESTSRV1] JPEG decompress started.
    [CONQUESTSRV1] Debug[DecompressJPEGL]: H = 320, W = 320, Bits = 12 in 16, Components = 1, Frames = 1
    [CONQUESTSRV1] ***[JPEG Library]: Unsupported marker type 0xf7
    [CONQUESTSRV1] ***[DecompressImage]: JPEG library decompression error
    [CONQUESTSRV1] C-Get (StudyRoot)
    [CONQUESTSRV1] UPACS THREAD 503: ENDED AT: Tue Aug 23 09:09:32 2022


    I just saw conquest is ordering.

    But, The result is not sorted in OHIF. I suspect it is making other ordering in the front end.

    Some questions:

    1. Does it work to sort metadata?

    2. Is there other param to sort asc or desc?



    Thank you

    I have modified latest ohif to be called on start time with:


    Otherwise, the default is get all studies and It will overload Conquest.

    And, I intent make changes in the API to avoid overload conquest if:

    1. PatientID is not passed to API, or

    2. PatientName length is lower than NN chars or

    3. and the range StudyDateTo-StudyDateFrom is lower than DD days.

    What do you think?

    Hi, Marcel,

    Here is my latest lua script and node api.

    Now working with OHIF RTStruct with your help.

    Tested with latest OHIF code.

    I found a bug in date input range in the OHIF UI and I submited it on Git.

    But this doesn´t impact the API

    Another time, I will do a "cleanup" in the code removing unnecessary comments.

    Here is my OHIF setup. I changed since the last time I posted here.

    Hi, Marcel,

    Working!!! My God!!!!

    I sent you a PM about problem multiple images.

    If you can, please fix my code.

    OK, But I´d like a valid image to test.

    Do you has someone such as you show above?

    All images I downloaded has problem.

    A few more fixes just posted!

    Would It not be to start with "i=0"?

    And don´t I need close the boundary after each image?

    Such as:

    Hi, Marcel

    I get an error:

    *** lua run error ...xt-iclindoctor\dicomapi/api/dgate/queryfunctions.lua:77: bad argument #1 to 'write' (string expected, got nil) in 'dofile([[F:\Programas\vuejs\nuxt-iclindoctor\dicomapi/api/dgate/queryfunctions.lua]]);getinstance([[CONQUESTSRV1]],[[simpleconquestqidobridgeb1f197b57dd69deb7e626764cf53f68c]],[[1.2.840.113619.]], [[]], [[]])'

    Hi, Marcel

    I am passing the boundary right into lua function to avoid do it in node API.

    To multiple instances, I have doubt about how loop the results to add the boundary/multipart

    Is it ok?

    I got the RTSTRUCT working too in php! I'll have a look at the coding error.

    What the lua script of getinstance?