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
If we have "." in the basename of the file set, matching between EGRID and UNRST might get confused.
The results does not match the EGRID case, but rather a different one.
From e-mail frm hhgs fr 04.05.2018 14:46
You can do the following tests:
Copy 2C3_BASE_CP_PLAN6.7.DATA and call it 2C3_BASE_CP_PLAN6.7_TEST.DATA and run again. After it has started (and started properly), you can load the case into Resinsight.
Copy 2C3_BASE_CP_PLAN6.7.DATA and call it TEST DATA. After it has started (and started properly), you can load the case into Resinsight.
Copy 2C3_BASE_CP_PLAN6.7.DATA and call it 2C3_BASE_CP_TEST_PLAN6.7.DATA. After it has started (and started properly), you can load the case into Resinsight.
For 1) you will be able to see RESTART data by 2045, but not for 2) and 3). Seems like something happens when there is a dot in the file name. Perhaps there is something that parses filenames and splits on a sentence?
I've already done steps 1,2 and 3 in the directory I linked you so you can check.
The text was updated successfully, but these errors were encountered:
* Need to send in QFileInfo::completeBaseName() rather than just baseName()
* The change will cause libECL to match only files where the base name is everything except what is after the LAST dot.
If we have "." in the basename of the file set, matching between EGRID and UNRST might get confused.
The results does not match the EGRID case, but rather a different one.
From e-mail frm hhgs fr 04.05.2018 14:46
You can do the following tests:
For 1) you will be able to see RESTART data by 2045, but not for 2) and 3). Seems like something happens when there is a dot in the file name. Perhaps there is something that parses filenames and splits on a sentence?
I've already done steps 1,2 and 3 in the directory I linked you so you can check.
The text was updated successfully, but these errors were encountered: