Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error while trying to parse valid dicom file #37

Closed
vampolo opened this issue May 18, 2020 · 5 comments
Closed

Error while trying to parse valid dicom file #37

vampolo opened this issue May 18, 2020 · 5 comments

Comments

@vampolo
Copy link

vampolo commented May 18, 2020

Hi,

I have this valid dicom file. i tried to run the simple program in the readme but i receive the following error:

Error: ReadValue(ParseFloat(ParseFloatError { kind: Invalid }))

at the line

let obj = open_file("949559.dcm")?;

What can it be?

@Enet4
Copy link
Owner

Enet4 commented May 18, 2020

Thank you for reporting. Would you like to try that again with the upstream version in the master branch? I just opened that file using the project's dcmdump binary without errors.

@vampolo
Copy link
Author

vampolo commented May 18, 2020

The one from master seems to work. Are you considering publishing an update?

@Enet4
Copy link
Owner

Enet4 commented May 18, 2020

I'm afraid I don't have an estimated date for a new release yet. It depends on how many things I wish to include in the next version. Still, considering the growing interest in the project and the fair amount of goodies already pending a release, this will weigh in on the decision. Feel free to watch the repository for releases.

@Enet4
Copy link
Owner

Enet4 commented May 21, 2020

Closing, as the original problem had already been fixed upstream. There are also plans for #12, which would "post-pone" value decoding errors to a later stage and prevent a single value from breaking the file reading process.

@Enet4 Enet4 closed this as completed May 21, 2020
@Enet4
Copy link
Owner

Enet4 commented May 24, 2020

Just letting you know that version 0.2.0 has just been released with the fixes described here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants