Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Expected prefix path #15

Open
sixy6e opened this issue Feb 13, 2025 · 0 comments
Open

Expected prefix path #15

sixy6e opened this issue Feb 13, 2025 · 0 comments

Comments

@sixy6e
Copy link

sixy6e commented Feb 13, 2025

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant