<p>As you rightly say, data will normally be deghosted during processing.</p>

<p>However, sometimes the deghosting is performed by the acquisition company rather than the processing contractor. The most obvious example would be PGS Geostreamer data, where 'raw' field tapes supplied by PGS to the customer are the upcoming wavefield, with the receiver ghost already removed. This is because the process of combining the velocity sensor and hydrophone data to remove the sea surface reflection is PGS's secret sauce - in many ways building a multi-sensor streamer is the easy part. They work with the true raw data internally, but never supply it to anyone else.</p>

<p>This is normally fine, but if the data is later processed (or reprocessed) by someone else, then complications can arise. If this other processing company wants to perform Full Waveform Inversion, which involves modelling a synthetic wavefield and comparing to the recorded wavefield, then the absence of the receiver ghost will cause an issue. Since the boundary condition at the sea surface has to be reflective to model the multiples correctly. Thus, they may add the receiver ghost back into the data by making an assumption of the sea surface reflectivity and adding it back, creating a 'reghosted' dataset to compare to the synthetics within the FWI.</p>

<p>That said, this would be an internal working dataset for the processing company, not something that would be supplied to the client. So I am surprised you would come across it without knowing what it was, if you see what I mean.</p>

CC BY-SA 4.0
2018-05-19T14:01:34.003Z
2018-05-19T23:12:14.770Z
2018-05-19T23:12:14.770Z
WibblyWobbly
<p>I came across to a seismic volume labeled as <em>reghosted</em>. In my understanding, a seismic survey is deghosted as part of a processing step. Then I wonder why one would like to reghosted the data? Is there any benefit in reghosted? Is it maybe reghosted something different than bring the ghost back to the data? Is there a visual inspection to know a data set is deghosted?</p>

CC BY-SA 4.0
2018-05-19T23:02:21.073Z
Look at the amplitude spectrum of the data. A ghosted amplitude spectrum has very distinct "ghost notches". These look like the seismic has been filtered with a notch filter in periodic frequencies. If you see a smooth spectrum it was probably a typo.
Jesper
<seismology><seismic>
What does 'reghosted' mean in a seismic cube label?
fabioaco
# What does 'reghosted' mean in a seismic cube label?

(Asked by: username_0 on 2018-05-17)

I came across to a seismic volume labeled as *reghosted*. In my understanding, a seismic survey is deghosted as part of a processing step. Then I wonder why one would like to reghosted the data? Is there any benefit in reghosted? Is it maybe reghosted something different than bring the ghost back to the data? Is there a visual inspection to know a data set is deghosted?

**Tags:** seismology, seismic

> **Comments:**
> **username_1**: Look at the amplitude spectrum of the data. A ghosted amplitude spectrum has very distinct "ghost notches". These look like the seismic has been filtered with a notch filter in periodic frequencies. If you see a smooth spectrum it was probably a typo.  

---

## 1 answers

### Answer by username_2 on 2018-05-19. Score: 2

As you rightly say, data will normally be deghosted during processing.

However, sometimes the deghosting is performed by the acquisition company rather than the processing contractor. The most obvious example would be PGS Geostreamer data, where 'raw' field tapes supplied by PGS to the customer are the upcoming wavefield, with the receiver ghost already removed. This is because the process of combining the velocity sensor and hydrophone data to remove the sea surface reflection is PGS's secret sauce - in many ways building a multi-sensor streamer is the easy part. They work with the true raw data internally, but never supply it to anyone else.

This is normally fine, but if the data is later processed (or reprocessed) by someone else, then complications can arise. If this other processing company wants to perform Full Waveform Inversion, which involves modelling a synthetic wavefield and comparing to the recorded wavefield, then the absence of the receiver ghost will cause an issue. Since the boundary condition at the sea surface has to be reflective to model the multiples correctly. Thus, they may add the receiver ghost back into the data by making an assumption of the sea surface reflectivity and adding it back, creating a 'reghosted' dataset to compare to the synthetics within the FWI.

That said, this would be an internal working dataset for the processing company, not something that would be supplied to the client. So I am surprised you would come across it without knowing what it was, if you see what I mean.


---

