DICOM @ OFFIS

I have observed that canWriteXFer() should be called before chooseRepresentation. Additionaly, you should make sure that the pixeldata is really loaded. By default, only tags with length < 4096 are loaded into memory.

HTH

Markus

You have to register the JPEG Codecs when your SCU starts up:
regards

Markus

I think you mean the "*.raw" file. Your assumption is correct - the +W option extracts the raw pixeldata to the file. There may be many reasons why the DICOM image is displayed differently from the raw data. Envision that all information about how the image has to be displayed still reside...

Format for date-span in DICOM:

20070701-20070731

The answer to this question heavily depends on which level shall be used to settle the query on. One possible solution is to write a new implementation for the WlmDataSource (wlds.h) interface. The solution I implemented does not use the dcmwlm code at all but simply starts a DIMSE_findProvider. You...

You will not get it to work, unless you change some code. Probably the easiest way to get that working is to modify the request dataset after it has been received and before executing the query on the datasource (filesystem). This change would apply to the method FindCallback() in wlmactmg.cxx. A be...

In addition to that, I think that '*' as a wildcard is not supported by the OFFIS. I am quite sure that a '*' in (0x0010, 0x0020) PatientID would cause no matches to be found. I suggest that you leave the attributes (e.g. (0040,0001)) completely blank in your request if you want any of the records t...

Eduardo,

as your worklist query is matched against the files in the worklist directory, it would help to see a dump of the worklist file (/home/dicom/WWW/worklist/data/WORKLIST_US/wl141.wl) as well.

Regards

Markus

What you could do is use the bit-preserving mode when receiving the file and afterwards open and load it. By default, all attributes smaller than 4096 bytes will be loaded into memory, the others are loaded transparently on demand when they are accessed. As the file was just received, it is very lik...

When you disable the --fork option, you cannot handle more than one association at a time.

Did you try the patch?

Hm, this does not sound like a dcmtk-related problem. Generally, a cool tool named visual leak detector can help you to find memory leaks. If you want to try it, look here:

http://www.codeproject.com/tools/visualleakdetector.asp

Thank you very much, Marco! This really helps me out. However, such a log is possible with a brilliant ;-) piece of code like this one: DcmDataset* poDataset = new DcmDataset; DcmSequenceOfItems* poSPSSeq = new DcmSequenceOfItems(DCM_ScheduledProcedureStepSequence); DcmTag oTag(0xfffe, 0xe000, EVR_S...

Jörg,

thanks for replying at all. It is not easy to provide sample code, for it is scattered all over the project (Dataset handling, Worklist Service, ...), but I will try.

Best regards

Markus

No ideas???

You might have a look at my post:

viewtopic.php?t=1051&start=0&postdays=0 ... highlight=

It might help to try that patch. It worked perfectly in a similar situation for me. Please let us know if it solved your problem as well.