Dipmeter/Image Repair______________________________________________________________ 1

Dipmeter / Image Repair Notes

Bill Newberry Version 1.0 - Jan., 1998 This is a work in progress and will be updated and expanded periodically.

Dipmeter/Image Repair______________________________________________________________ 2

Dipmeter/Image Repair

When there is an apparent problem with a set of image or dipmeter data there is a logical path to follow in trying to locate the specific cause. The following checklist can be used a starting point in analyzing the problem. Relatively straightforward fixes exist for many of the common problems. The most common problems involve poor image quality or inclinometry channels which are incorrect. Many of these bad jobs can be repaired with a high degree of confidence; others are hopelessly bad. The term repair often means not so much the fixing of bad data as it does the determination of processing parameters which will permit the computation of reasonable and usable dip results.

Apparent Problem Images Look Bad

Check Speed Correction Turn on sticking logic, tune with thresholding Check for oil or gas in the borehole, particularly in horizontal wells Check for mirror imaging of pad and/or flap images Check EMEX Voltage Turn off EMEX correction ( output = input / EMEX Voltage ) Check for sections of bad data Run BorEID in sections, omitting the bad zones Change Equalization Parameters

Dips are Bad

Check Inclinometry using GPIT Survey Rescale or recompute bad accelerometers or magnetometers If more than one magnetometer and/or accelerometer are bad, use well deviation survey and process on VAX Calipers are bad Set to Bit Size in BorDip or process on VAX, using MAPUTL to fix calipers Change BorDip parameters

Dipmeter/Image Repair______________________________________________________________ 3

MSD Parameter Selection for BorDip

BorDip is a very effective dip analysis program. However it is not CorDip under a new name. It was completely rewritten from the ground up. In order to get good consistent dips from BorDip parameters must be selected in a slightly different manner than you are accustomed to with CorDip. What follows is a discussion of my findings after looking at a large number of SHDT, FMS and FMI jobs from a variety of geographical locales with differing geological formations and mud conditions. There is no magic bullet set of parameters that will universally provide the best results. There is a straightforward methodology which will take care of all but the most extreme data sets. When there is no prior knowledge as to what sort of dips to look for, I make a pass of BorDip run on default settings. If this does not produce reasonable results, i.e. good quality, consistent dips with recognizable patterns, I go directly into BorView and manually pick a few dips to get the overall trend. I then rerun BorDip using the dip trend found from the manual picks as a focusing plane. Also, since I already know the general trend, I lower the search angle from 60 to 40 . The results of this pass should show at least moderate quality dip patterns. Next, I hang a second BorDip module under the first. Here I change the Correlation Cutoff (under Correlation Parameters ) from 0.5 to 0.25, under Focusing Plane Parameters ; change the search angle to 20 , set the Type of Focusing Plane to Variable Plane and select the output from the previous run in Select Previous Dip Results for Variable Focus. If the input data is of reasonable quality, the results should be good. If the input data is of poor quality, (oil-based mud, poor pad contact, ovalized hole, etc.) there is an additional procedure which can often dramatically improve the dip calculations. This scheme involves serious changes to the button-to-button correlations. In general, better correlations are seen on opposing pads than on adjacent ones. After eliminating the adjacent pad correlations, the dips improve greatly. Figure 1 shows the standard MSD button correlations. Figure 2 shows the correlation links I use, all are two way links.

Figure 1

Figure 2

Dipmeter/Image Repair______________________________________________________________ 4

Figure 3 shows the results of 3 passes of BorDip using marginal FMI data from a highly deviated well in the Gulf of Mexico. The first tadpole track shows the dips computed by running BorDip with default parameters. The second set of tadpoles were computed using a fixed plane for focusing. The third tadpole track is from a pass using the results from the previous pass as a variable focus and using the modified correlation links. The dips drastically improved and they are correct as compared to manually picked dips.

Figure 3

Dipmeter/Image Repair______________________________________________________________ 5

Recommendations:
If you do not know what sort of dips to expect, start by making a reconnaissance pass of BorDip run on defaults. If necessary, use BorView to find the dip trend to use as a focusing plane. If you are not expecting high dips or you are using a focusing plane, set the Search Angle to 40 and use Fixed Plane. Make a second pass using: Correlation Cutoff = 0.25 Search Angle = 20 Variable Plane Previous output for focusing Change the correlation links if you have poor input data

Hints: BorDip does not work well when bad buttons are included. It is good practice to kill obviously bad or flaky buttons. BorDip does not have the double angle search option. In CorDip you could input a search angle value of something like 135 , which would tell CorDip to first search 35 and if no dip were detected then search out an additional 35 to try to find a dip. In BorDip, if you put in 135 , it interprets that literally and will most likely give trash results. If you really want a 70 search angle, put in 70 not 135 .

Dipmeter/Image Repair______________________________________________________________ 6

GPIT_Survey
The GPIT_Survey module is invaluable for determining the quality of the inclinometry data as well as for performing some of the more common fixes to GPIT data. It is the only means of validating the usability of the inclinometry data and should be run on EVERY job. The earths magnetic field is changes with your location on the earths surface and also varies slowly over time. By default, GPIT_Survey picks up the date, latitude and longitude from the input data file. If Date was not set in the raw data file, GPIT_Survey will probably crash. If this happens, use the Data Manager to set an appropriate Date, then restart the module. In the middle of the panel, there 3 columns of data. The first or Used are the earth constants as read from the raw data. The second column or IGM contains the constants as determined from a lookup table based on the values of date, latitude and longitude. These two columns should closely agree and should conform to known values for the local area. It is not uncommon for latitude and longitude values to get mistyped. The third column, Averaged log, has the calculated values for the earth constants based on the accelerometer and magnetometer data. If the tool is operating properly, these Averaged log values should be close to know values. GF3.0 even alerts you hen these values are out of tolerance. In the example below, there is an obvious problem with the accelerometer and magnetometer data.

Averaged log values are obviously bad.

Dipmeter/Image Repair______________________________________________________________ 7

Selecting GPIT Data Processing, will produce crossplots of the XY accelerometer and magnetometer data. Normally these will appear as circles, spirals or portions thereof, centered on zero. The accelerometers look totally useless but the magnetometers seem to be showing something consistent, but most of it is off scale.

First we want to determine if part of the interval is good. By selecting the second icon on the left, we can reset the depth interval. Looking at only the lower section of data, we get more reasonable looking crossplots. The accelerometer data still contains some junk data since the max gravity value is bad.

Dipmeter/Image Repair______________________________________________________________ 8

After reducing the depth interval by another 5, only good data is included.

The magnetometer data now shows a nice circle and the accelerometer crossplot is a spiral. Spirals occur when the hole deviation is changing. You will get larger amplitudes at higher well deviations. In this case, the well is nearly vertical at the top of the interval and slowly builds to a high deviation at the bottom. The circular nature of these plots is due to the rotation of the tool. As the tool makes a complete rotation, a circle is swept. If the tool was run on TLC equipment there with probably be little tool rotation and only an arc of a circle is seen. This is OK. The only problem now seen is that the crossplots are not centered on zero. In hot holes the accelerometers and magnetometers tend to drift a bit which is the case here. By selecting the

Dipmeter/Image Repair______________________________________________________________ 9

first icon on the left, we can rescale the X and Y data to make them centered. A little bit of arithmetic will give you the offsets that need to be applied to each component. Calculated offsets needed Accelerometers -0.190785 0.016910 Magnetometers 0.09733 0.05085

X Y

Xplots after offsets have been applied to accelerometers and magnetometers. After each fix is applied, the Averaged log values are updated so that you can see if the calculated values are now within tolerance. The reconstructed values now look good for the norms.

Dipmeter/Image Repair______________________________________________________________ 10

If a single magnetometer or accelerometer is dead, it is often possible to use the recompute option to fix it. In this procedure, the 5 good components and the known values for the earth norms are used to calculate the missing channels. This option must be used carefully since the calculation can sometimes fail. Look at the results closely. When more than one of the 6 components are dead, GPIT_Survey cannot be used to produce a fix ( as of GF3.0). However, there is a LOGOS program named GPIPRE which allows one to do more extensive repairs when an independent deviation survey is available. Use GPIPRE to rebuild the inclinometry using only the accelerometers and the independent HAZI channel. Run BorEID and other processing on the VAX. If all the magnetometers are good and the accelerometers are bad, you will need both DEVI and HAZI data for GPIPRE to be able to reconstruct the inclinometry. Sometimes the customer supplied deviation information is not in a convenient form. Below is a rather extreme case where only the latitude and longitude values for the well at various depths is given.

Dipmeter/Image Repair______________________________________________________________ 11

Deviation Survey from customer

The following procedure can be used to convert this raw data to something usable. 1. 2. 3. 4. 5. Find change in Latitude and Longitude for each depth Convert to change in Feet East or North Calculate Hole Azimuth In WellEdit create a new HAZI channel with these values Output new HAZI to a dlis file, read into LOGOS

Dipmeter/Image Repair______________________________________________________________ 12

Typical LOGOS GPIPRE Dialogue

Dipmeter/Image Repair______________________________________________________________ 13

GPIT Speed Correction I am a firm believer in using the sticking detection logic in BorEID under GPIT Parameters. This option can often significantly improve the speed correction results in sticky holes. However, you have to use a little caution when using this feature. In very smooth holes where there is little activity on the Z-accelerometer the sticking logic can be activated erroneous depth shifts created. Also in very sticky holes, the Kalman filter can blow up, producing some very bad outputs. Unfortunately, these incorrect shifts are often not noticeable on the images. It is necessary to check the playback to make sure that the depth correction did not do anything strange. There should be some reasonable correlation between the computed stuck sections and the values seen on the cable tension.

Dipmeter/Image Repair______________________________________________________________ 14

Sticking Detection - OFF

Sticking Detection - ON

The playback above in a sticky hole with sticking detection turned off shows a reasonable computed DEPTH_SHIFT curve. For the case with the righthand display, the sticking logic caused the Kalman filter to blow up. Note that the DEPTH_SHIFT curve, even at a compressed scale, slowly marches off the page. Something like this will result in a large section of good data being cut out. The depths will be incorrect but this will most likely not be obvious on the images. When the speed correction blows up it is sometimes necessary to shock the algorithm to make it give reasonable results. Setting the Recovery Speed Factor to an abnormally high value such as 20 will get the processing working again.

Dipmeter/Image Repair______________________________________________________________ 15

Sticking Detection - ON , Recovery Speed Factor = 20

Another commonly encountered problem in processing GPIT data occurs when sections of the data are bad. This can cause BorEID to fail completely or produce very long pulls on the images. Sometimes a bad pull over say 20 feet may cause the speed corrected images to show a pull of 200 feet or in some cases the entire section above the pull will be bad. Since the GPIT data is processed over the entire logged interval, changing the Start and Stop depths in BorEID will not cure the problem. The cleanest way to handle this is to first locate the sections of good data, then go back to Data_Load and load only the good sections. This way BorEID sees only good data and should run fine.

Dipmeter/Image Repair______________________________________________________________ 16

FMS Tools Logged in an Incorrect Mode

There are three types of FMS tools: MESTA - 2 pad tool MESTB - Slim hole tool MESTC - 4 pad tool If the logging engineer inputs the wrong sonde type during acquisition, you will have to intervene in the processing to get correct results. The processing software, both LOGOS and GeoFrame, key off of some of the tool parameters. If these are incorrect, the output will not be right. The following should help you repair the two most common problems. -------------------------------------------------------------------------MESTB tool logged as a MESTC , LOGOS Processing After the data has been loaded, in MAPUTL, change the "BUTTON SPACING" from 0.15 to 0.12 . Otherwise the processing is the same. -------------------------------------------------------------------------This is to change a MEST tool that was ran in (2)pad mode to (4)pad mode. The job has to be processed in LOGOS on the VAX. If you have a DLIS file, first convert it to LIS. The following steps will produce an LIS file which will load and process correctly on the VAX. $ASSIGN SYS$OUTPUT FOR$PRINT $DS/GO LISU $ASSIGN/BLOCKSIZE=8192 SAMDI0.DAT $ASSIGN/BLOCKSIZE=8192 SAMDI2.DAT/WRITE $TEMP/BUILD/MEDIT ! You will be in edit mode . ! At the first of each line of a "CONS" file, replace the first ! character ( Usually an "L" ) with a "*" $TEMP/ANA/SHOW $TEMP/BUILD/APPLY/TEDIT ! You will be in edit mode . ! Search for "MLM", then change (FSCA to 4SCA) or (1800 TO 4180) $TEMP/GO/ANAL $EXIT

Dipmeter/Image Repair______________________________________________________________ 17

CALIPER Problems with SHDT/FMS/FMI Tools ------------------------------------------------------------The most common caliper problem is one of simple miscalibration. The tool is actually working properly but the output values are incorrect. This is a relatively straight-forward problem to fix. If the calipers are not operating correctly, it is usually necessary use the caliper information from other tools. Assuming that the calipers have been miscalibrated, it is first necessary to obtain a good set of calibrations for that tool from the field and to read the bad set of calibrations from the data tape. Then the bad calibration has to be removed and the good calibration applied. This is basically a simple algebra problem of solving two equations for two unknowns. y1 = m1 * x1 + b1 y2 = m2 * x2 + b2 where: x1 = Raw C1 reading x2 = Raw C2 reading y1 = Calibrated C1 reading y2 = Calibrated C2 reading m1 = Gain applied to Raw C1 reading m2 = Gain applied to Raw C2 reading b1 = Offset applied to Raw C1 reading b2 = Offset applied to Raw C2 reading If we use subscripts of "b" for the original bad calibration and "g" for the new, good calibrations, the following transforms should provide the desired results.

( y1b - b1b ) y1g = m1g * (--------------) + b1g ( m1b )

( y2b - b2b ) y2g = m2g * (--------------) + b2g ( m2b )

These transforms can be applied in LOGOS by using MAPUTL or in GeoFrame through "Data Functioning" in the Playback module.

Dipmeter/Image Repair______________________________________________________________ 18

Similarly, when the original caliper data is unusable, "Data Functioning" can be used to generate C1 and C2 channels using caliper data from other tools.

Dipmeter/Image Repair______________________________________________________________ 19

FMI Pad/Flap Overlap

The relative positions of the FMI Pads and Flaps change azimuthally around the borehole depending on hole diameter. The flaps are offset vertically from the pads by a constant distance ( 5.7" ). The flaps are NOT offset azimuthally by a constant distance. This offset or gap changes with borehole diameter.

-----------------------------| | | PAD | | | --- | o o o o o o o o o o o o | | | o o o o o o o o o o o o| | | | | | | | | | | -----------------------------| | | 5.7 inches ->| |<- GAP | | | | ------------------------------| | | | | FLAP | | | | --| oo o o o o o o o o o o | | o o o o o o o o o o o o| | | | | | | ------------------------------

Pad/Flap as viewed from inside the wellbore

Dipmeter/Image Repair______________________________________________________________ 20

In boreholes larger than 6.75 inches, the resulting orientations are thus:

Pads/Flaps ____ ____ | 4 | | 1 | | | ____ | | _____ || 8 | || 5 | || | || |

Images _________ | || | |4 || 8 | | || | | || | _________ | || | | 1 || 5 | | || | | || |

The tool is opened sufficiently that there is only a small gap between the pad and flap on each arm of the tool. The gap between each pad/flap assembly will increase as the hole size increases.

In boreholes less than 6.75 inches, the orientations are: Pads/Flaps ____ ____ | 4 | | 1 | | | _ | | _____ | | 8 | | | 5 | | | | | | | ____ | | |4 | | | | | Images _________ | | | | 8 | 1 | | | | | | | ____ | | | 5 | | | | |

The tool is only partially open. There is a gap between the pad and flap on each arm of the tool. There is an overlap of the flap from one arm with the pad on the adjacent arm. For this case, flap #8 overlaps the adjacent pad #1. The gap between the pad and flap on each arm of the tool will increase ( gap between #4 and #8, between #1 and #5 ) as the hole size decreases. This projection scheme can sometimes give the appearance of a pad-to-flap mismatch when in fact the speed correction is good. If the images are presented with say a 6.75 bit size and the hole is washed out to 9, then the images may appear to be poorly speed corrected. It is easy to check if this is truly the case. Find what values the calipers are reading and change the bitsize accordingly. In LOGOS, to get the images to align properly azimuthally around the borehole some of the display parameters must be changed. For LGG, if you use

Dipmeter/Image Repair______________________________________________________________ 21

GEOL_SLG_BLD to build the sidefiles, this computation will be taken care of for you. If you use "canned" sidefiles, it will be necessary to edit them appropriately.

Dipmeter/Image Repair______________________________________________________________ 22

For display on the workstation, changes need to be made in the "HEADER_FORMATS.DAT" file before running VAXSUN. The default assumes a pad/flap gap of 0.0 .

HEADER_FORMATS.DAT
/* FMI FLAP A */ TYPE 35 NAME FMI FLAP A CHAN_NAMES UNITS_NAMES OFFSET_ANGLE 0.00 OFFSET_DISTANCE 2.4 Add the appropriate gap ( from the following table ) to the 2.4 to get the flaps positioned correctly. For instance, for a 6.5" hole, 2.4 + 0.501 = 2.901 . For a 10" hole, 2.4 + 0.332 = 2.732 . This value should be the same as the "Arc Dist" entry in the GAP table. There are 4 flaps, so remember to set this OFFSET_DISTANCE for all flaps. ==========================================================

Dipmeter/Image Repair______________________________________________________________ 23

GAP TABLE
Bit size Gap Arc Dist Coverage Overlap inches inches inches % inches ---------- -------- ----------------------6.000 0.547 2.947 88.387 0.635 6.500 0.501 2.901 90.183 0.196 7.000 0.463 2.863 87.308 0.000 7.500 0.431 2.831 81.487 0.000 8.000 0.400 2.800 76.394 0.000 8.500 0.380 2.780 71.901 0.000 9.000 0.363 2.763 67.906 0.000 9.500 0.346 2.746 64.332 0.000 10.000 0.332 2.732 61.115 0.000 10.500 0.319 2.719 58.205 0.000 11.000 0.306 2.706 55.560 0.000 11.500 0.295 2.695 53.144 0.000 12.000 0.285 2.685 50.930 0.000 12.500 0.276 2.676 48.892 0.000 13.000 0.267 2.667 47.012 0.000 13.500 0.259 2.659 45.271 0.000 14.000 0.252 2.652 43.654 0.000 14.500 0.245 2.645 42.149 0.000 15.000 0.239 2.639 40.744 0.000 15.500 0.233 2.633 39.429 0.000 16.000 0.227 2.627 38.197 0.000 16.500 0.222 2.622 37.040 0.000 17.000 0.217 2.617 35.950 0.000 17.500 0.212 2.612 34.923 0.000 18.000 0.208 2.608 33.953 0.000 18.500 0.204 2.604 33.035 0.000 19.000 0.200 2.600 32.166 0.000 19.500 0.196 2.596 31.341 0.000 20.000 0.193 2.593 30.558 0.000 20.500 0.189 2.589 29.812 0.000 21.000 0.186 2.586 29.103 0.000 =======================================

Dipmeter/Image Repair______________________________________________________________ 24

FMS sensor array FLIC processing numbering convention +-------------------------------+ row 4 | 4| 8 12 16 20 24 | ---+ | | | | 0.4" row 3 | 3 | 7 11 15 19 23 27 | ---+ | | | | 0.4" row 2 | 2 |6 10 14 18 22 26 | ---+ | | | | 0.4" row 1 | 1 5 9 13 17 21 25 | ---+ +-------------------------------+ | | | | | | | +---+---+---+---+---+---+ .4" .4 .4" .4" .4" .4"

4-pads FMS tool MEST-C, MEST-B (PTYP=MEC) +----------------------------------+ row 2 | 2 |4 6 8 10 12 14 16 | ---+ | | | | 0.3" row 1 | 1 3 5 7 9 11 13 15 | ---+ +-----------------------------------+ | | | | | | | | | +--+- -+--+--+---+---+---+--+ .3" .3 .3" .3" .3" .3" .3" .3"

4-pads FMS tool MEST-B (PTYP=HR) - Slim hole tool +-----------------------------------+ row 2 | 2 |4 6 8 10 12 14 16| ---+ | | | | 0.3" row 1 | 1 3 5 7 9 11 13 15 | ---+ +----------------------------------+ | | | | | | | | | +--+--+--+---+---+---+---+---+ .24 .24 .24 .24 .24 .24 .24 .24 (inches)

FMI tool +-----------------------------------------------------+ row 2 | 2 |4 6 8 10 12 14 16 18 20 22 24| ---+ | | | | 0.3" row 1 | 1 3 5 7 9 11 13 15 17 19 21 23 | ---+ +-----------------------------------------------------+ | | | | | | | | | | | | | +--+--+--+---+---+---+--+---+---+---+---+---+ .2" .2" .2" .2" .2" .2" .2" .2" .2" .2" .2" .2"

Dipmeter/Image Repair______________________________________________________________ 25

Order of FMS and SHDT buttons on the tool for the 2-pad FMS (tool seen from above) :

North 27 1 S1 1 1A * * | | | 1 4A * | * 2 27 West --------O-------East 27 4 * | * 2A S2 1 | | | * * 3A 3 1 27 South

For the 4-pad FMS tool the scheme is the following (tool seen from above) :

North 16 1 * * | | | 1 * | * 16 West --------O-------- East 16 * | *1 | | | * * 1 16 South

Dipmeter/Image Repair______________________________________________________________ 26

For the FBST(FMI) tool the scheme is the following (tool seen from above) :

North 24 1 * *24 1 * * | *24 | | *1 1 * | * 24 West --------O-------- East 24 * | *1 1* | | 24 * | * * 1 24* * 1 24 South

The order of the buttons in the SHDTxxx.00x files is the following: S1 1 2 3A 4A S2 1A 2A 3 4 The order of the buttons in image files is always 1-16 or 1-27 or 1-24 as above.

Extraction of pseudo-SHDT data For 4-pad FMS tool or FBST tool, MSTCIS automatically extracts pseudo-SHDT data when the corresponding SHDTRB.xxx file does not exist. This allows dip computation as for SHDT tool. To fit the SHDT pad geometry, buttons 13 and 5 are extracted from the 4-pad FMS data on every pad, and buttons 19 and 7 are extracted from the FBST pad data. There is no data for the so-called 'speed buttons'.

Dipmeter/Image Repair______________________________________________________________ 27

FMS Raw Channels

channel names output file 2-pad tool : MDRB

contents

SHDTRB.00n SHDT fast channels (10 channels - sampling 0.1") MESTB3.00n FMS fast channels, pad 3 (27 channels - sampling 0.1") MESTB4.00n FMS fast channels, pad 4 (27 channels - sampling 0.1")

MRBA

MRBB

experimental 4-pad tool : MDRB + MRBA + MRBB MESTB1 + MESTB2 + MESTB3 + MESTB4 4 times 16 fast channels (sampling 0.1") 4-pad tool : MDRB SHDTRB.00n pseudo-SHDT fast channels (10 channels - sampling 0.1") MESTB1.00n FMS fast channels, pad 1 (16 channels - sampling 0.1") MESTB2.00n FMS fast channels, pad 2 (16 channels - sampling 0.1") MESTB3.00n FMS fast channels, pad 3 (16 channels - sampling 0.1") MESTB4.00n FMS fast channels, pad 4 (16 channels - sampling 0.1")

MRPA

MRPB

MRPC

MRPD

Dipmeter/Image Repair______________________________________________________________ 28

FMS Edit Channels

channel names output file standard tool : SBi - DBi

contents

SHDTRB.x0n (pseudo-)SHDT fast channels (sampling 0.1") MESTB3.x0n FMS fast channels, pad 3 (volts) (27 channels - sampling 0.1") MESTB4.x0n FMS fast channels, pad 4 (volts) (27 channels - sampling 0.1")

B3ij

B4ij

4-pad tool : B3ij or BCij MESTB3.x0n FMS fast channels, pad 3 (volts) (16 channels - sampling 0.1") B4ij or BDij MESTB4.x0n FMS fast channels, pad 4 (volts) (16 channels - sampling 0.1") B1ij or BAij MESTB1.x0n FMS fast channels, pad 1 (volts) (16 channels - sampling 0.1") B2ij or BBij MESTB2.x0n FMS fast channels, pad 2 (volts) (16 channels - sampling 0.1")

Order of 2-pad FMS channels in the output file : Bi11, Bi21, Bi31, Bi41, Bi12, Bi22, ...., Bi46, Bi17, ..., Bi37 Order of 4-pad FMS channels in the output file : Bi11, Bi21, Bi12, Bi22, ...., Bi26, Bi17, Bi27, Bi18, Bi28 Order of the (pseudo-)SHDT channels : SB1, DB1, DB2, DB3A, DB4A, SB2, DB1A, DB2A, DB3, DB4

Dipmeter/Image Repair______________________________________________________________ 29

FMI Channels

channel names output file standard tool : SBi - DBi

contents

SHDTRB.x0n pseudo-SHDT fast channels (sampling 0.1") FMI1.x0n FMI fast channels, pad A, rows 1 and 2 (24 channels - sampling 0.1") FMI5.x0n FMI fast channels, flap A, rows 3 and 4 (24 channels - sampling 0.1") FMI2.x0n FMI fast channels, pad B, rows 1 and 2 (24 channels - sampling 0.1") FMI6.x0n FMI fast channels, flap B, rows 3 and 4 (24 channels - sampling 0.1") FMI3.x0n FMI fast channels, pad C, rows 1 and 2 (24 channels - sampling 0.1") FMI7.x0n FMI fast channels, flap C, rows 3 and 4 (24 channels - sampling 0.1") FMI4.x0n FMI fast channels, pad D, rows 1 and 2 (24 channels - sampling 0.1") FMI8.x0n FMI fast channels, flap D, rows 3 and 4 (24 channels - sampling 0.1")

FBA1 + FBA2

FBA3 + FBA4

FBB1 + FBB2

FBB3 + FBB4

FBC1 + FBC2

FBC3 + FBC4

FBD1 + FBD2

FBD3 + FBD4

Order of FMI channels in the output file : x101, x201, x102, x202, ...., x112, x212 or x301, x401, x302, x402, ...., x312, x412 for x = A, B, C or D Order of the pseudo-SHDT channels : SB1, DB1, DB2, DB3A, DB4A, SB2, DB1A, DB2A, DB3, DB4

Dipmeter/Image Repair______________________________________________________________ 30

Image files (FMS : MESTBi, FMI : FMIi) : - header.I(6) = pad number i - header.I(7) = number of pads on the tool (2 or 4 for FMS, 8 for FMI) - header.I(8) = number of rows on every pad (4 for 2-pad FMS; 2 for 4-pad FMS; 2 for FMI) - header.R(4) = distance between buttons (inches) 0.1 = 2-pads FMS tool 0.15 = 4-pads FMS tool MEST-C, MEST-B (PTYP=MEC) 0.12 = 4-pads FMS tool MEST-B (PTYP=HR) 0.1 = FMI tool - header.R(5) = distance between rows (inches) 0.4 = 2-pads FMS tool 0.3 = 4-pads FMS tool 0.3 = FMI tool

SHDTRB file : - header.I(9) = origin of data 1 = standard SHDT 2 = FMS 2-pad 3 = FMS 4-pad 4 = FMI