Fix Hydra config loading to support custom config paths and prevent reinitialization errors #101
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR updates the
build_sam2()function to use Hydra’s recommendedinitialize_config_dir()pattern, resolving configuration loading issues and enabling flexible, reusable model initialization.✅ Key Changes:
compose()-only approach withinitialize_config_dir()to support loading configs from custom local paths (config_root).GlobalHydra already initializedruntime errors.📌 How can this help:
Custom Config Support:
The original code assumed Hydra could locate the config via its default search path, which failed for local or container-mounted configs. This change enables users to explicitly specify the root directory for config files.
Hydra Reinitialization Error Fix:
In scripts or interactive sessions (e.g., notebooks, demos), Hydra throws a
GlobalHydra is already initializederror when reused. This patch handles such cases safely.Improved Portability:
The updated implementation ensures reliable config loading across environments, including containers, distributed jobs, and non-Hydra CLI contexts.