Medios publicitarios

Note: Annotations for logs are constructed using the control file comment.fil (see page 2-13).

See Remark

Follow the recommendations in the “Remarks” section (see page 3-10). All remarks should be referenced on the log by the “See Remark” annotation.

If the “See Remark” refers to a particular depth interval, position the reference in between the top and bottom of the interval instead of at the top or bottom of the interval. Do this unless the interval to be remarked is several hundred feet in depth on the log.

Trace Labels

Trace labels should be placed within the first 100 feet and last 100 feet of each log. If your log is only a few hundred feet in length, such as a relog or morning log, it may not be necessary to supply trace labels at both the top and the bottom of the log (i.e., avoid crowding the log with too much information). Examine TVD logs carefully for this! In addition, trace labels should be provided at intermediate points on quantitative logs and lengthy correlation logs. As a rule, these should be spaced approximately every five feet, or 1.5 meters, on both quantitative and correlation logs. It is important to remember that the trace labels may need to be adjusted so they are evenly spaced on the log. It is better to have fewer trace labels than too many trace labels. Also, avoid placing trace labels in pay zones or areas of interest.

Also, always make sure trace labels are provided where one service ends and another service begins on the log (i.e., where RGD converts to DPR).

If large gaps are present on the log due to tool failures, or intervals that were drilled without Eastman Teleco, etc., provide trace labels where the traces end and begin again. Depending on the length of the gap, it may not be necessary to do this for the correlation log, but it should always be done for the quantitative log presentation.

When plotting correlation DPR logs with linear grids (such as the Gulf Coast), trace labels are required for both R_at and R_pd on the 0 to 10 scale as well as R_pd on the 0 to 2 scale. It is acceptable to position the trace labels for the 0 to 10 scale to the left of the traces, which will probably put the trace labels in the depth track (see log examples at the end of each chapter for service descriptions). Make sure that the trace labels are positioned such that they do not interfere with depth labels, run markers, casing markers, etc. Also take care to make sure the R_at trace label accurately points to the R_at trace (dashed curve) and the R_pd trace label points to the R_pd trace (solid line). As a rule, when the R_at and R_pd traces overlap one

Log Preparation Log Quality and Data Management Standards another, place R_at on the left side and R_pd on the right side of the

overlapping traces.

Back Up Trace Labels

Make sure back up traces are labeled when plotted. They should be labeled as CSAX back up ->. These are entered as a freeform remark using the

“Annotations Across” option (see page 2-15). This is done primarily for the conductivity trace.

Casing Markers

Always include casing markers in the depth track on all final logs

regardless of whether the casing marker overlaps with a depth label. Also identify the casing markers with the size of the casing (for example, 13-3/8” casing, see log examples at the end of each chapter for service descriptions). Attempt to place this inside of the casing unless space is a factor. This is done using the “Annotations Across” option (see page 2-15).

Also make sure to reposition your casing markers appropriately for 5-inch logs. Casing markers can also be generated manually by using the “Line Annotation” option for comment.fil (see page 2-16).

If we log out of casing and this is recorded on the log, mark the casing according to the log, not at the depth recorded by the driller. If there is a discrepancy in depths, make note of it in the Remarks page. List separately the driller's casing depth and Teleco's casing depth (see log examples at the end of each chapter for service descriptions). It is also important to note those intervals of log that have been logged behind casing.

Run Markers

Identify run markers on the right side of the depth track where runs begin and end. If there are any runs that overlap one another, these runs need to be entered by hand using the “Annotations Down To” and “Annotations Down From Depth” options (see page 2-16). When runs do overlap, offset and alternate the run markers as shown in the log examples at the end of each chapter for service descriptions. Where resistivities plot below 0.2 ohm-m (i.e., plots into the depth track), offset run markers if necessary to avoid overlap between the run marker and resistivity trace.

Make note that run markers should now be plotted on the right side of the depth track. Data density has been moved to the left-hand side of the depth track so it will not interfere with resistivity traces that plot below 0.2 ohm-m.

Log Quality and Data Management Standards Log Preparation TD Markers

TD markers should also be provided at the end of the log (at “TD”) in the depth track unless they overlap with depth labels (see log examples at the end of each chapter for service descriptions). Commonly, this will happen on only one log, such as the TVD log. In this case, remove the marker from the log in question but include it on all other logs where it does not overlap.

TD markers can also be generated manually using the “Line Annotation”

option for comment.fil (see page 2-16).

Sliding Indicator

This is a new option that permits identification of sliding intervals on the log. As a default, plot the line between the specified depth interval on the outside edge of the right side of the log (i.e., track 3).

Comment Files

Note: In order to activate all or any of the annotation options in comment.fil, go to the HPUTIL main menu and select MPLOT CONFIGURATION. Select “Yes” for desired options. It is important to note that comment files are generated using the SEE ASCII editor (selected from the HPUTIL main menu). Comment files are edited using either the SEE editor or the edit option in the MPLOT log plotting configuration menu (press [F1] to edit). To facilitate editing and log preparation, all features such as trace labels and annotations etc. can be viewed directly on the screen logs (press [F8] to view log).

Remarks

Type in your remarks as they should appear on the remarks page. If you do not want a remark printed, you must either delete it or insert an

exclamation mark in front of the remark. The exclamation mark, when placed in column 1, basically tells the computer not to print that line (see

“Exclamation Mark” on page 2-12).

Annotations

You should make an attempt to learn all of the annotation options available under the comment.fil. Become familiar with freeforming the annotations and, in particular, the “Down from Depth” and “Down to Depth” options.

These allow you to freeform run markers in the event that you have overlapping runs. You will also be required to annotate the casing size in the depth track of each log where applicable (see example logs at the end of each chapter for service descriptions). You may also find it necessary to

Log Preparation Log Quality and Data Management Standards freeform the “See Remark X” option when the preset positions get in the way of log traces.

Look for areas of conflict after plotting a log. For example, look for overlapping run markers, casing markers and TD markers that overlap depth markers, or trace labels and “See Remark X” that overlap traces, etc.

If there are conflicts, reposition the label accordingly. Overlapping run markers should be put in the depth track using freeform annotations. Omit TD markers from logs where the TD marker conflicts with a depth label.

See Remark 1

Make note of the track coding (1 through 4). If none of these positions works well for your log, use the freeform annotations (see the preceding section).

Exclamation Mark

Use the “!” symbol for any line you do not want to print on the remarks page. Also use this to fill line spaces between different sections in your comment.fil. This prevents blank remarks pages from printing below your last remarks.

Scale Changes

Become familiar with the “Scale Change” option (see example logs at the end of each chapter for service descriptions). This has a very important application for the first track on every log. In the past, we have encountered conflicts between the gamma ray and the rate of penetration trace. These conflicts can, in many cases, be eliminated with a scale change. In the event of high rates of penetration, you should apply a scale change to the rate of penetration trace through the interval characterized by the high drilling rates. In many cases, you may find it necessary to apply a scale change to the gamma ray trace when it drifts off to one side. Use good judgement for scale changes. Although you should feel comfortable about making scale changes, do not get in the habit of applying scale changes every 1,500 feet.

Trace Labels

When setting up trace labels, make sure to set up separate gamma ray trace labels for the correlation and quantitative logs. Due to the different

smoothing intervals between the two, labels set up for the correlation log typically will not work for the quantitative log.

Most engineers find it convenient to build a comment.fil for the main header and each log type (such as 1MD.fil, 1TVD.fil, 5MD.fil, 5TVD.fil, comment.fil). It is recommended to end each file with the three letter extension “.fil.” This ensures that all of these files will be stored when a

Log Quality and Data Management Standards Log Preparation Getdata is performed. Also make sure to use a name that makes it easy to understand which file is for which log. Remember, we need to have the capability to plot your log in the event you cannot. If any corrections are made to your comment files while you are plotting final logs, make sure to restore these to disk via a Getdata.

Traces On/Off

This is a new function in MPLOT that enables the engineer to turn traces on or off where desired. This is advantageous, for example, when you log behind casing. Your log response is rather erratic and may drift beyond the track it is plotted in. This data can be turned off without having to

manipulate the database. The same can be done in areas with poor data quality due to a tool failure. Its most common use is when combining real-time and memory data. Typically, the real-real-time data is disabled in the overlap region where the real-time data ends and the memory data begins or vice versa. (see “Traces On and Off” on page 2-15 for instructions on how to use this option.)

Guide to Comment.fil (Bryan Dugas) Comment.fil

Comment.fil contains commands and text to be displayed on logs generated with MPLOT. It is important to note that the comment file is generated using the SEE editor (selected from the HPUTIL main menu).

The comment file can be edited using either the SEE editor or the edit option in the MPLOT log plotting configuration menu (press [F1] to edit).

To facilitate editing, all features such trace labels, annotations, etc., can be viewed directly on the screen logs (press [F8] to view log).

Each line in the comment.fil is classified by the first character (which should always be left justified). Also note that there are no spaces in between characters. Below is a summary of the formats of the different types of annotations:

#LABEL,DEPTH,VALUE,LEFT OR RIGHT : Trace Labels

!COMMENT : Do Not Print

@X,DEPTH,TRACK # : See Remark X

^LABEL,DEPTH,CYCLES,LEDGE,REDGE : Scale Change

%ANNOTATION,DEPTH,LOCATION : ASCII Across

*ANNOTATION,DEPTH,LOCATION : ASCII Down To

&ANNOTATION,DEPTH,LOCATION : ASCII Down From

Log Preparation Log Quality and Data Management Standards

+LABEL,DEPTH : Trace On

-LABEL,DEPTH : Trace Off

|START DEPTH,END DEPTH,LOCATION,WIDTH : Line Annotation

Any Other Character : Remark On Header

See Remarks X

@X,DEPTH,TRACK #

@1,12000,1 (example 1)

@2,12500,4 (example 2)

Example 1: Place See Remark 1 at 12000 MD in the first track.

Example 2: Place See Remark 2 at 12500 MD in between tracks 2 & 3.

TRACK # coding 1 = TRACK 1 2 = TRACK 2 3 = TRACK 3

4 = Between tracks 2 & 3 Comment Line

!This Line Will Not Print.

Trace Labels

#LABEL,DEPTH,VALUE,LEFT OR RIGHT

#GRCM,12000,160,R (example 1)

#GRCM,12500,160,L (example 2)

Example 1: Place GRCM label at 12000 MD to the right of the trace at a value of 160.

Example 2: Place GRCM label at 12500 MD to the left of the trace at a value of 160.

An arrow automatically accompanies each trace label.

For L the trace label looks like GRCM->.

For R the trace label looks like <-GRCM.

See “Mnemonics Listing” in Appendix A for a listing of trace labels.

Log Quality and Data Management Standards Log Preparation Traces On and Off

+/-LABEL,DEPTH

-GRCM,12000 (example 1) +GRCM,12100 (example 2)

Example 1: The GRCM trace is turned off at 12000 MD (the trace is no longer plotted on the log).

Example 2: The GRCM trace is turned on at 12100 MD (the trace begins plotting at the above depth).

Note: A valid range must exist for the <curve> when the log begins plotting in order for the “+” and “-” commands to work. The screen log does not support this feature.

Scale Change

LABEL,DEPTH,CYCLES,LEDGE,REDGE

^GRCM,12000,0,25,250 (example 1)

^RSAX,12500,2,.2,20 (example 2)

Example 1: Change scale of GRCM at 12000 MD with 0 cycles (Linear Grid) and a scale from 25 to 250.

Example 2: Change scale of RSAX at 12500 MD with 2 cycles (Logarithmic Grid) and a scale from 0.2 to 20.

Annotations Across

%ANNOTATION,DEPTH,LOCATION

%10 3/4”,12500,540 (example 1)

%CASING,12000,540 (example 2)

Example 1: Place 10 3/4” at 12500 MD at location 540 (Depth Track).

Example 2: Place CASING at 12000 MD at location 540 (Depth Track).

LOCATION CODING

28 280 540 690 940 1200 1450 1700

TRACK 1 Depth TRACK 2 TRACK 3

660

Log Preparation Log Quality and Data Management Standards Annotation Down From Depth

&ANNOTATION,DEPTH,LOCATION

&> Run 6,12000,660 (example 1)

&> Run 5,11000,660 (example 2)

Example 1: Place > Run 6 starting at 12000 MD at location 660 (Depth Track).

Example 2: Place > Run 5 starting at 11000 MD at location 660 (Depth Track).

Annotation Down To Depth

*ANNOTATION,DEPTH,LOCATION

*Run 6 <,13000,660 (example 1)

*Run 5 <,12000,660 (example 2)

Example 1: Place Run 6 < ending at 13000 MD at location 660 (Depth Track).

Example 2: Place Run 5 < ending at 12000 MD at location 660 (Depth Track).

Line Annotation

|<START DEPTH>,<END DEPTH>, <LOCATION>,<WIDTH>

This line command draws a line between the <Start Depth> and <End Depth> at the location of a given width. The width is represented in 1/200^th of an inch (for example, “2” is 2/200^th of an inch). This command is used to manually generate casing markers, TD markers, and sliding indicators.

|11000,11050,1701,8

Example: A vertical line is drawn on the outside edge of the track 3 from 11,000 to 11,050 feet with a line thickness of 8/200^ths of an inch. “8” is a typical line thickness for a “sliding” bar indicator. “2” is typical for standard width lines.

Log Quality and Data Management Standards Log Preparation Horizontal Lines

|START DEPTH,END DEPTH,LOCATION,WIDTH

Horizontal lines can also be drawn by manipulating the start and end depth and width. In this case, start and end depth represent the line thickness and width is line length.

|9000,9000.2,540,153

Example: The TD marker is placed in the depth track at 9,000 feet. The length of the line begins at the location of 540 and extends for 153/200^ths of an inch. Line thickness is 0.2 (log) feet.

Casing Markers

%?,DEPTH-0.5,537

%Þ,DEPTH-0.5,671

Casing markers can be created individually by using a combination of Annotation Across (%) and a line command (|). The depth listed should be the casing depth minus 0.5. Two special characters (?, Alt 22...for the left side) and (Þ, Alt-23...for the right side) are needed for plotting the casing markers. These ASCII characters are created in the text editor by holding down [ALT] and typing the number on the numeric keypad, then releasing [ALT]. As can be seen, this annotation takes two comments, one for each side of the depth track. Additionally, a line annotation is needed to draw a line across the depth track. Note the example below:

%?,9000.5,537

%Þ,9000.5,671

|9001,9001.2,537,153

Example: A casing marker is placed on each side of the depth track (location 537 and 671) at a depth of 9,000.5 feet. A horizontal line is also drawn across the depth track at 9,001 feet.

Note: Examples in “Line Annotation,” Horizontal Lines,” and

“Casing Markers” are based on a 5-inch log

presentation, the values for line width or thickness will vary depending on depth scales used for plotting.

Log Preparation Log Quality and Data Management Standards

In document UNIVERSIDAD COMPLUTENSE DE MADRID (página 86-93)