smikitky / vscode-dicom-dump Goto Github PK

Add a link to export any binary data (including Pixel Data (7FE0,0010)) to a file, so that one can use hexdump or a similar tool to investigate its contents.

Although originially my dicom files did not have any extension at all, adding .dcm or .dicom does not result in the context menu options. When I load the files, I get the default warning the file is not displayed because it's binary or has an unsupported encoding. Opening it anyway, or not, both don't result in the context options. Through dicom-parsers online demo it seems like there's nothing wrong with the files (all other tooling we have handles them fine too).

I restarted vsc and reinstalled the plugin a few times, no dice.

I use VSCodium, would that make a difference? It hasn't for any other plugin I use so far...

This is not issue. just request.

dicom.showPrivateTags is set true, (odds,00XX) tag is known as Private Creator, VR LO.
But still ?? ? = <binary data of length: are displayed.

I understand dicom.dictionary doesn't handle Private Creator. so this is skipped.

extractor.ts line# 149 around. findTagInfo(). add follows to show Private Creator.

if(/[13579bdf]/i.test(tag[4])/*isPrivateTag*/ && tag.substring(5, 7) === '00') { return { name: 'PrivateCreator', vr: 'LO'}; }

Like .dcm and .dicom, worklist files also have a DICOM structure and should be dumped to text/JSON files. The current workaround is to change the .wl file extension to .dcm.

Doing Kaggle.com on RNSA and wanted to view dicom data in visual basic.

Found your code while searching for a vb.net viewer/decoder.

Added and installed in VS code - latest version. Anytime I come near you code it locks up system - eventually message to reopen window. Have not tried installing in Visual Studio.

Should it work in VS Code ? It certainly seems to install there ok.

The image data can be displayed in the Java link you supplied - so they are good.

microsoft/vscode#48034

See: https://code.visualstudio.com/api/working-with-extensions/bundling-extension

Currently this extension cannot handle Korean characters (Hangul). What DICOM standard says is as follows:

• Use KS X 1001 character set, formerly known as KS C 5601 and registered as ISO-IR 149
• Use ISO-2022-KR encoding which uses escape sequences
  • G0 set ESC 02/04 02/08 04/03
  • G1 set 01/11 02/04 02/09 04/03 or ESC $ ) C (i.e., "Use Hangul from here")

The problems is that ISO-2022-KR is a very rare encoding and I cannot find a pure-JS decoder for that. Seemingly EUC-KR is very similar, and CP949 is a superset of EUC-KR. A hacky solution would be to just decode the text with CP949 and remove the 4-byte escape sequence using regex. This works at least in this example, but I don't know if it's the right approach.

https://code.visualstudio.com/updates/v1_56#_define-whether-your-extension-supports-a-virtual-workspace