getanc produces incorrect doubled relative output path (eg. anc/anc/) when using -o with relative directories
Posted: Sat Nov 15, 2025 8:46 pm America/New_York
I would like to report a path-handling issue in getanc.
When running getanc with an output path that contains a relative directory, for example:
getanc L1B/PACE_OCI.20240913T030441.L1B.V3.nc \
-o anc/PACE_OCI.20240913T030441.anc
getanc fails with:
FileNotFoundError: [Errno 2] No such file or directory:
'/home/.../anc/anc/PACE_OCI.20240913T030441.anc.server'
I expected getanc to write to:
anc/PACE_OCI.20240913T030441.anc
But instead the tool creates a wrong doubled directory:
anc/anc/...
If -o contains only a filename (no directory), it works correctly.
If -o uses an absolute path, the problem does not occur.
OCSSW V2025.5
Ubuntu 20.04 / WSL2
When running getanc with an output path that contains a relative directory, for example:
getanc L1B/PACE_OCI.20240913T030441.L1B.V3.nc \
-o anc/PACE_OCI.20240913T030441.anc
getanc fails with:
FileNotFoundError: [Errno 2] No such file or directory:
'/home/.../anc/anc/PACE_OCI.20240913T030441.anc.server'
I expected getanc to write to:
anc/PACE_OCI.20240913T030441.anc
But instead the tool creates a wrong doubled directory:
anc/anc/...
If -o contains only a filename (no directory), it works correctly.
If -o uses an absolute path, the problem does not occur.
OCSSW V2025.5
Ubuntu 20.04 / WSL2