Linux workstation

Upstream software project

octave-dicom

Dicom processing for Octave

About octave-dicom

Dicom processing for Octave

This project links 3 native package records across 3 recorded operating-system releases. Compare the retained versions and architectures below, then open the package for your own release.

These are catalog observations, not a guarantee of installation, compatibility, or upstream support.

Project pictures and package coverage

Debian 13 (Trixie): 1 package records; Fedora 43: 1 package records; Fedora 44: 1 package records. Catalog coverage diagram, not an application screenshot.octave-dicom: recorded package coverageDebian 13 (Trixie)1 recordsFedora 431 recordsFedora 441 records
OpenFactory diagram of linked package records. It is not an application screenshot.

Project identity

Project
octave-dicom
Publisher
Not authoritatively mapped
Native package records
3
Operating systems
debian-13, fedora-43, fedora-44
License expression
GPL-3.0-or-later
Metadata completeness
100/100 (not a software quality rating)
Source repository
Not reported

Source-reported description

The fullest retained description is shown with its source. Distribution packaging descriptions may include downstream details.

The Octave-forge Image package provides functions for processing Digital communications in medicine (DICOM) files.

Description source

Packages by operating system

Compare recorded versions, then open a package for dependency, file, checksum, and repository evidence. Version strings are distribution-specific, not a ranking of newer software.

Debian 13 (Trixie)

  1. octave-dicom

    Debian 13 (Trixie) / math

    0.6.1-1

    manipulate DICOM files in Octave

    amd64arm64trixie

Fedora 43

  1. octave-dicom

    Fedora 43 / Unspecified / source octave-dicom

    0.7.3-1.fc43

    Dicom processing for Octave

    aarch64x86_6443

Fedora 44

  1. octave-dicom

    Fedora 44 / Unspecified / source octave-dicom

    0.7.3-1.fc44

    Dicom processing for Octave

    aarch64x86_6444

Project resources and further reading

Mapping provenance

Only source-backed identity signals create public cross-OS links. A reviewer can later approve or dispute an inferred relationship without rewriting native package history.

No field-level source record is published yet.