Markus D. Herrmann

> > I think it would be great to have that class implemented in pydicom so that we can just import it in highdicom > > It seems reasonable to...

> Could you elaborate on what the issue is and what changes you'd like? It doesn't seem terribly reasonable to remove tooling that allows storage to and from a json-like...

> having the FrameReader class and associated functions in its own module makes the library more readable overall The problem with the term `FrameReader` is that is doesn't make clear...

@kalebdfischer I suggest implementing the API of the [highdicom.io.ImageFileReader](https://highdicom.readthedocs.io/en/latest/package.html#highdicom.io.ImageFileReader) class. I am all for improvement of implementation details, but our goal is to avoid duplication of functionality between *pydicom* and...

@garhiaNfer thank you for your interest in Slim and for reporting the issue. Unfortunately, I do not fully understand the problem you are experiencing. Could you kindly elaborate on what...

Ah..I see. Thank you for the clarification. For complex geometries (RECTANGLE, POLYGON, etc.), we compute the centroid of the geometry and render the individual point. So, the fact that only...

@igoroctaviano that's awesome! Thank you for your efforts. To @garhiaNfer's point, I suggest ultimately always keeping Graphic Type POLYGON, even if the graphic data are rendered as points at lower...

@nwey thank you for your interest in Slim and for bringing this issue to our attention. It appears that you are asking three questions: 1. Does Slim support decoding of...

Can you please try with the latest v0.13.0? That version now includes the debug information and error reporting features.

Potentially related to https://github.com/ImagingDataCommons/slim/issues/124