1 / 9

Rationale for Rev3 proposals

Rationale for Rev3 proposals. Rune Hagelund WesternGeco. General. All headers blocks have a identification byte (byte 32) to allow blocks to be optional and be placed in e.g. Trace header in any order. A table in SEGD standard will identify all types of header Client info

manning
Download Presentation

Rationale for Rev3 proposals

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Rationale for Rev3 proposals Rune Hagelund WesternGeco

  2. General • All headers blocks have a identification byte (byte 32) to allow blocks to be optional and be placed in e.g. Trace header in any order. • A table in SEGD standard will identify all types of header • Client info • Channelset block 1 • Channelset block 2 • Position block 1 • Position block 2 • AIrgun source • Vibroseis source • Additional source info • Extended trace header info 1 • Etc etc

  3. General headers • Added (optional?) header blocks • Vessel/crew identification (with abbreviation?) ASCII*32 • Area name (with abbreviation?) ASCII*32 • Client name (with abbreviation?) ASCII*32 • Job name/number/identification ASCII*32 • Line name/number/identification ASCII*32 • More accurate timestamp defined (exactly defines time of first sample) • Used in general header • Source header • Trace header • Defined as a 64 bit unsigend integer counting number of microseconds since 1jan1980

  4. Source header • Used to be General header N • Expand source header to contain most of SPS (needed to process SEGD automatically) • Need more than 32 bytes -> put common info into extended source info header • Can be put into trace header (e.g. in case of slipsweep acquisition)

  5. Channelset • Reformatted due to large number of new requirements • Samplerate • Starttime/stoptime • Number of channels/samples • Filter definition extended • 64 bytes (Channeset header block 1 & 2) • Removed sensitivity from chset header (put into trace header) (only sensors with same sensitivity could be in same channelset, needed data for it to be valuable, each sensor have different sensitivity)

  6. Trace header • Increased in size (255*32 byte) • Partly defined in SEGD standard • Partly user defined (more space available than in rev 2.x) • Can contain position of trace • Can contain source headers

  7. Positions • Consists of one or more 32 byte data blocks TBD • Contains timestamp, quality, type • Can be attached to any trace or source header • Can have several versions in same trace header

  8. General trailer • Completely reformatted from Rev 2.x • Consists of separate blocks of different (userdefined) information • Each block starts with a description block defining type and size. • Some blocks predefined • Edits • Positions (SEGD, P1, P2) • Text comments • Observer log • TOC? [GT Desc Block (32 byte)][Block 1 (x*32byte)][GTDB][Block2][GTDB][Block3]....

  9. Table Of Contents file • Separate file written after last last seismic file on tape • Optional? May not fit • Lists contents of tape • May be written to disk file Requirements for SPS • Contains some (most?) of the info in SPS x file • May be generated from SPS X file?

More Related