Fix python bindings ESmry, start date #4509
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR fixes handling of daylight-saving time when importing start date from a summary file (and ESMRY) using python bindings.
Consider the following example. Start date is set in the data deck.
When running this deck with OPM Flow, the following is saved to the SMSPEC file
So far, all good.
However, when using the following python script to import start date from the summary file
results are as following
This is not as expected. As could be seen, this is one hour shifted relative to the input and to what is stored in the SMSPEC file.