Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Introduction

Petrel will load the SEGY SEG-Y files generated by the SyQwest Bathy2010 CHIRP sub-bottom profiling system so that these can be incorporated into a project that includes the site survey seismic, core and logging data. This assumes that a project already exists with at least the basic information that is needed (map projection etc) – these are covered in the Petrel manuals if not.

The online SEGY files are likely to be easier to load into Petrel than those generated by ODC-SEGY conversion later. However the principles are the sameprinciples are the same, whether you are loading the raw, processed or OCD-converted SEGY files.

Procedures

  1. Start Petrel and load the existing project
  2. Right click on the appropriate seismic data folder in the Petrel project. Choose “Import (on selection)” with the “SEGY Toolbox” option (Fig. 1). The other
  3. SEGY
  4. SEG-Y load options
  5. won't
  6. are unable to extract the navigation information.
    Image Added
    Figure 1: SEG-Y file selected for import into Petrel using the SEG-Y toolbox (2D) workflow.

    Image Added
    Figure 2: Main window of the the SEG-Y toolbox (2D) workflow

  7. When the
  8. SEGY Toolbox starts
  9. SEG-Y toolbox starts (Fig. 2), the first thing is to sort out Byte positions – click on the “Define” button. Set Trace number, SP number, CDP number all to 9 – this is the only trace header that is properly set (Fig. 3). Leave X and Y coordinate as they are. Don't do anything with the “advanced” options. If you click “scan” you will get line graphs that hopefully relate to what you think you collected. Then
  10. hit OK
  11. click OK.
    Image Added
    Figure 3: Definition of SEG-Y byte positions.

  12. Navigation source will be SEGY trace coordinates
  13. In
  14. SEGY
  15. the SEG-Y overrides, click on
  16. Headers and
  17. the "Trace header coordinate unit' and set it to "Arc seconds" (Fig. 4). Although this is selected by default, and a geographic coordinate system is later specified, an error message may appear when the import process is executed.
    Image Added
    Figure 4: SEG-Y Overrides, Parameters tab.

  18. In the "Headers" tab of the SEG-Y Overrides window, check the box for “Zero
  19. coordinates” -
  20. coordinates', and you can keep the default "Interpolate from neighboring traces”, as the link to navigation is often problematic (Fig. 5).

    Image Added
    Figure 5: SEG-Y Overrides, Headers tab.

  21. For the Coordinate reference system (CRS), click "Specify" (Fig. 2). The Input File CRS will be WGS84 – the easiest way to choose this is to click on Select and type “geodet” into the filter (Fig. 6).

    Image Added
    Figure 6: Window for selecting the coordinate reference system (CRS).

  22. Finally click on , in the main SEG-Y toolbox window, click “Run” and the SEGY toolbox will translate the coordinates into the trace headers in the correct CRS for your project, and as long as you have “Load generated SEGY files to Petrel” checked the data will appear immediately in your catalogue (Fig. 7).
    Image Added
    Figure 7: Main SEG-Y toolbox window, with the required settings for importing a CHIRP sub-bottom profile. 

  23. Check as for any other new import: (map, interpretation windowa) location of profile in 2D map window; (b) interpretation window (Fig. 8). Note that the data are processed to be the envelope, ie only positive amplitude values >0 are present. Note also that the SEGY file that Petrel actually uses is in the “Output SEGY directory” location, not where the original data source was.. Also, the vertical exaggeration in the Interpretation window should be set high in order to see the reflectors. To do this, open the Interpretation window settings > Settings tab.
    Image Added
    Figure 8: Example of a Bathy2010 CHIRP sub-bottom profile displayed in an Interpretation window in Petrel.


Other notes:

  1. If you are using data from the

...

  1. SEG-Y conversion you will probably encounter a range of problems. The most serious is that the program occasionally puts in traces with different length or sample interval or both. You might be able to handle some of these with the SEGY overrides. Otherwise you will need to use a seismic processing package to fix the problems. For example this is a set of commands I used in Seismic Unix (a free processing package) to clean up data during Exp362:

 segyread tape=20161001134130P_zoom-LF-2.seg endian=0 | suwind key=fldr min=400 max=6120 | suwind key=dt min=200 max=300 | sushift tmin=5.4 tmax=5.7 | suximage perc=97

...

 segyread tape=20161001134130P_zoom-LF-2.seg endian=0 | suwind key=fldr min=400 max=6120 | suwind key=dt min=200 max=300 | sushift tmin=5.4 tmax=5.7 | segywrite tape=fixed_chirp2.seg endian=0 bfile=binary2a


Credits

This guide was originally written by Timothy Henstock (2016; Exp. 362 Logging Scientist)

Archived Versions

There are no archived versions of this document

...