Closed chielmi closed 2 months ago
Thanks for the report! This sounds more like a bug in the condition parser itself. I actually can see that there is a check missing. It would be helpful if you could provide the test file (or an anonymized version that still shows this error) to understand when this error occurs.
Thanks for the quick reply! I get this error for any DICOM file, even for the ones that I know don't contain any issues. Also I have the exact same error when I run validate_iods.exe in an Ubuntu VM.
Perhaps it's an issue in the latest version?
Perhaps it's an issue in the latest version?
Could be - would be a bit awkward if no test did catch this... Can you please check with the previous version 0.6.0 (it also has the executable)? I will certainly have a look later today.
You are spot on! I can confirm that 0.6.0 works fine, I only have the issue with 0.6.1!
Right - I just tried it locally, and it is indeed a regression in 0.6.1. Sorry for that... You can use version 0.6.0 until I fix that.
All clear, indeed I'll use the prior version for now. Thanks again for the fast confirmation!
A new patch release with a fix is out.
For my own reference: this was not caught because the tests had been run with the 2023c DICOM standard, while the problem only occurs since 2024a. In a few conditions, a link had been introduced into the condition text instead of the previous text, and as the link is removed during processing, the resulting (incomplete) sentence led to the error due to a change in parsing in 0.6.0. We shall always use the latest standard for testing...
Let me start with saying thanks for creating the packaged Windows executables version 0.6.1 for dump_dcm_info.exe and validate_iods.exe!
Unfortunately they don't work for me. When running these I get an unhandled exception when docbook files are created for the first run. I can see the files being downloaded to the docbook directory, so it doesn't seem to be a permission issue:
Any suggestion on what I'm doing wrong here?