-
Notifications
You must be signed in to change notification settings - Fork 24
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Questions about the conversion of time domain data to frequency domain data #3
Comments
I have a similar problem. From the tutorial the FD used for the FWI seems to be source-receiver domain, and a regular FFT on the TD data won't work. I wonder if you have found a solution to this @chenzhaoxingxin . |
Hi everybody, Very good question, I have not applied GERMAINE to field data, yet. Therefore, I have no script to convert time-domain to frequency domain data. However, for this Radar TE modelling/FWI tutorial ... https://danielkoehnsite.wordpress.com/wp-content/uploads/2018/10/koehn_etal_2017_germaine_te_fwi.pdf ... I created a few Jupyter notebooks to convert frequency domain data to time domain data, e.g. on page 55, 60 or 67, to compare them with analytical solutions in the time-domain. So, in theory if you reverse the steps described in the notebooks, you should be able to transform time-domain data to the frequency domain. As a first step, it might be a good idea to use the available scripts to model frequency domain data for the initial model, convert it to the time-domain and compare it with the field data. Best regards, Daniel |
Hello, Dear Daniel.I downloaded and learned the program you released. You wrote it in great detail, which is very helpful for our study. In the application, I have a question to ask you. I found that the seismic record generated by the program is in frequency domain. If my actual seismic record is in time domain, is there any program that can change it into frequency domain data suitable for FWI stage of the program?
Thank you again for sharing the program and your contribution. Looking forward to your reply.
The text was updated successfully, but these errors were encountered: