*.EGRID File
Moderator: Simulation_team
- Bilal Amjad
- Senior member
- Posts: 258
- Joined: Sat Sep 20, 2008 12:14 am
- Location: اسلامی جمہوریہ پاکستان
*.EGRID File
I have use
GRIDFILE
0 1 /
to out put the EGRID file, but it is not working, I have attached, Check it
GRIDFILE
0 1 /
to out put the EGRID file, but it is not working, I have attached, Check it
You do not have the required permissions to view the files attached to this post.
Bilal Amjad
Reservoir Engineering Consultant
Reservoir Engineering Consultant
- Bilal Amjad
- Senior member
- Posts: 258
- Joined: Sat Sep 20, 2008 12:14 am
- Location: اسلامی جمہوریہ پاکستان
- Bilal Amjad
- Senior member
- Posts: 258
- Joined: Sat Sep 20, 2008 12:14 am
- Location: اسلامی جمہوریہ پاکستان
- Bilal Amjad
- Senior member
- Posts: 258
- Joined: Sat Sep 20, 2008 12:14 am
- Location: اسلامی جمہوریہ پاکستان
- Bilal Amjad
- Senior member
- Posts: 258
- Joined: Sat Sep 20, 2008 12:14 am
- Location: اسلامی جمہوریہ پاکستان
I have found the solution, Just write EDIT kewyord after RPTGRID in above data file and there is output of EGRID.
It means ECLIPSE need confirmation that the GRID section is completed, writing EDIT ensures ECLIPSE that GRID section has ended.
thankyou all
It means ECLIPSE need confirmation that the GRID section is completed, writing EDIT ensures ECLIPSE that GRID section has ended.
thankyou all
Bilal Amjad
Reservoir Engineering Consultant
Reservoir Engineering Consultant
At first I thought you found the solution but upon think about it I went back to check what is happening there.
OK, I can ran a DATA file with all SECTIONS present (test DATA file) and with JUST the keyword GRIDFILE I was able to have a EGRID written.
The key here is that "all SECTIONS" were present that normally should be there. In your case you wrote a funny ECLIPSE DATA file in that the GRID section had no logical ending for ECLIPSE GRID section, hence it did not do what the GRIDFILE keyword requested. By putting a keyword to denote the NEXT section, EDIT, you logically CLOSED the GRID section for it to be able to write the EGRID. So there was nothing wrong with the GRIDFILE keyword parameters, the reason was how you put the DATA file together.
I tried to close the GRID section with END keyword but this would not do it. So a keyword defining another SECTION of the ECLIPSE DATA file is needed to close it.
OK, I can ran a DATA file with all SECTIONS present (test DATA file) and with JUST the keyword GRIDFILE I was able to have a EGRID written.
The key here is that "all SECTIONS" were present that normally should be there. In your case you wrote a funny ECLIPSE DATA file in that the GRID section had no logical ending for ECLIPSE GRID section, hence it did not do what the GRIDFILE keyword requested. By putting a keyword to denote the NEXT section, EDIT, you logically CLOSED the GRID section for it to be able to write the EGRID. So there was nothing wrong with the GRIDFILE keyword parameters, the reason was how you put the DATA file together.
I tried to close the GRID section with END keyword but this would not do it. So a keyword defining another SECTION of the ECLIPSE DATA file is needed to close it.