We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
As far as I can see the DICOM Web Viewer does not handle LUT tables such as the attribute: (0028,3006)
When the attribute is read, it is done as a String and then a data.split is performed (dwv.js line: 4855)
else { if ( vr === "SH" || vr === "LO" || vr === "ST" || vr === "PN" || vr === "LT" || vr === "UT" ) { data = reader.readSpecialString( offset, vl ); } else { data = reader.readString( offset, vl ); } offset += vl; data = data.split("\\"); }
I have made a change to the following:
else { if ( vr === "SH" || vr === "LO" || vr === "ST" || vr === "PN" || vr === "LT" || vr === "UT" ) { data = reader.readSpecialString( offset, vl ); } else { if (tag.name == "x00283006") { data = reader.readInt16Array(offset, vl); } else { data = reader.readString(offset, vl); } } offset += vl; if (tag.name != "x00283006") { data = data.split("\\"); } }
This works for my image, but there could be other cases where additional work would be required.
The text was updated successfully, but these errors were encountered:
You are right, dwv does not use the LUT module. As far as I get it, the LUT data type is set by the other LUT attributes.
If you have data you can share, that would be of great help!
Sorry, something went wrong.
No branches or pull requests
As far as I can see the DICOM Web Viewer does not handle LUT tables such as the attribute: (0028,3006)
When the attribute is read, it is done as a String and then a data.split is performed (dwv.js line: 4855)
I have made a change to the following:
This works for my image, but there could be other cases where additional work would be required.
The text was updated successfully, but these errors were encountered: