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

Rerun with additional forward models without having parameters.txt overwritten #4571

Closed
rnyb opened this issue Jan 6, 2023 · 5 comments
Closed
Labels

Comments

@rnyb
Copy link

rnyb commented Jan 6, 2023

Is your feature request related to a problem? Please describe.
As a user I often need to add new forward models without having to rerun everything. This is mainly done to save time (a HM run can take hours - days to fully rerun), but can also be relevant for older cases that is hard to rerun fully. However, when doing this the parameters.txt file (and STATUS file) is overwritten. This is an unwanted situation and the user needs to make creative solutions to avoid it.

Describe the solution you'd like
There should be an option for the user to easily rerun parts of workflow without having the parameters.txt file overwritten.

@rnyb rnyb added the feature label Jan 6, 2023
@rnyb
Copy link
Author

rnyb commented Jan 6, 2023

One suggestion could be to never write parameters.txt if neither GEN_KW nor DESIGN2PARAMS is present in the ERT model file.

@oyvindeide
Copy link
Collaborator

oyvindeide commented Jan 27, 2023

Hi, sorry for being slow to respond. Today the parameters.txt will be backed up if it already exists, but I guess that is not the feature you are asking for?

@rnyb
Copy link
Author

rnyb commented Feb 17, 2023

Hi, sorry for being slow to respond. Today the parameters.txt will be backed up if it already exists, but I guess that is not the feature you are asking for?

Correct. The backup file is great on it's own, but that is not what is requested here. The idea is to be able to avoid user specific copy hacks to get back original state.

@oyvindeide
Copy link
Collaborator

One suggestion could be to never write parameters.txt if neither GEN_KW nor DESIGN2PARAMS is present in the ERT model file.

We could probably not write it when there are no GEN_KW in the model, but ert as such does not really know that DESIGN2PARAMS exists, so would be hard to account for that. That highlights the main problem, we dont know if there are other forward models that rely on this file existing, which means removing it will probably cause a lot of problems.

@oyvindeide
Copy link
Collaborator

I think long term the best solution is to make design matrix natively supported #4656, so will close this issue, and we can bring it up again later.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants