Open jbocce opened 8 months ago
FYI @pieper
Sorry for tagging you Steve, we meant to see if @dmlambo has any comment on this
Sorry for tagging you Steve, we meant to see if @dmlambo has any comment on this
Thanks, I'm very happy for someone else to investigate this. 👍
For background:
When I click on one of the error message I get to this code:
Which reference this issue thread for background:
https://github.com/dgobbi/vtk-dicom/issues/38
But I don't know why the latest changes would trigger more of those cases. Can you maybe bisect between 0.29.5 and 0.29.11 to see exactly which commit leads to the extra logging?
https://github.com/dcmjs-org/dcmjs/commit/f0dc1995f3e1d986b7e668dc4780181176e90ba6
Ah, yeah that would be my change -- it's a symptom of variable VR types, which I just found out were possible: SmallestImagePixelValue, for example.
What my change introduces is the ability to access values differently than their backing data structure, to allow PN (PersonName) type values to return dicom+json when json stringifying, and formatted strings when writing part10 dcm. As part of that change I obtain the ValueRepresentation class for the VR type and call into a function which can add the required accessors. This actually only happens with PN currently (and may indeed forever stay that way).
The good news is this doesn't affect anything; it's safe to ignore it for the time being. The bad news is the dicom standard is a bit messier than I originally thought. I'll have a look at supressing this accessor step for unknown VRs.
Using OHIF...
Not sure what is causing it. Please advise.