I would close it because we have the DICOM property view for that. This view shows the DICOM properties with also the human readable name of the tag. In addition it shows the value slice and time resolved.
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Feed Advanced Search
Advanced Search
Advanced Search
Feb 12 2020
Feb 12 2020
Feb 2 2020
Feb 2 2020
Nightly CI looks good as well.
Jan 31 2020
Jan 31 2020
Dec 20 2019
Dec 20 2019
CI
Pushed new branch T26942-ImproveCESTPrivateTagParsing.
Despite all of the obvious flaws of the parsing code around the highlighted line linked above, the particular reason for the crash is a missing check against npos regarding the results of the find() calls. Even without a more comprehensive fix, the hex number string extraction and conversion to ASCII characters should be enhanced by checking against non-ASCII hex values.
@k656s Is the example data available on our network drives?
Dec 19 2019
Dec 19 2019
May 20 2019
May 20 2019
May 17 2019
May 17 2019
Apr 12 2019
Apr 12 2019
kislinsk edited projects for T24303: A segmentation should generate all DICOM relevant IDs as soon as it can be referenced., added: DICOM; removed Request for Discussion.
We all agree on the proposed solutions. We want to collect all segmentation related tasks in a a Segmentation project/tag.
Mar 15 2019
Mar 15 2019
kislinsk moved T26165: How to handle erroneous DICOMS/input data? from MITK Meeting to Backlog on the Request for Discussion board.
hentsch moved T26165: How to handle erroneous DICOMS/input data? from Backlog to MITK Meeting on the Request for Discussion board.
hentsch added a project to T26165: How to handle erroneous DICOMS/input data?: Request for Discussion.
Mar 13 2019
Mar 13 2019
kislinsk edited projects for T25983: Update DICOM related toolkits, added: MITK; removed MITK (2018-04-2).
Feb 6 2019
Feb 6 2019
Feb 4 2019
Feb 4 2019
Aug 6 2018
Aug 6 2018