Difference between revisions of "Synthetic seismograms: correlation to other data"
Jump to navigation
Jump to search
(Initial import) |
Cwhitehurst (talk | contribs) m (added Category:Treatise Handbook 3 using HotCat) |
||
| (11 intermediate revisions by 4 users not shown) | |||
| Line 6: | Line 6: | ||
| part = Predicting the occurrence of oil and gas traps | | part = Predicting the occurrence of oil and gas traps | ||
| chapter = Interpreting seismic data | | chapter = Interpreting seismic data | ||
| − | | frompg = 12- | + | | frompg = 12-17 |
| − | | topg = 12- | + | | topg = 12-17 |
| author = Christopher L. Liner | | author = Christopher L. Liner | ||
| link = http://archives.datapages.com/data/specpubs/beaumont/ch12/ch12.htm | | link = http://archives.datapages.com/data/specpubs/beaumont/ch12/ch12.htm | ||
| Line 14: | Line 14: | ||
| isbn = 0-89181-602-X | | isbn = 0-89181-602-X | ||
}} | }} | ||
| − | The goal of using a synthetic seismogram is to match stratigraphy as seen in well logs or outcrops to seismic field data. The field data need to have been migrated, since only then does the time axis represent vertical traveltime, which is calculated from sonic log measurements. | + | The goal of using a synthetic seismogram is to match [[stratigraphy]] as seen in well logs or outcrops to [[Seismic data|seismic field data]]. The field data need to have been [[Seismic migration|migrated]], since only then does the time axis represent vertical [[traveltime]], which is calculated from [[Basic_open_hole_tools#Sonic|sonic log]] measurements. |
==The matching process== | ==The matching process== | ||
| − | The matching process involves simulating a seismic trace from well logs and user parameters | + | The matching process involves simulating a [[seismic trace]] from well logs and user parameters [[Wikipedia:Waveform|waveform]], [[Wikipedia:Frequency|frequency]], [[Wikipedia: Phase (waves)|phase]], then manually aligning the simulated trace with the field trace(s) in the vicinity of the well. This is normally done over some limited interval in the well, probably centered on the reservoir target. If the fit is not good enough, then the parameters are changed (updated) and another comparison is made. This continues until a match is achieved. It can be a tedious and time-consuming job, particularly for large projects involving many wells. But if not done properly, it is possible to incorrectly associate seismic events and geological horizons. |
==Problems with matching== | ==Problems with matching== | ||
In practice, [[synthetic seismograms]] are rarely a perfect match to field data. There are many reasons for this. | In practice, [[synthetic seismograms]] are rarely a perfect match to field data. There are many reasons for this. | ||
| − | * '''Frequency'''—Sonic logging operates in the kilohertz frequency range (high frequency short wavelength), while seismic data are typically 10–90 Hz (low frequency, long wavelength). This means the sonic log is influenced by a tiny volume of rock compared to a seismic wave passing the borehole. | + | * '''Frequency'''—Sonic logging operates in the kilohertz frequency range (high frequency short wavelength), while [[seismic data]] are typically 10–90 Hz (low frequency, long wavelength). This means the sonic log is influenced by a tiny volume of rock compared to a seismic wave passing the borehole. |
| − | * '''Anisotropy'''—Sonic logs measure velocity in the vertical direction, while seismic waves travel at significant angles away from the vertical. If anisotropy is present (and it usually is), then velocity depends on the direction the wave is traveling. It is not uncommon to see a 10–15% difference between horizontal and vertical velocities. | + | * '''[http://wiki.seg.org/wiki/Dictionary:Anisotropy Anisotropy]'''—Sonic logs measure [[Wikipedia:Velocity|velocity]] in the vertical direction, while seismic waves travel at significant angles away from the vertical. If anisotropy is present (and it usually is), then velocity depends on the direction the wave is traveling. It is not uncommon to see a 10–15% difference between horizontal and vertical velocities. |
| − | * '''Hole'''—Sonic logging is sensitive to washouts and other hole problems, while long-wavelength seismic waves are not. | + | * '''Hole'''—Sonic logging is sensitive to [[Drilling problems|washouts and other hole problems]], while long-wavelength seismic waves are not. |
| − | * '''Wavelet'''—The user is required to specify the wavelet, and it is very easy to get it wrong. Some advanced software products can scan the data and attempt to extract the wavelet. But these scanners involve many user parameters. | + | * '''[[Wavelet]]'''—The user is required to specify the wavelet, and it is very easy to get it wrong. Some advanced software products can scan the data and attempt to extract the wavelet. But these scanners involve many user parameters. |
==See also== | ==See also== | ||
| − | * [[ | + | * [[Seismic data]] |
| − | * [[Synthetic | + | * [[Seismic data: building a stratigraphic model]] |
| − | * [[ | + | * [[Synthetic seismogram]] |
| + | * [[Seismic data: identifying reflectors]] | ||
==External links== | ==External links== | ||
| Line 39: | Line 40: | ||
[[Category:Predicting the occurrence of oil and gas traps]] | [[Category:Predicting the occurrence of oil and gas traps]] | ||
[[Category:Interpreting seismic data]] | [[Category:Interpreting seismic data]] | ||
| + | [[Category:Treatise Handbook 3]] | ||
Latest revision as of 19:10, 27 January 2022
| Exploring for Oil and Gas Traps | |
| |
| Series | Treatise in Petroleum Geology |
|---|---|
| Part | Predicting the occurrence of oil and gas traps |
| Chapter | Interpreting seismic data |
| Author | Christopher L. Liner |
| Link | Web page |
| Store | AAPG Store |
The goal of using a synthetic seismogram is to match stratigraphy as seen in well logs or outcrops to seismic field data. The field data need to have been migrated, since only then does the time axis represent vertical traveltime, which is calculated from sonic log measurements.
The matching process
The matching process involves simulating a seismic trace from well logs and user parameters waveform, frequency, phase, then manually aligning the simulated trace with the field trace(s) in the vicinity of the well. This is normally done over some limited interval in the well, probably centered on the reservoir target. If the fit is not good enough, then the parameters are changed (updated) and another comparison is made. This continues until a match is achieved. It can be a tedious and time-consuming job, particularly for large projects involving many wells. But if not done properly, it is possible to incorrectly associate seismic events and geological horizons.
Problems with matching
In practice, synthetic seismograms are rarely a perfect match to field data. There are many reasons for this.
- Frequency—Sonic logging operates in the kilohertz frequency range (high frequency short wavelength), while seismic data are typically 10–90 Hz (low frequency, long wavelength). This means the sonic log is influenced by a tiny volume of rock compared to a seismic wave passing the borehole.
- Anisotropy—Sonic logs measure velocity in the vertical direction, while seismic waves travel at significant angles away from the vertical. If anisotropy is present (and it usually is), then velocity depends on the direction the wave is traveling. It is not uncommon to see a 10–15% difference between horizontal and vertical velocities.
- Hole—Sonic logging is sensitive to washouts and other hole problems, while long-wavelength seismic waves are not.
- Wavelet—The user is required to specify the wavelet, and it is very easy to get it wrong. Some advanced software products can scan the data and attempt to extract the wavelet. But these scanners involve many user parameters.
See also
- Seismic data
- Seismic data: building a stratigraphic model
- Synthetic seismogram
- Seismic data: identifying reflectors
External links
| find literature about Synthetic seismograms: correlation to other data |
|
|
|
|