420 Posts in 208 Topics by 63 members
If this is your first visit, you will need to register before you can post. However, you can browse all messages below.
| Thread | Order: Newest | Oldest | Title | RSS Feed |
|
About Resstat module
Ok, thank you the precision ! Is it possible to have the articles on which you based the resstat module ? Thank you for your answer. 6 months ago |
||
|
About Resstat module
We don't have any article references for the RESSTAT module, it just follows the generic CDP-aligned residual statics methodology. Seismic Data Analysis by Öz Yilmaz, the residual statics corrections section, might be a good reference source. 6 months ago |
||
|
About Resstat module
Very well, thank you for your answers. 6 months ago |
||
|
Adaptive subtraction of frequency split multiple model
An approach that splits the multiple model into different frequency bands and adaptively subtracts these separately can prove to be a most effective way of attenuating multiple. The attached example flow (Freq_Split_Adaptsub_example.job) : • Reads in data. • Mutes any water column noise by applying a manually picked water bottom mute. • Stores the multiple model in a pseudotrace (SRME_MODEL). • Saves a copy of the data to a pseudotrace (TRACE_COPY). • Replaces the seismic trace... 2 years ago |
||
|
Advanced Marine Tutorial Documentation
Updated Advanced Marine Tutorial Documentation for the V6.5 release of GLOBE Claritas 2 years ago |
||
|
Anisotropic Pre-Stack time Migration
The IMAGE-K2T and IMAGE-K3T modules now allow for Anisotropic PreSTM, the anisotropy parameters can be derived in the Claritas Velocity Analysis package CVA as eta or horizontal velocities in Claritas format or externally if desired and supplied to the modules in SegY format again as eta fields or Vh. We also upgraded the algorithm from straight ray approximation to a higher fidelity curved ray implementation of the Kirchhoff migration operator. 2 years ago |
||
|
Apply DATUM_FIX module
HI, When I run the STATIC module, I want to compute my corrections from the refstat's workflow, plus a fix reference datum. The module explains that I should use the DATUM_FIX module, however, when I use it, my traces don't show that elevations corrections are applied. How should I use it in my flow ? Thank you, Matt. 3 months ago |
||
|
Apply DATUM_FIX module
What does your jobflow look like, could you attach it? The *.shf file output from the refstat application can be applied to data via the STATIC module. The DATUM_FLT - DATUM_SRD pairing of modules allows correction from acquisition datum to floating datum (a smoothed version of the topography) {DATUM_FLT] followed later by correction from floating datum to fixed seismic reference datum (SRD) [DATUM_SRD]. The DATUM_FLT module is normally applied at the start of the overall processing sequen... 3 months ago |
||
|
Apply DATUM_FIX module
My jobflow looks like this : 1 - SEISJOB 2 - SEISREAD 3 - ADDGEOM 4 - STATIC 5 - DATUM_FIX 6 - SEISWRITE Only my *.shf file is applied for the static correction, but no elevation correction. However, if I use the command "Datum" and "Vel_datum" in the STATIC module, some corrections are applied to my data. 3 months ago |
||
|
Apply DATUM_FIX module
Shifting to a floating datum and/or fixed seismic reference datum helps to correct for the effect of topography / elevation. Refractions statics (refstat application) on the other hand corrects for variation in near surface terrain. On land seismic surveys, we can expect the near surface terrain to vary significantly. In a few meters we might go from soft, marshy ground to a weathered outcrop. This can lead to large, localised velocity variations which distort the seismic travel times. Is... 3 months ago |
||