Open mauriciolmatos opened 3 years ago
I'll take a look at this today and get back to you in the next couple of days.
Okay I had a quick look at this. I commented out the PINCHREG keyword, as it is not supported in the current release. The run then causes the simulator to throw an exception and to abort. This is because the oil PVT is not in the input deck, due to the PVCO keyword not being supported.
Warning: Unsupported keywords or keyword items:
NOINSPEC: keyword not supported
In file: /mnt/d/Linux/OPM/Fields/UNISIM-I-D/UNISIM-I-D-deterministic-ECLIPSE/UNISIM_I_D_ECLIPSE.DATA, line 38
PINCHNUM: keyword not supported
In file: /mnt/d/Linux/OPM/Fields/UNISIM-I-D/UNISIM-I-D-deterministic-ECLIPSE/UNISIM_I_D_ECLIPSE.DATA, line 145867
PMAX: keyword not supported
In file: /mnt/d/Linux/OPM/Fields/UNISIM-I-D/UNISIM-I-D-deterministic-ECLIPSE/PVT_0.INC, line 1
PVCO: keyword not supported
In file: /mnt/d/Linux/OPM/Fields/UNISIM-I-D/UNISIM-I-D-deterministic-ECLIPSE/PVT_0.INC, line 4
NOECHO: keyword not supported
In file: /mnt/d/Linux/OPM/Fields/UNISIM-I-D/UNISIM-I-D-deterministic-ECLIPSE/UNISIM_I_D_ECLIPSE.DATA, line 146039
NOECHO: keyword not supported
In file: /mnt/d/Linux/OPM/Fields/UNISIM-I-D/UNISIM-I-D-deterministic-ECLIPSE/UNISIM_I_D_ECLIPSE.DATA, line 146135
EXCEL: keyword not supported
In file: /mnt/d/Linux/OPM/Fields/UNISIM-I-D/UNISIM-I-D-deterministic-ECLIPSE/UNISIM_I_D_ECLIPSE.DATA, line 146151
So you need to use one of the supported oil PVT keywords instead: PVCDO, PVDO or PVTO.
Let me know how you get on.
First, thanks for the feedback.
I tried commenting the keyword "PINCHREG" and changing the keyword "PVCO" to PVCDO, PVDO or PVTO and it didn't work. Reported this error:
"Exception caught: PARSE_UNKNOWN_KEYWORD: Unknown keyword: PINCHNUM"
So, I commented/deleted all the keywords you listed, which are not supported, and also not run. Did this data run on your machine?
When i use PVCDO:
When i use PVDO:
When i use PVTO:
In flow 2020.10 the message is always the same as my first comment.
Thank you very much.
Maurício,
First thing is install the latest version of OPM Flow, which is 2021.04, as there has been many improvements with reading the input decks. Then send me you input decks with the two different oil PVT keywords and I'll take a look.
OPM User @.***
On 23-Aug-21 20:39, Maurício Matos wrote:
First, thanks for the feedback.
I tried commenting the keyword "PINCHREG" and changing the keyword "PVCO" to PVCDO, PVDO or PVTO and it didn't work. Reported this error:
"Exception caught: PARSE_UNKNOWN_KEYWORD: Unknown keyword: PINCHNUM"
So, I commented/deleted all the keywords you listed, which are not supported, and also not run. Did this data run on your machine?
When i use PVCDO: image https://user-images.githubusercontent.com/47835964/130448058-0fc31be8-88aa-4316-b7d9-35a8bc035cf8.png
When i use PVDO: image https://user-images.githubusercontent.com/47835964/130448139-924bfe9c-d1c2-4951-9d00-547213ac096e.png
When i use PVTO: image https://user-images.githubusercontent.com/47835964/130448215-2389a830-5825-4715-b935-6c3636c467cf.png
In flow 2020.10 the message is always the same as my first comment.
Thank you very much.
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/OPM/opm-simulators/issues/3483#issuecomment-903726988, or unsubscribe https://github.com/notifications/unsubscribe-auth/AEJAQD62KXH7GF5G56HS3X3T6I6O7ANCNFSM5CTAITGQ. Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email.
Dear,
First I installed the latest version of OPM. Then, I commented on keywords not supported by OPM. And finally I changed the PVCO keyword to PVTO modifying the input structure, according to the OPM manual.
Although there is no error, the simulation is not executed.
If possible I would like to share the inputs I am using.
Hi,
In the RUNSPEC section make sure NOSIM is commented out, so instead of this:
NOSIM
use this:
-- NOSIM
If it still does not run send me the deck and I'll take a look.
OPM User @.***
On 10-Sep-21 22:54, Maurício Matos wrote:
Dear,
First I installed the latest version of OPM. Then, I commented on keywords not supported by OPM. And finally I changed the PVCO keyword to PVTO modifying the input structure, according to the OPM manual.
Although there is no error, the simulation is not executed.
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/OPM/opm-simulators/issues/3483#issuecomment-916966587, or unsubscribe https://github.com/notifications/unsubscribe-auth/AEJAQDZBWKC3FKAR5VCRZI3UBIL3RANCNFSM5CTAITGQ. Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
Unfortunately there isn't NOSIM keyword .
Could you send me your email so I can share the folder with you?
Dear, I would like to kindly help with a simulation that I need to run.
I'm trying to run the simulation of the synthetic field "UNISIM" made available by the UNICAMP university in Brazil.
Those were originally built for Eclipse and are available at: https://www.unisim.cepetro.unicamp.br/benchmarks/br/unisim-i/unisim-i-d, in source files, "dataset - deterministic (ECLIPSE). It's a small, quick simulation file.
When I try to run on flow 2019.04 I get this error:
I tried to delete the keywords that were not recognized and I was not successful.
When I try to run on flow 2020.10 I get this error:
Note: the examples of opm and the norne field run normally
Possibly it's a simple thing but my knowledge in the software doesn't allow me to solve it. I apologize for writing on this site, I believe this issue could be posted on a forum, but I don't know of a forum for OPM discussions.
Thank you very much in advance.