Horizon Utility Howto's


Howto extract Elevations, Fold and Total Statics as seismic horizons

elev.gif
fold.gif
static.gif

Above we see a map view for extractions from the trace header. This processed 3D is a pre stack merge, can you tell where the merge line is? Let's extract all that good stuff out of the EnCana trace headers and create some horizons for: We get to use yet another perl script and here is how we do it. We will extract the data out of the first version of the line, no sense to create duplicate data. Here is the script header2hor.pl
ls *.0.sgy > junk
~ekeyser/perl/header2hor.pl
F101692.ECC-NWT-2003-25.2D-2003-25.f-pr-fk-pr-mig.200304.gox.sgy F101692 ECC-NWT-2003-25
P173286.ECC-MERG-033DM-1.3D-JENSENMERGE.test-istk.200302.gox.sgy P173286 ECC-MERG-033DM-1
P34808.43461.2D-43461.f-tpna-freq-tx-mig.200402.es.sgy P34808 43461
fini -- 
This perl script creates a file called elevations.asc. Here is what this file looks like:
more elevations.asc
4 -9999.99
ELEV C Blue
STATIC C Gold
FOLD C Peru
SP_loc  C Salmon
2D-2003-25                         103.000     541025.0   7697814.0   113    41     1     0
2D-2003-25                         103.500     541014.0   7697824.0   113    45     3    50
2D-2003-25                         104.000     541003.0   7697834.0   113    50     4     0
2D-2003-25                         104.500     540993.0   7697844.0   113    56     6     0
2D-2003-25                         105.000     540983.0   7697854.0   113    60     7     0
2D-2003-25                         105.500     540973.0   7697866.0   112    65     8    50
2D-2003-25                         106.000     540962.0   7697877.0   112    70     8     0
2D-2003-25                         106.500     540951.0   7697888.0   112    76     8     0
2D-2003-25                         107.000     540940.0   7697898.0   113    81     9     0
2D-2003-25                         107.500     540930.0   7697908.0   113    86    10    50
2D-2003-25                         108.000     540919.0   7697918.0   113    79    11     0
2D-2003-25                         108.500     540908.0   7697928.0   112    57    12     0
2D-2003-25                         109.000     540897.0   7697937.0   112    34    13     0
...
Load it into SeisX by Horizon, import and you are done!

Howto copy another project as your use

The first step is to create the directory structure where the SeisX project is going to be located. I recommend opening up the permissions with chmod 777. Use the tar command to copy the files to the new location. tar is better than a cp -R because links and dates are preserved. Here is the command I like:
cd /auto/fs63/jfong/seisx
tar -cf - alaska2  | (cd /auto/fs63/kroot/seisx; tar  -xBpf - )
Note: we are going to push the data from Jennifer to Kevin! The project may have moved but several of SeisX internal files need to have their pointers updated! I suggest that the user use sed to make these corrections. The files that need updating are: It's simple to use vi to make this change:
:%s/jfong/kroot/g
If your path to change is complicated you may find it easier to use sed. Here is how I do it:
mkdir tmp
mv project.history tmp/.
mv culture.dat tmp/.
mv map.pha tmp/.

sed s#sdonalds#progers#g < tmp/culture.dat > culture.dat
sed s#sdonalds#progers#g < tmp/project.history > project.history
sed s#sdonalds#progers#g < tmp/map.pha > map.pha
Note: we have preserved the original files in the tmp directory in case we screw up.

Your final step is to add the project to your .proj.lst_v3.00 file located in your user_support directory:

vi /home/ekeyser/user_support35/.proj.lst_v3.00
Add your project here:

Project
    "Alaska"
    "/auto/fs63/kroot/seisx/alaska2"
    "Jennifers Alaska project Nov 10, 2003"

Howto take a partial interpretation and give it a new name

Here are the steps:
 grep -v 9999.99 taglutemp.asc > c0.asc
Add the first line back into the card deck and give it the new name
1 -9999.99
C0 P Green
I'd suggest clearing out the horizon that you want to add the new information back into

Howto export 2D horizons from Landmark into SeisX project

Landmark Export Utility
Ahhhhh, this one isn't quick. Part of the problem stems from the fact that Landmark's standard export utility HIE is too smart. It automatically removes all underscores at the end of the line, this is a good thing but it also converts all underscores in the middle of the line to a sing space. This is a bad thing because the line name now is different that the name of the line in the landmark project and the time data will not fit the segy data. Hence we need a new landmark program called mltexp_SunOS. It's sort of unsupported and resides at EnCana as /apps/R2003/SeisUtils/bin/mltexp_SunOS. What you have to do is open a Landmark xtermina and execute the following:
/apps/R2003/SeisUtils/bin/mltexp_SunOS
Select the default format, 2D project making sure the data are exported in ascii format and select a single horizon. All multiple horizons do is append the output. SeisX doesn't like this. The next step we have to do is copy the file from the Landmark location to where the data can be read into SeisX and reformat this file (remove the suffix underscores, label the horizon) with our perl script fix_.pl Here's how:
cp /intl/alasmacs/seis1/alaska/horizon.dat junk
~ekeyser/perl/fix_.pl > fix.asc
All you need to do is now read the data into SeisX with (Horizon), (Import Horizons)

Howto resample a 3D to any line increment

Here is the problem, I have spent months interpeting a 3D and I still have some bad horizon picks. I'd like to resample the 3D to some fixed even increment. SeisX lets you export an odd increment. Here's how, export all horizons as a file, edit the thin3d.ak script to change the increment from 32 to what ever you desire and run the script.
awk -f ~ekeyser/ak/thin3d.ak < burntlake_hor.asc > burntlake_hor_32.asc
Note that the new file is very much smaller and you probably can edit the header if you want to change the name of a horizon for your 3D and do not want to change the name for all the other lines in the project.

Howto transfer a 3D horizon between different size versions

Here is the problem. A year ago we purchased the Caroline 3D, line 651-1208, traces 4740-5320. Today we purchased more of the same 3D and have lines 652-1435 and cross lines 4609-5408. Here's how:

Howto export a 3D horizon from Landmark for use with SeisX

From the OpenWorks command menu. Select Data, Management, Seismic Project Manager Horizons, Hie.

Select the project, Survey, File Export Horizons. Select hz3dtr for Format file and give the Output File a name you can find. Remember, Landmark will place this file in the disk pack with the most space in your dir.dat.

Select your Z Field (horizon) and press Apply. This will output Line Trace and a value.

Howto find where Landmark outputs a file

This one is a little complicated. From the OpenWorks Comman Menu open an Xterminal. System, Unix Window. T ype in the following command:
43 sun803:/home/ekeyser % echo $OW_PMPATH
/auto/havana1/apps/lgc/conf_wnv
Go to this directory and take a look at your dir.dat. This is the magic file that landmark uses to determi ne where your data belongs.
46 sun803:/auto/havana1/apps/lgc/conf_wnv % head dir.dat
/auto/fs32/lgc_data sys global
/auto/fs60/lgc_data global
/auto/fs61/lgc_data global
/auto/fs65/lgc_data global
I have written a simple awk script that will find where Landmark has placed your file. You must first edit the Name of the the SeisWorks project (replace the burntlk3) and the $OW_PMPATH. The script will read your dir.dat and locate your file.
awk '{printf("find %s/burntlk3 -name eric_find_me\n", $1)}' /auto/havana1/apps/lgc/conf_wnv/dir.dat > run.
job
chmod +x run.job
./run.job
Here is what the job screen looks like:
72 sun803:/home/ekeyser % awk '{printf("find %s/burntlk3 -name eric_find_me\n", $1)}' /auto/havana1/apps/l
gc/conf_wnv/dir.dat > run.job
chmod +x run.job
./run.job
73 sun803:/home/ekeyser % 74 sun803:/home/ekeyser % /auto/fs60/lgc_data/burntlk3/eric_find_me
We found the file!

Howto import a 3D Landmark file into SeisX

Here is what the Landmark file hz3dtr looks like:
{29} sun801:/dat/photon/p007042/Mac3/asc % head eric_find_me
                729.      605.               1856.
                728.      605.               1853.
                727.      605.               1852.
                726.      605.               1851.
                725.      605.               1849.
                724.      605.               1845.
                723.      605.               1843.
First step is to edit the lm3d2sx.ak awk , changing the constant information, horizon name, Horizon type, Colour and 3D name. We must first sort the data and run an awk to reforat the data for SeisX.
sort < eric_find_me > sort_eric
nawk -f /home/ekeyser/ak/lm3d2sx.ak  < sort_eric > taglu777.asc
Our output looks like:
{30} sun801:/dat/photon/p007042/Mac3/asc % head taglu777.asc
1 -9999.99
Taglu777 P Red
#3D_GRIDNAME burntlk_16bit
   10    32 555555.55 7777777.77   2090
   10    33 555555.55 7777777.77   2087
   10    34 555555.55 7777777.77   2085
   10    35 555555.55 7777777.77   2084
   10    36 555555.55 7777777.77   2081
   10    37 555555.55 7777777.77   2078
   10    38 555555.55 7777777.77   2077
Notice the dummy XY's SeisX reads the data from line and trace, not XY! In order to read the data, select Horizon, Import horizon. If you have sorted the data first, it will read in very quickly.

Howto read and grid contour a XYZ file in SeisX

Your data must be space limited and XY's specified (not Lat Long). First count the number of lines.
{35} sun801:/dat/photon/p007042/Mac3/asc % wc -l < taglu_pat
  318593
Here is what need to be added to your card deck:
#Photon Systems ASCII Format v1.0

struct DATA_SET[N]{
        X
        Y
        Z
}
DATA_SET 3
569330.125 1042500.250  582.213
569340.125 1042500.250  582.464
569350.125 1042500.250  583.338
...
Add the first few cards above to your xyz file and change the number of samples (change 3 to 318593)

Select Horizon, Grid&Contour, ASCII and grid the file like any other. I use this function to take a digitized time horizon map to generate and convert a grid to a horizon.

Howto transfer a 3D horizon between different size versions

Here is the problem. A year ago we purchased the Caroline 3D, line 651-1208, traces 4740-5320. Today we purchased more of the same 3D and have lines 652-1435 and cross lines 4609-5408. Here's how:
Last Updated: Feb 23, 2004