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
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
The text was updated successfully, but these errors were encountered:
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
The text was updated successfully, but these errors were encountered: