-
Notifications
You must be signed in to change notification settings - Fork 92
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
Mixed casing in summary file names #10720
Labels
BugInRelease
Bug in an official release
Milestone
Comments
Related to #10617? |
kriben
added a commit
that referenced
this issue
Oct 20, 2023
…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.
magnesj
pushed a commit
that referenced
this issue
Oct 20, 2023
…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
bot
added
the
PendingRelease
Issues is fixed and will be available in next release
label
Oct 20, 2023
magnesj
removed
the
PendingRelease
Issues is fixed and will be available in next release
label
Oct 23, 2023
magnesj
modified the milestones:
Maintenance 2023 - Sprint 11,
Maintenance 2023 - Sprint 10
Nov 1, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
A case is exported from Intersect resulting in mixed casing on disk
my_case.SMSPEC
andmy_case.EGRID
When importing data into ResInsight, import of
EGRID
andUNRST
data works as expectedIt is not possible to import summary data with mixed casing
Renaming to
MY_CASE.SMSPEC
andMY_CASE.UNSMRY
will import the data correctly.The mixed casing should work for both
libecl
andopm-common
file reader, and should work for both single case and ensemble case.Related issues
#8385
#10617
#3009
4e51516
The text was updated successfully, but these errors were encountered: