View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0004314 | Slicer4 | Module DICOM | public | 2016-12-08 16:49 | 2020-03-04 11:56 |
Reporter | attila | Assigned To | pieper | ||
Priority | normal | Severity | minor | Reproducibility | always |
Status | resolved | Resolution | fixed | ||
Platform | x64 | OS | Windows 10 | OS Version | 10.0.14393 |
Product Version | Slicer 4.6.1 | ||||
Target Version | Fixed in Version | Slicer 4.11.0 | |||
Summary | 0004314: When a non-ASCII character exists in the path a DICOM cannot be opened if only links are imported | ||||
Description | When importing a DICOM into the DICOM database, the user has to choose if the data or only links should be added to it. After clicking OK, the error popup is dismissed and the Processing... window pops up but it effectively stays at 0% as long as it is cancelled. See the Python output in the "Additional information" If DICOM data is imported, not just the links are added, then things work as expected. Also if the non-ASCII characters are removed from the path then after deleting and re-importing the same DICOM series, data can be loaded even if "Add link" is selected. | ||||
Steps To Reproduce | 1.) Import any DICOM (I downloaded one example dataset from imaging.nci.nih.gov but the problem does not depend on the data) | ||||
Additional Information | In the Python console it reads: Python 2.7.11 (default, Nov 7 2016, 23:29:25) [MSC v.1800 64 bit (AMD64)] on win32
See python console for error message. | ||||
Tags | No tags attached. | ||||
I can replicate this issue on my windows 10 computer based on the steps provided. |
|
Possible solution: It would be good to move the SlicerWizard utility code that uses the chardet python package into the main slicer.util space so that it could be used in dicom plugins. https://github.com/Slicer/Slicer/commit/b9aec1d2058c49e979d6e94dedf5e46c1e7d79cc |
|
Fixed in recent preview releases (for example, Slicer-4.11.0-2020-03-01 - revision 28798). See https://discourse.slicer.org/t/slicer-switches-to-utf-8-everywhere/10374. |
|
Date Modified | Username | Field | Change |
---|---|---|---|
2016-12-08 16:49 | attila | New Issue | |
2016-12-08 16:49 | attila | Status | new => assigned |
2016-12-08 16:49 | attila | Assigned To | => pieper |
2016-12-08 19:04 | pieper | Note Added: 0014269 | |
2016-12-08 19:04 | pieper | Status | assigned => confirmed |
2016-12-08 19:08 | pieper | Note Added: 0014270 | |
2016-12-09 10:56 | pinter | Relationship added | related to 0004156 |
2020-03-04 11:53 | lassoan | Status | confirmed => resolved |
2020-03-04 11:53 | lassoan | Resolution | open => fixed |
2020-03-04 11:53 | lassoan | Fixed in Version | => Slicer 4.11.0 |
2020-03-04 11:53 | lassoan | Note Added: 0016326 | |
2020-03-04 11:56 | lassoan | Relationship added | has duplicate 0003999 |