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
Build metadata has no inputs and is thus build initially and only once. This is no problem when starting from a clean working directory.
When the working directory is not clean and the model is rebuild, that may be a problem. As an example, one could build euro-calliope v1.0 and receive the correct build metadata. One could then update the configuration parameters and re-execute the model, without build metadata being updated leading to an inconsistent build-metadata.yaml. We need to automatically trigger a rebuild in these cases.
The text was updated successfully, but these errors were encountered:
Good idea. Currently, that's not possible because the metadata is part of the model. But we could change that and yes, that sounds like a good idea.
The disadvantage is that we likely have to move metadata then into the resolution-specific folder and have several copies of it. Otherwise the trigger is weird and can become inconsistent.
Build metadata has no inputs and is thus build initially and only once. This is no problem when starting from a clean working directory.
When the working directory is not clean and the model is rebuild, that may be a problem. As an example, one could build euro-calliope v1.0 and receive the correct build metadata. One could then update the configuration parameters and re-execute the model, without build metadata being updated leading to an inconsistent
build-metadata.yaml
. We need to automatically trigger a rebuild in these cases.The text was updated successfully, but these errors were encountered: