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.

Sign up for GitHub

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

Jump to bottom

Mixed casing in summary file names #10720

Closed
magnesj opened this issue Oct 16, 2023 · 3 comments · Fixed by #10738
Closed

Mixed casing in summary file names #10720

magnesj opened this issue Oct 16, 2023 · 3 comments · Fixed by #10738
Labels
BugInRelease Bug in an official release
Milestone
Maintenance 2023 ...

Comments

@magnesj
Copy link
Member

magnesj commented Oct 16, 2023 •
edited
Loading

A case is exported from Intersect resulting in mixed casing on disk my_case.SMSPEC and my_case.EGRID
When importing data into ResInsight, import of EGRID and UNRST data works as expected
It is not possible to import summary data with mixed casing
Renaming to MY_CASE.SMSPEC and MY_CASE.UNSMRY will import the data correctly.

The mixed casing should work for both libecl and opm-common file reader, and should work for both single case and ensemble case.

Related issues

#8385
#10617
#3009

4e51516
@magnesj magnesj added the BugInRelease Bug in an official release label Oct 16, 2023
@magnesj magnesj added this to the Maintenance 2023 - Sprint 10 milestone Oct 16, 2023
@kriben
Copy link
Collaborator

kriben commented Oct 16, 2023

Related to #10617?

@magnesj
Copy link
Member Author

magnesj commented Oct 20, 2023

#3009

@magnesj
Copy link
Member Author

magnesj commented Oct 20, 2023

4e51516

kriben added a commit that referenced this issue Oct 20, 2023
@kriben
#10720 Summary Import: support upper/lower case mismatch between file…
27785da 
…name and extension.

Importing files with different casing in base name and extension would fail when
using libecl summary reader. E.g "norne_atw2013.SMSPEC" would fail since libecl
forces the extension to be lower case even though it is given the actual extension.

Removing the lowercasing allows more flexibility in the file naming.

The problem only occurs when the libecl summary reader is used, the opm-common
can already import these files.

Fixes #10720.
Fixes #10617.
@kriben kriben mentioned this issue Oct 20, 2023
Merged
magnesj pushed a commit that referenced this issue Oct 20, 2023
@kriben @magnesj
#10720 Summary Import: support upper/lower case mismatch between file…
852cd40 
…name and extension.

Importing files with different casing in base name and extension would fail when
using libecl summary reader. E.g "norne_atw2013.SMSPEC" would fail since libecl
forces the extension to be lower case even though it is given the actual extension.

Removing the lowercasing allows more flexibility in the file naming.

The problem only occurs when the libecl summary reader is used, the opm-common
can already import these files.

Fixes #10720.
Fixes #10617.
@github-actions github-actions bot added the PendingRelease Issues is fixed and will be available in next release label Oct 20, 2023
@magnesj magnesj removed the PendingRelease Issues is fixed and will be available in next release label Oct 23, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
BugInRelease Bug in an official release
Projects
None yet
Milestone
Maintenance 2023 - Sprint 10
Development

Successfully merging a pull request may close this issue.

#10720 Summary Import: support upper/lower case mismatch between file… OPM/ResInsight
2 participants
@kriben @magnesj