Skip to content

Conversation

pabloitu
Copy link
Collaborator

refac: changed forecast registry abstraction. i) renamed to model reg…istry for clarity (ii) Registries' main job is to provide global access to Object keys (model forecasts, input catalog and arguments file), build the key structure (for instance, the path tree) and check if these objects already exists (iii) current (ModelFileRegistry) and future (ModelHDF5Registry, ModelSQLRegistry) concrete classes are abstracted from ModelRegistry, which has the defined interface.

…istry for clarity (ii) Registries' main job is to provide global access to Object keys (model forecasts, input catalog and arguments file), build the key structure (for instance, the path tree) and check if these objects already exists (iii) current (ModelFileRegistry) and future (ModelHDF5Registry, ModelSQLRegistry) concrete classes are abstracted from ModelRegistry, which has the defined interface.
@pabloitu pabloitu linked an issue Apr 29, 2025 that may be closed by this pull request
…used in file-base registries. Created ExperimentRegistry abstract and File-based concrete classes. Renamed registries' interface to add/get_*_key. abstracted registry logging to be a function in the logger module.

tests: added unit tests for experiment file registry
@pabloitu pabloitu merged commit 2e8c9eb into main May 27, 2025
7 checks passed
@pabloitu pabloitu deleted the 53-correct-management-of-models-input-catalog-and-arg-files branch June 2, 2025 13:30
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.

Correct management of model's input catalog and arg files
1 participant