mise API - v0.0.0
    Preparing search index...

    Function path_physical

    • The address the bytes actually live at.

      A path can name a file three times over: the logical place a listing shows it (/home/me/feeds/feed_42/pl-dircopy_1/data/...), the projection the graph gives for the same place (/proc/jobs/feed_42/pl-dircopy_1/data/...), and the physical file CUBE stores. A pl-dircopy of a PACS pull is the case where all three differ: its output folder is a LINK, and the DICOM under it is stored beneath /SERVICES/PACS. Reading the logical name got no file id, so every slice of a pulled series was unreadable from the feed it was pulled into — a listing that shows what it cannot open — while the same series read fine at its PACS address, and cd into the folder (which does follow links) made the very same command work.

      So the address is resolved before anything is read: a projection through the provider that owns it, then the link walk the rest of the file commands already do. A path that resolves to nothing stands as it was, so a bad path still refuses by its own name.

      Parameters

      • input: string

        The path as the operator or a surface gave it.

      Returns Promise<string>

      The physical path, or the input when it resolves no further.