DICOMPULL(1)

πŸ’– DICOMPULL(1) β€” User Commands πŸ’–

okay so bestie, welcome to dicompull(1), the little icon that lives in your User Commands section and pulls DICOM files around like it's got main character energy. let's get into it 🫢


✨ NAME ✨

dicompull β€” vtk-dicom CLI πŸ’…


🌸 DESCRIPTION 🌸

🌈 usage:

dicompull [options] <directory> ...

πŸŽ€ options:

  • -L β€” follow symbolic links. this is the default, so it's already doing it, slay.
  • -P β€” do NOT follow symbolic links. opposite vibe.
  • -k tag=value β€” hand over an attribute that you wanna query and match on.
  • -q <query.txt> β€” give it a file that describes the find query.
  • -u <uids.txt> β€” give it a file that contains a list of UIDs.
  • -o <directory> β€” the directory where the files get placed. the destination, the final girl.
  • -maxdepth n β€” set the maximum directory depth.
  • -name pattern β€” set which file names to match (with * or ?).
  • -image β€” restrict the search to files that have PixelData.
  • -series β€” find all files in a series if even one file matches.
  • --directory-only β€” don't scan files for search if DICOMDIR is present.
  • --ignore-dicomdir β€” ignore the DICOMDIR file even if it is present. not me ignoring my problems 😭
  • --charset <cs> β€” the charset to use if SpecificCharacterSet is missing.
  • --silent β€” do not report any progress information. quiet queen behavior.
  • --help β€” print a brief help message.
  • --version β€” print the software version.

okay so the whole point: find dicom files in one directory and copy them to a new directory. literally that's the job. πŸ¦‹

the output directory you give with -o can use DICOM attributes, by naming those attributes within curly braces. for example, consider:

{PatientID}/{StudyDescription}/{SeriesDescription}-{SeriesNumber}

or something similar, to produce a hierarchical directory structure. nesting folders inside folders, it's giving organized. ✨

the files to be copied are specified with search keys, which take the form -k key=value where keys can either use the standard names given in the DICOM dictionary, e.g. Modality or SeriesDescription, or can be in the form GGGG,EEEE with hexadecimal group and element values. the tags can also be listed in a query file with the -q option (one tag per line). private tags should be preceded by the private dictionary name in square brackets. iykyk πŸ’œ

the values used for -k key=value can use the wildcards * and ?, and can also use date ranges of the form "19990103-19990105". yes bestie, ranges, we love a glow-up. πŸ”₯

the -u option can be used to provide a list of UIDs. provide a file where the first line of the file is the key (e.g. SeriesInstanceUID) and the rest of the file is the UIDs to match, one UID per line. πŸ“


πŸ‘‘ AUTHOR πŸ‘‘

this manual page was written by Mathieu Malaterre <malat@debian.org> for the Debian GNU/Linux system, but may be used by others. iconic of them honestly. 🫢


and that's the whole page, no notes. go pull some dicoms, bestie. πŸ’–

this was dicompull version 0.8.17, dated August 2026. periodt. πŸ’…πŸŽ€

πŸ“¦ where this page comes from