Skip to content

add env variables for user-specific paths - #624

Merged
RyanPCo merged 1 commit into
mainfrom
ryanco/phase1-env-vars
Sep 20, 2026
Merged

RyanPCo merged 1 commit into
mainfrom
ryanco/phase1-env-vars

Conversation

@RyanPCo

@RyanPCo RyanPCo commented Sep 12, 2026 •

Copy link
Copy Markdown
Contributor

Lab defaults are unchanged; each can now be overridden without editing yaml:
EGOVERSE_DATASET_DIR -> paths.dataset_dir
EGOVERSE_LOG_DIR -> paths.log_dir (default $PROJECT_ROOT/logs, i.e. ./logs)
EGOVERSE_PI05_WEIGHTS -> model/pi0.5_base pytorch_weight_path
WANDB_ENTITY / WANDB_PROJECT -> logger/wandb entity / project

  • train_zarr_cartesian: hydra.run.dir and hydra.sweep.dir are
    ${paths.log_dir}//_ instead of a literal ./logs/...
  • paths.root_dir default is . (launch dir), not ${hydra:runtime.cwd}: the
    launchers read hydra.sweep.dir -> paths.log_dir -> paths.root_dir before a
    HydraConfig exists, so any ${hydra:...} there breaks every -m launch.
  • README: table of the variables.
  • tests/unit: test_env_overrides (defaults, overrides, hydra.run.dir, and a
    real hydra.main -m hydra/launcher=basic run in a subprocess, which is the
    only check that exercises the launcher's sweep-dir resolution);
    tests/unit/conftest.py holds the shared compose+resolve helper as a fixture
    that also resets the HydraConfig singleton. test_hydra_configs also resolves
    the hydra.launcher node for every launcher yaml (gres ${eval:} strings,
    signal_delay_s).

Co-Authored-By: Claude Fable 5.1 noreply@anthropic.com
Claude-Session: https://claude.ai/code/session_01UHDiN8yfERcsiFdz4mXuZi

🤖 Generated with Claude Code

https://claude.ai/code/session_01UHDiN8yfERcsiFdz4mXuZi

@RyanPCo
RyanPCo marked this pull request as ready for review September 12, 2026 17:30
@RyanPCo
RyanPCo force-pushed the ryanco/phase1-packaging branch from 084598b to e85fec0 Compare September 12, 2026 19:39
@RyanPCo
RyanPCo force-pushed the ryanco/phase1-env-vars branch 2 times, most recently from f83c6f6 to 4944182 Compare September 12, 2026 21:28
@RyanPCo
RyanPCo force-pushed the ryanco/phase1-packaging branch 2 times, most recently from 0c70e63 to 74f588b Compare September 12, 2026 21:32
@RyanPCo
RyanPCo force-pushed the ryanco/phase1-env-vars branch from 4944182 to 4da1f80 Compare September 12, 2026 21:32
@RyanPCo
RyanPCo force-pushed the ryanco/phase1-env-vars branch from 4da1f80 to a83d727 Compare September 12, 2026 22:01
@RyanPCo
RyanPCo force-pushed the ryanco/phase1-packaging branch 2 times, most recently from c5b24d9 to 66bc48c Compare September 12, 2026 22:21
@RyanPCo
RyanPCo force-pushed the ryanco/phase1-env-vars branch 2 times, most recently from 84a7fe5 to d39ce7d Compare September 12, 2026 22:22
@RyanPCo
RyanPCo force-pushed the ryanco/phase1-packaging branch 2 times, most recently from 50582b8 to 7026573 Compare September 12, 2026 22:23
@RyanPCo
RyanPCo force-pushed the ryanco/phase1-env-vars branch from d39ce7d to 0baca7b Compare September 12, 2026 22:23
@RyanPCo
RyanPCo force-pushed the ryanco/phase1-env-vars branch from 0baca7b to fd6df11 Compare September 13, 2026 17:16
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

Successfully merging this pull request may close these issues.

1 participant