Activity

Jörg Riesmeier's activity

From 2017-01-27 to 2017-02-25

18:11 DCMTK Bug #618: Assocation aborted due to network timeout in storescp: After checking the DICOM standard (state machine in Part 8), the implemented state transition (see above) seems to be... Jörg Riesmeier
17:20 DCMTK Bug #618: Assocation aborted due to network timeout in storescp: Further investigations (with "storescp -ts 1" and "dcmsend +dly" trying to send a _very_ large compressed DICOM image... Jörg Riesmeier
13:54 DCMTK Bug #723 (Closed): Newer versions of Doxygen require unique section labels throughout the DCMTK man pages: In the past, Doxygen accepted the use of identical section labels for all man pages in the DCMTK (i.e. for all comman... Jörg Riesmeier
13:45 DCMTK Feature #722 (Closed): Export all (relevant) CMake options to "DCMTKConfig.cmake", some "newer" options are still missing: Currently, the file "CMake/DCMTKConfig.cmake.in" and "CMake/DCMTKConfig.cmake26.in" do not contain all relevant CMake... Jörg Riesmeier

18:24 DCMTK Feature #721 (New): Inconsistent use of ERROR and FATAL logger in command line tools: Throughout the various DCMTK command line tools, sometimes the log level ERROR and sometimes the level FATAL is used ... Jörg Riesmeier
18:15 DCMTK Bug #388 (Closed): DICOMDIR causing a crash in the destructor of DcmDicomDir: Fixed with commit 246cbe6. Jörg Riesmeier

18:27 DCMTK Bug #565: setXXX() method should consider the SpecificCharacterSet value: dcmrt will not be touched anymore for the 3.6.2 release, at least not for fixing the described issue. Jörg Riesmeier
14:31 DCMTK Conformance #695 (Assigned): Check whether Non-Patient Object Storage SOP Classes should be treated differently: Jörg Riesmeier
14:31 DCMTK Conformance #695: Check whether Non-Patient Object Storage SOP Classes should be treated differently: See Commit d8dcde0 (Allow for sending non-patient DICOM objects). Jörg Riesmeier

17:07 DCMTK Conformance #695: Check whether Non-Patient Object Storage SOP Classes should be treated differently: The first two commits in this regard are 1093ead and a2bf7a6.
Of course, there is more work to be done, e.g. dcmIs... Jörg Riesmeier

18:03 DCMTK Conformance #702: Supplement 195 adds two new Transfer Syntaxes (HEVC/H.265): Now, also movescu's --accept-all option supports the two new transfer syntaxes (see commit 781db52). Jörg Riesmeier

19:11 DCMTK Conformance #644 (Closed): Supplement 180 adds three new MPEG-4 transfer syntaxes: See commit c03fccd. Jörg Riesmeier

16:21 DCMTK Bug #391 (Closed): valgrind reports "invalid read" when calling gethostbyname(): See commit 18e429f and 105f4c2. Jörg Riesmeier
11:36 DCMTK Conformance #717 (Closed): CP-1653: Clarify Photometric Interpretations Permitted for Decompressed and Compressed Transfer Syntaxes: Check whether the DCMTK correctly handles Photometric Interpretation as clarified in this CP.
Also note that it is p... Jörg Riesmeier
11:08 DCMTK Conformance #716 (Closed): CP-1678: Use of JPEG Family Transfer Syntaxes rather than RLE for YBR_FULL: Check whether the DCMTK correctly handles the YBR_FULL color model:
*Rationale for Correction*
Traditionally,th... Jörg Riesmeier

17:38 DCMTK Bug #646: storescu/scp crash in debug mode when using association negotiation profiles: Also dcmrecv crashes in debug mode when started without --config-file, i.e. without an association negotiation profil... Jörg Riesmeier
14:39 DCMTK Bug #715 (Closed): gethostbyaddr() is obsolete and should be replaced by getnameinfo(): Both on Linux and Windows the gethostbyaddr() function is marked as obsolete or deprecated and should, therefore, be ... Jörg Riesmeier
14:35 DCMTK Bug #714 (Closed): gethostbyname() is obsolete and should be replaced by getaddrinfo(): Both on "Linux":http://man7.org/linux/man-pages/man3/gethostbyname.3.html and "Windows":https://msdn.microsoft.com/de... Jörg Riesmeier
14:00 DCMTK Bug #391: valgrind reports "invalid read" when calling gethostbyname(): Also remove call to gethostbyname() in "dcmnet/include/dcmtk/dcmnet/dcompat.h"? Jörg Riesmeier
13:44 DCMTK Bug #380 (Closed): (Possibly) problematic warnings (gcc 2.95.3): Not relevant anymore since the compiler (gcc 2.95.3) is more than 15 years old and the warnings, if still problematic... Jörg Riesmeier

Also available in: Atom