Search found 17 matches
- Fri, 2015-08-07, 16:09
- Forum: DCMTK - General
- Topic: Adding SC images to existing DICOMDIR
- Replies: 9
- Views: 9647
Re: Adding SC images to existing DICOMDIR
I guess so.. keeping back compatibility is a big issue, but the current state of the standard does not allow to include a SC image with a bit depth beyond 8, or a compressed one, losing either grayscale resolution and/or storage.
- Thu, 2015-08-06, 16:00
- Forum: DCMTK - General
- Topic: Adding SC images to existing DICOMDIR
- Replies: 9
- Views: 9647
Re: Adding SC images to existing DICOMDIR
As a final note to the post... I was (and still am) confused by a restriction in the standard that makes no sense to me. Why is not allowed for the AP STD-XA1K to add the Multiframe Grayscale WORD/BYTE Secondary Capture Image IODs? as I see they are exactly the IOD I would use to add a SC multiframe...
- Tue, 2015-08-04, 15:32
- Forum: DCMTK - General
- Topic: Adding SC images to existing DICOMDIR
- Replies: 9
- Views: 9647
Re: Adding SC images to existing DICOMDIR
My mistake... the table I should have looked at was B-3.1...
- Tue, 2015-08-04, 14:20
- Forum: DCMTK - General
- Topic: Adding SC images to existing DICOMDIR
- Replies: 9
- Views: 9647
Adding SC images to existing DICOMDIR
I´ve processed some SC images with SOPClassUID UID_SecondaryCaptureImageStorage and want to add them to a new series in an existing XA study. The TS used is EXS_JPEGProcess14SV1TransferSyntax and when I try to add the image files to the DICOMDIR in order to burn a DVD, the CheckSOPClassAndXfer(...) ...
- Tue, 2014-12-02, 16:58
- Forum: DCMTK - General
- Topic: How to efficiently read and write only DE
- Replies: 1
- Views: 2570
How to efficiently read and write only DE
I would like to know if there´s any way to read and write only the data portion of a DICOM file, that is not including any image. I am currently filling a database with information of the DICOM files and loading the whole multiframe file in memory is very time (and RAM) consuming - Hig-res multifram...
- Fri, 2013-07-05, 15:07
- Forum: DCMTK - General
- Topic: ANY-SCP in StoreSCP
- Replies: 2
- Views: 3610
Re: ANY-SCP in StoreSCP
Thanks for the exact and precise answer... and sorry for the confusion with storescp and storescu.
DICOM is so extense that I thought I missed some "wildcard" AE Title option.
Thanks again!
Juan Manuel Cena
IKON Sistemas S.A.
DICOM is so extense that I thought I missed some "wildcard" AE Title option.
Thanks again!
Juan Manuel Cena
IKON Sistemas S.A.
- Wed, 2013-07-03, 13:24
- Forum: DCMTK - General
- Topic: ANY-SCP in StoreSCP
- Replies: 2
- Views: 3610
ANY-SCP in StoreSCP
I have a little doubt... what´s the exact meaning of "ANY-SCP" in the destination AE Title of StoreSCP?. I was unable to find it in DICOM so must I assume it´s a custom solution to send it to any SCP service that´s listening on the peer's IP:Port ?
Thanks for your time.
Thanks for your time.
- Fri, 2013-03-22, 17:55
- Forum: DCMTK - General
- Topic: Possible bug in OFString::copy()
- Replies: 3
- Views: 4672
Re: Possible bug in OFString::copy()
sorry, the line shoud have been
OFBitmanipTemplate<char>::copyMem(sub->theCString, s, result); // copy the substring to s
OFBitmanipTemplate<char>::copyMem(sub->theCString, s, result); // copy the substring to s
- Fri, 2013-03-22, 17:49
- Forum: DCMTK - General
- Topic: Possible bug in OFString::copy()
- Replies: 3
- Views: 4672
Possible bug in OFString::copy()
Imay have come across a little bug in the implementation of the OFString::copy() in version 3.6.0 (ofstring.cc line 434) The referred method didn´t work as expected and when I traced it found that the copyMem function was copying the original string and not the desired substring. [code] size_t OFStr...
- Tue, 2013-03-19, 13:28
- Forum: DCMTK - General
- Topic: strange problem with network initialization
- Replies: 2
- Views: 3404
Re: strange problem with network initialization
Dear Mr Riesmeier: thank you for your flash answer.
I must apologize, it was a pointer aliasing problem in a third part library code and it was solved as soon as it was detected.
Thanks again.
I must apologize, it was a pointer aliasing problem in a third part library code and it was solved as soon as it was detected.
Thanks again.
- Thu, 2013-03-14, 13:59
- Forum: DCMTK - General
- Topic: strange problem with network initialization
- Replies: 2
- Views: 3404
strange problem with network initialization
Hi everybody! I´ve extracted the main idea fron StoreSCP (v3.6.0) in order to give my app a SCP Store service and when I execute it gives me an access violation just form the very first network function call. After some tracing I tracked the source of the problem to the line 351 in dul.cc ASC_Initia...
- Wed, 2013-01-23, 17:13
- Forum: DCMTK - Installation
- Topic: ofstream.h Cannot open include file: 'iostream.h': No such f
- Replies: 12
- Views: 21987
Re: ofstream.h Cannot open include file: 'iostream.h': No su
I finally found the reason of this error, it seems that the CMake version I´m using stores osconfig.h in a different directory than the older version I used, that is "%DCMTKROOT%\include" and left some standard almost empty osconfig.h in "%DCMTKROOT%\config\include", that was whe...
- Wed, 2013-01-23, 13:34
- Forum: DCMTK - Installation
- Topic: ofstream.h Cannot open include file: 'iostream.h': No such f
- Replies: 12
- Views: 21987
Re: ofstream.h Cannot open include file: 'iostream.h': No su
Hi everybody, I have just the same problem and it begun when updating my code from version 3.5.5 _xxx to 3.6.0. I compiled DCMTK with CMake 2.8.10.2 and after compiling I got that "fatal error C1083: cannot open include file: 'iostream.h'" message. I´m developing on VS2008 and Windows XP-3...
- Wed, 2011-01-26, 15:46
- Forum: DCMTK - General
- Topic: two issues with external Iconimages
- Replies: 5
- Views: 5608
- Wed, 2011-01-26, 15:34
- Forum: DCMTK - General
- Topic: two issues with external Iconimages
- Replies: 5
- Views: 5608
OK ... then it´s a prefix you´ve intended to use... it seems quite complicated for me to implement an iconimage that way as the sourceFileName is the file´s full path. I read the PGM specs and it states that the whitespace you can use for separating fields may be for example the newline character, b...