Setting Default tables and Fields

Changing these default interval tables can be useful from an administrative perspective.  Changing these tables ensures that all new projects will be created with the same interval tables and fields, though these can always be changed inside Petra.  

When creating a new project, Petra looks at a file called INTDATA.DEF located in the program’s Parms directory.  On most standalone installations, this will be located in C:\geoplus1\Parms. This file contains the default tables and fields that will be created in a new project.

It’s important to not edit the default interval table file (INTDATA.DEF).  Instead, copy the INTDATA.DEF file to a new file called INTDATA.USR.  Make all new changes to the new file called INTDATA.USR.  Petra first looks for INTDATA.USR before it looks for INTDATA.DEF.

The default version of this file contains three tables: LITH, CORE, and PALEO.

Table: LITH - Lithology

Field: Desc - Description

Table: CORE - Core Interval Data

Field: Poros - Core Porosity

Field: Perm - Core Permeability

Field: Recov - Amt of Core Recovered

Table: PALEO - Paleo Data

Field: FmName - Formation Name

Field: Bug - Fossil Name

Field: Age - Age of Zone

Petra reads the INTDATA file and builds interval data based on comma-delimitated values.

TABLE, TABLE NAME, “Table Description”

FIELD, KIND, NAME, SRC, “Field Description”, UNITS, DECIMALS

TABLE – This signifies that the entry is for a new table.

Table Name – This is the name of the table.  It’s a good idea to separate tables based on genetically related data, such as mudlogs, core descriptions.  Remember that tables, unlike zones, are completely independent of stratigraphy, so it is probably easier to lump all related data together rather than break out intervals based on specific formations.

“Table Description” - This sets a brief description of the table.  In the example, the “LITH” field’s description is “Lithology Data.”  Remember to put quotation marks around the description.

FIELD – This just signifies that the entry is for a new field.  Make sure all new field entries are prefaced by “FIELD.”

Kind – Fields can store three kinds of data: Real Values, Date Values, or String Values.  The letter here tells Petra what kind of data this field will store – “R” for Real values, “D” for Date values, and “S” for String values.  Real values simply store numbers, such as porosity or permeability.  Dates store calendar days as MM/DD/YYYY.  String values store text, like core descriptions.  

Name – This is the name of the field.

SRC – This sets the user source for the specific field.  User sources are useful for distinguishing between different user’s interval data in a multiuser environment.

“Field Description” – This sets a brief description of the field.  In the example, the “Recov” field’s description is “amt of core recovered.”  Remember to put quotation marks around the description.

UNITS – This sets the units of the field.

DECIMALS – This sets the number of decimals shown for real value (numerical) data.  Though it’s a good idea to set this value to 0 for string and date fields, it’s not necessary