You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Issue: Implement YAML Configuration for Dynamic Model and Ensemble Paths (Directories and Scripts)
Description
Implement four YAML configuration files to dynamically set up directories and scripts within the ModelPath and Ensemble classes.
The point is to have files that determine which model-specific dirs can be accessed as attributes by the ModelPath and EnsemblePath respectively. This ensures we don't have to change the script of the class if we decide to change something in the models-specific dirs.
This approach will also ensure that there is a clear separation between models and ensembles and between directories and scripts, streamlining configuration management and making the code more adaptable.
Note that the root level dirs are still expected to be had coded in the two path classes. This issue only pertains to the model-specific dirs and configs.
Details and Requirements
YAML Files:
Add the following YAML configuration files to common_configs:
model_dirs.yaml: Contains directory paths specific to each model.
model_scripts.yaml: Contains script paths specific to each model.
ensemble_dirs.yaml: Contains directory paths for ensemble models.
ensemble_scripts.yaml: Contains script paths for ensemble models.
Dynamic Attribute Creation:
Use _initialize_directories() and _initialize_scripts() to parse these files and set attributes dynamically.
Class attributes generated from the YAMLs should use snake_case formatting.
Issue: Implement YAML Configuration for Dynamic Model and Ensemble Paths (Directories and Scripts)
Description
Implement four YAML configuration files to dynamically set up directories and scripts within the
ModelPath
andEnsemble
classes.The point is to have files that determine which model-specific dirs can be accessed as attributes by the ModelPath and EnsemblePath respectively. This ensures we don't have to change the script of the class if we decide to change something in the models-specific dirs.
This approach will also ensure that there is a clear separation between models and ensembles and between directories and scripts, streamlining configuration management and making the code more adaptable.
Note that the root level dirs are still expected to be had coded in the two path classes. This issue only pertains to the model-specific dirs and configs.
Details and Requirements
YAML Files:
Add the following YAML configuration files to
common_configs
:model_dirs.yaml
: Contains directory paths specific to each model.model_scripts.yaml
: Contains script paths specific to each model.ensemble_dirs.yaml
: Contains directory paths for ensemble models.ensemble_scripts.yaml
: Contains script paths for ensemble models.Dynamic Attribute Creation:
_initialize_directories()
and_initialize_scripts()
to parse these files and set attributes dynamically.snake_case
formatting.Examples of something like this can be found here: https://github.com/prio-data/views_pipeline/tree/simon_stabs_at_path_stuff
logger
for basic error handling, ensuring any parsing issues with YAML files are captured and logged._initialize_directories()
and_initialize_scripts()
for easy troubleshooting.Example YAML Structure:
Tasks
model_dirs.yaml
andmodel_scripts.yaml
for model-specific paths incommon_configs
.ensemble_dirs.yaml
andensemble_scripts.yaml
for ensemble-specific paths incommon_configs
._initialize_directories()
for directory paths._initialize_scripts()
for script paths._initialize_directories()
and_initialize_scripts()
for any YAML parsing errors.Labels
enhancement
,yaml
,configuration
,logging
,error-handling
The text was updated successfully, but these errors were encountered: