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
This issue has been discussed via e-mail for some time (at least @joakim-hove, @hhgs, @magnesj and myself has been involved), but for the sake of openness it really belongs to the GitHub issue tracker. I choose to open it here, but it is not clear to me whether this issue belongs here or in another OPM module, e.g. opm-core or opm-upscaling.
The problem is that not all eclipse output files from the upscaling application steadystate_test_implicit are possible to open in ResInsight. The produced EGRID file opens fine, but the UNRST files are not possible to open. Three issues have been identified:
The basename (without extension) of all eclipse output files must be identical.
ERT crashes when time stampes are prior to 1970.
The number of active cells in the EGRID files does not match the number of parameter values in the UNRST files.
By this issue I do not intend to push those of you already working on it, but it is probably for the best to let the hole community of OPM be aware of it.
The text was updated successfully, but these errors were encountered:
This issue has been discussed via e-mail for some time (at least @joakim-hove, @hhgs, @magnesj and myself has been involved), but for the sake of openness it really belongs to the GitHub issue tracker. I choose to open it here, but it is not clear to me whether this issue belongs here or in another OPM module, e.g. opm-core or opm-upscaling.
The problem is that not all eclipse output files from the upscaling application
steadystate_test_implicit
are possible to open in ResInsight. The producedEGRID
file opens fine, but theUNRST
files are not possible to open. Three issues have been identified:EGRID
files does not match the number of parameter values in theUNRST
files.By this issue I do not intend to push those of you already working on it, but it is probably for the best to let the hole community of OPM be aware of it.
The text was updated successfully, but these errors were encountered: