July 2002
The June release of Tigress 4.6.3 brings a major extension to
the template functionality, widely used for loading log data in
Well Correlation and Log Plot. There is a big increase in the
number of ways the user can specify and search for data to be
loaded.
The template can now be configured to search through specific
well logs, interpreted sets, or core sets as appropriate. The
search can be an exact text match, or use wildcards. In addition
there is a Browse button to help the user view the entries in the
database before making a selection.
One or more alternative well logs can be specified, in case the
required data is not found in the initial named well log selection.
These alternate selections can be defined globally or on a trace-by
trace basis.
More improvements
At the trace level, the user can now optionally specify
edited/non-edited, merged/non-merged and (for porosity and
saturation traces) effective/total trace types. This is in addition
to the standard trace status selection options. Two new settings
Any and Highest have also been added. The ‘Highest’ selection will
choose the trace with the highest status based on the order RAW,
DM, BHC, ENVC and INT, where RAW is the lowest and INT the
highest.
The option of specifying an alternate name has been extended to
the trace level, if the desired trace is not found. Each alternate
trace can have its own scale, appearance and wrap settings. The
main and alternate traces do not need to belong to the same well
log or interpreted set. For example, the user could specify a core
porosity trace as the main trace and a RHOB well log trace as an
alternate trace to be used in wells where the core trace is not
available.
Finally you can now read and write templates to external files
in XML format, so that key templates can now be moved to different
projects and different sites easily!
Back to index