Good afternoon, Marcel!
More and more often we come across studies that we cannot upload to conquest. I will attach examples.
Could you recommend how to fix it?
Good afternoon, Marcel!
More and more often we come across studies that we cannot upload to conquest. I will attach examples.
Could you recommend how to fix it?
I will have a look. It may be a SOP that is not enabled in dgatesop.lst. What version are you using?
Marcel
Hi,
the one image (written from radiant) has a group 2 header that is explicit,as it should be, followed by a three more group 2 items (out of order) that are implicit. My dicom parser expects all of group 2 items to use explicit coding and loses synchronisation on these. I severly doubt that it conforms to the standard. The other image (without extension), fails in parsing the image data. I have not yet been able to debug that, my next step is to accept image data parsing errors when NoDicomCheck=1.
Marcel
That works for study2, but I cannot release the change as I am travelling. Does the image in study1 load in other packages?
Marcel
I will have a look. It may be a SOP that is not enabled in dgatesop.lst. What version are you using?
Version Conquest 1.5.0e.
SOP from the study is enabled in dgatesop.lst.
That works for study2, but I cannot release the change as I am travelling. Does the image in study1 load in other packages?
Marcel
These files are opened/loaded in RadiAnt DICOM Viewer and some other viewers.
Hi Marcel,
maybe also related to this issue.
Unconfirmed bugs:
U4) Random ***No valid presentation contexts/transfer syntax found in 0 candidates, in dicomget from web interface
I am additionally getting:
when using conquest as DICOM proxy and executing dicomquery from PACS with lua. The lua actually writes out:
It is also random. I cannot reproduce it for specific dataset because the second execution on the same data works fine. I noticed this after migration from 1.4.19b to 1.5.0d.
A test script would be good. It can be run for a long time.
And is there any difference between an external webserver or the buil-in webserver?
Marcel
So, study 1 is not valid DICOM. I can, however, make study 2 a warning rather then an error.
Marcel
So, study 1 is not valid DICOM. I can, however, make study 2 a warning rather then an error.
Marcel
Yes, it would be nice to change it to "warning".
Many studies come from devices from Siemens with such a problem.
Is there anyway I can change this myself?
Compiling it is hard, I will update on github next week.
Marcel
Unless you are on linux.
We use windows version.
Don’t have an account yet? Register yourself now and be a part of our community!