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
From the Everest course, user ran a case and got this warning from this part of everest_to_ert:
try:
data_wells = list(_load_all_wells(data_files))
except Exception:
warn_msg = (
"Failed to load well names from {}. "
"Only well data for wells specified in config file will be "
"internalized during run."
The warning:
IOConfig: Reading GRIDFILE keyword from GRID section: Output of GRID file is not supported. Supported format: EGRID
WARNING:everest:Failed to load group names from ['/project/everest/users/xxxx/day_3_wellrate/eclipse/model/REEK.DATA', '/project/everest/users/xxxx/day_3_wellrate/eclipse/model/REEK.DATA', '/project/everest/users/xxxx/day_3_wellrate/eclipse/model/REEK.DATA', '/project/everest/users/xxxx/day_3_wellrate/eclipse/model/REEK.DATA', '/project/everest/users/xxxx/day_3_wellrate/eclipse/model/REEK.DATA']. No group summary data will be internalized during run.
IOConfig: Reading GRIDFILE keyword from GRID section: Output of GRID file is not supported. Supported format: EGRID
WARNING:everest:Failed to load well names from ['/project/everest/users/xxxx/day_3_wellrate/eclipse/model/REEK.DATA', '/project/everest/users/xxxx/day_3_wellrate/eclipse/model/REEK.DATA', '/project/everest/users/xxxx/day_3_wellrate/eclipse/model/REEK.DATA', '/project/everest/users/xxxx/day_3_wellrate/eclipse/model/REEK.DATA', '/project/everest/users/xxxx/day_3_wellrate/eclipse/model/REEK.DATA']. Only well data for wells specified in config file will be internalized during run.
The actual error:
As a minimum we should at least forward the caught exception message+traceback.
The text was updated successfully, but these errors were encountered:
From the Everest course, user ran a case and got this warning from this part of
everest_to_ert
:The warning:
The actual error:
As a minimum we should at least forward the caught exception message+traceback.
The text was updated successfully, but these errors were encountered: