dicom-go / Support
dicom-go support
Setup, troubleshooting, and a direct contact for help.
Install and choose a tool
Use the public repository and the Go version required by its go.mod file, currently Go 1.22 for the root module. Optional nested codec modules can have additional runtime or build requirements.
Start with dcmdump for local inspection. Read each command's help before using a sender or receiver, because those tools operate on DICOM services and files.
Configure a connection
Check AE titles, the destination address and port, negotiated transfer syntaxes, and the target service permissions. Select transport security deliberately. The basic command-line examples are not a complete secured PACS deployment.
Receive files deliberately
storescp writes received Part 10 files to its output directory. Its default listener is 127.0.0.1:11112 and its default output directory is the working directory. Set an explicit destination and review access controls before using a different listening address.
A codec or parser fails
Include the transfer syntax UID, selected module and codec, Go version, command, and sanitized error. Optional JPEG-LS, JPEG 2000, HTJ2K, or JPEG XL paths require the relevant registered adapter. A readable dataset does not imply every pixel format can be rendered.
Prepare a reproducible issue
Use a synthetic or reviewed de-identified fixture. DICOM dumps and query output can contain patient information, and packet captures can contain complete datasets. Remove such content and credentials before attaching diagnostics.
Project documentation
Find installation details and release-specific guidance in the public project documentation.
Contact support
Contact Thales Matheus M Santos about dicom-go at thalesmmsradio@gmail.com.
Include the app or package version, your operating system, the steps to reproduce the problem, and a sanitized error message. Do not send patient information, private documents or source code, API keys, passwords, or private keys.