Skip to content

Expected prefix path #15

@sixy6e

Description

@sixy6e

Specifying a base output directory via:

--output-base fails when specifying a path that is different to the internally defined expected path.

File "/g/data/yp75/projects/eo-auxiliary/fetch/fetch2/brdf.py", line 74, in get_working_dir
  raise ValueError(
ValueError: Expected path to start with '/g/data/v10', but got '/g/data/yp75/projects/eo-auxiliary/BRDF/MCD43A1.061/2023.12.31'

Is it a design requirement to have the expected path, or can it be more flexible?

The working space should be hidden under the specified output path (if provided). That should preserve the integrity as outlined by this comment. And no assumptions are needed (presumably) at that point in being on the same drive.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions