Suyash Kumar

@bbeckrest That is my understanding as well re: the size of the pixel data. Regarding the NativeFrame interface I proposed in https://github.com/suyashkumar/dicom/issues/161#issuecomment-846706345 I think it's reasonable but keeping in mind...

hi @bbeckrest! So there is another issue that may somehow be related to this (though I'm not exactly sure how or why). For files that have a weird bytesAllocated, we...

Yep, in the case you describe that is the case (though in the comment above I was referring to another issue). https://github.com/suyashkumar/dicom/issues/161#issuecomment-846706345 is where I lay out a possible interface...

Yes, this is a known behavior (see #2 for autoscale of pixel values issue). The reason it is done as it is now is to preserve the clinical data in...

There may also be value in adding a simple normalization for the `dicomutil` utility to start with

Yep, as @bbeckrest said, the second issue you're facing @bernardopericacho is #85 -- namely that lossless JPEG decoding doesn't yet have native support in Go. At some point I may...

Hi! Thanks so much for spending time on this. The current write package should probably be considered more of a "draft"--lots of tires to kick. It was a known issue...

Regarding the tests--I agree we should have some flavor of that. I'm not sure if we need to test bit-for-bit identity yet (I don't think that will pass). We do...

More details on GitHub actions artifacts: https://docs.github.com/en/actions/guides/storing-workflow-data-as-artifacts

Library functions to do these kinds of conversions (`DataSet -> tf.Example`) can live in a `convert` package.