Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Simplify build workflow by caching value hashes #669

Open
deltamarnix opened this issue Nov 30, 2023 · 0 comments
Open

Simplify build workflow by caching value hashes #669

deltamarnix opened this issue Nov 30, 2023 · 0 comments
Labels
Enhancement New feature or request Needs refinement issue still needs refinement V1
Milestone

Comments

@deltamarnix
Copy link
Contributor

Kind of request

Changing existing functionality

Enhancement Description

The course contains multiple steps to update the model. First, I build a model, and then I update parts of the model with separate .ini files. So I explicitly tell HydroMT which parts to update in my model. This reduces the reproducibility of the model and I think there is a solution for this.

Instead of multiple ini files, I would like to see only a single build.ini file. This file contains all the information. When hydromt build is called, it will create the model as expected, but it will also create a file that will contain per section a hash of all the information that was used to create the model. Then, when you make a small change in build.ini, call hydromt build again and hydromt will check the file with hashes to see if the hashes are still equal. If there is a slight change, it means that this section requires updating.

This would mean that you only need a single build.ini file, and that hydromt is smart enough to figure out which parts to update and which are still valid.

Use case

No response

Additional Context

No response

@deltamarnix deltamarnix added Enhancement New feature or request Needs refinement issue still needs refinement labels Nov 30, 2023
@alimeshgi alimeshgi added this to the v1.0 milestone Dec 1, 2023
@savente93 savente93 added the V1 label Jan 11, 2024
@savente93 savente93 modified the milestones: v1.0, Future Sep 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Enhancement New feature or request Needs refinement issue still needs refinement V1
Projects
None yet
Development

No branches or pull requests

3 participants