Continue to Site

Eng-Tips is the largest engineering community on the Internet

Intelligent Work Forums for Engineering Professionals

  • Congratulations cowski on being selected by the Eng-Tips community for having the most helpful posts in the forums last week. Way to Go!

Eclipse 100 error

Bekzat

Student
May 1, 2025
2
Hello everyone
I'm currently a student working on my diploma (graduation) project, and as part of the final section I would like to present a production forecast using Eclipse 100.
However, I’m facing some errors during the simulation, and unfortunately, I haven't been able to resolve them on my own. I'm kindly reaching out to see if anyone here might be able to help or guide me in the right direction.
Any support or suggestions would be truly appreciated!
Thank you in advance 🙏

@-- ERROR AT TIME 0.0 DAYS (30-MAY-2025):
@ UNRECOGNISED KEYWORD PERMX 5. IN GRID DATA
18 READING PERMY 5.

@-- ERROR AT TIME 0.0 DAYS (30-MAY-2025):
@ UNRECOGNISED KEYWORD PERMY 5. IN GRID DATA
19 READING PERMZ 5.

@-- ERROR AT TIME 0.0 DAYS (30-MAY-2025):
@ UNRECOGNISED KEYWORD PERMZ 5. IN GRID DATA

@--WARNING AT TIME 0.0 DAYS (30-MAY-2025):
@ SPURIOUS DATA BEFORE ENDBOX KEYWORD
@ /
20 READING ENDBOX
21 READING PORO
22 READING INIT
23 READING PROPS

@--MESSAGE AT TIME 0.0 DAYS (30-MAY-2025):
@ UNSPECIFIED TOPS VALUES OBTAINED BY ADDING DZ
@ TO TOPS VALUE FOR LAYER ABOVE

@--MESSAGE AT TIME 0.0 DAYS (30-MAY-2025):
@ NEITHER OLDTRAN,OLDTRANR NOR NEWTRAN SPECIFIED
@ BLOCK CENTRE TRANSMISSIBILITIES TO BE CALCULATED
@ USING OLDTRAN

@-- ERROR AT TIME 0.0 DAYS (30-MAY-2025):
@ INSUFFICIENT DATA TO COMPUTE PORE VOLUMES
@ PORE VOLUMES WILL BE SET TO ZERO

@-- ERROR AT TIME 0.0 DAYS (30-MAY-2025):
@ INSUFFICIENT DATA TO COMPUTE CELL CENTRE DEPTHS

@-- ERROR AT TIME 0.0 DAYS (30-MAY-2025):
@ INSUFFICIENT DATA TO COMPUTE X TRANSMISSIBILITIES

@-- ERROR AT TIME 0.0 DAYS (30-MAY-2025):
@ INSUFFICIENT DATA TO COMPUTE Y TRANSMISSIBILITIES

@-- ERROR AT TIME 0.0 DAYS (30-MAY-2025):
@ INSUFFICIENT DATA TO COMPUTE Z TRANSMISSIBILITIES

@--COMMENT AT TIME 0.0 DAYS (30-MAY-2025):
@ NO NON-NEIGHBOUR CONNECTIONS FOUND

@--MESSAGE AT TIME 0.0 DAYS (30-MAY-2025):
@ NUMBER OF ACTIVE CELLS IS 0

@-- ERROR AT TIME 0.0 DAYS (30-MAY-2025):
@ THERE ARE NO ACTIVE CELLS IN THE RESERVOIR
 
Replies continue below

Recommended for you

I assume you don't have a user manual, nor anyone who has used this s/ware ?

have you run a tutorial problem ? It is obvious that you have really confused it !

A google search "eclipse 100 manual" returned a bunch of hits which looked applicable ??

YT is often a good source ...
 
I assume you don't have a user manual, nor anyone who has used this s/ware ?

have you run a tutorial problem ? It is obvious that you have really confused it !

A google search "eclipse 100 manual" returned a bunch of hits which looked applicable ??

YT is often a good source ...
Thank you for your response! I’m a student and I’m currently using the university’s version. I wrote the code myself, but since I don’t have much experience yet, I’ve encountered some issues. Could you please help me with them?
 
sorry, no ... as I don't know anything about what you are doing.

Is "eclipse 100" a language, like Python ?

You "wrote the code" ... is this "code" a specific problem solving or a more generalised code ??

Is there no one there who can help, a thesis supervisor ??

What support do you have ? Maybe someone said "here is something, make it work" ?
 
Look for Schlumberger Eclipse 100. It's a permeability modeling software for petroleum and water subsurface movement.

Looking at error messages doesn't tell what is wrong with the file. It tells where in the file to look for what caused a cascade of problems. It could be an extra tab character or a comma instead of a semicolon.

There should be a course in software debugging given in the freshman year as there are plenty of ways for user input to cause software to misbehave, sometimes "running" but giving garbage answers.
 
Given that some of the inputs don't generate errors, it's likely to be typos or formatting errors in the input.

I used to use a simulation program whose input was still based on punch card formatting, so a slip in column position would throw a catastrophic error, often with no obvious warnings from the program. Likewise, if the inputs weren't correctly formatted, it would throw errors.

Actually, I would still be using that program, even though they upgraded to a more free form input, because their GUI was so obtuse.
 
I liked the C compilers that would throw an "Unmatched Brace" error with the line number of the last line of the program because I missed one a few hundred lines earlier. I know it could not guess where the problem was, but the fake-out on the line number was just putting salt on the wound.
 
arrgghh, don't get me started on rants about programming. I recently encountered an app where I needed to input my birthdate, but rather than the usual mm/dd/yyyy input, the a$$hole programmer put in a calendar app because they were too lazy to figure out how to parse a date string, so I had to click the back a month button more than 700 times, because I'm THAT old. There should be a place in hell for lazy programmers. What was doubly annoying is that elsewhere in the app, someone else already coded a mm/dd/yyyy input parser.
 
On the Windows day/date/time calendar, clicking on the month switches to showing just the year and all the months. Clicking then on the year shows a panel of years. Perhaps the one you had does the same??

3 clicks:
calendar.png

I have looked at time software underpinnings and most everyone involved with it says two things. One is, that way lies madness and the other is. use someone else's library. The mess that calendars and time has become what with everyone f'ing with it ... Like, is it daylight savings time? Does it include the segments where that was extended or shortened? Is it a date and time from outside the current time zone? Does it include when the number of seconds in a year is tweaked?
 

Part and Inventory Search

Sponsor