-
-
Notifications
You must be signed in to change notification settings - Fork 0
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
[FEA] Modify the NIP tomography programs to use stereotomography strategy #17
Labels
enhancement
New feature or request
Comments
Dirack
added a commit
that referenced
this issue
Feb 25, 2021
The program sfstereoniptomo uses the NIP sources to trace rays from them to acquisition surface in order to obtain the traveltime curve and to compare it with the CRE traveltime calculated values. The data misfit will be used to update the velocity model. We also add the program sfgetparameter to extract the parameters from parameters cube for (t0,m0) location given
Dirack
added a commit
that referenced
this issue
Feb 25, 2021
Picking of 26 nip sources and experiment repetition
Dirack
added a commit
that referenced
this issue
Mar 6, 2021
This script prepares the txt files generated by sfipick in a format readable by sfdd that convets them to RSF
Dirack
added a commit
that referenced
this issue
Mar 6, 2021
Backup of the input files needed to run this test and a setup SConscript. Run 'scons -f SConscript1' to setup input files and allow the test
Dirack
added a commit
that referenced
this issue
Mar 6, 2021
Generate the GDB version of sfgetparameter with 'make getparameter.x' command
Dirack
added a commit
that referenced
this issue
Mar 6, 2021
Utility python script to plot the NIP sources using depth coordinates and to plot m0s in the acquisition surface. To setup input files run 'scons -f SConscript2' and after run the viewNipSources.py script. It will load generated files and plot sources using matplotlib python library
Dirack
added a commit
that referenced
this issue
Mar 6, 2021
sfstereoniptomo is a program that does the forward modeling for a set if NIP sources given and normal ray angles
Dirack
added a commit
that referenced
this issue
Mar 23, 2021
Coordinates of the nipsources are optimized using VFSA and summation of time misfit root mean squared criteria
Dirack
added a commit
that referenced
this issue
Mar 23, 2021
Plot the true interface using the program viewNipSources.py
Dirack
added a commit
that referenced
this issue
Mar 23, 2021
The program sfnipmodsetup uses t0/2 instead of t0 and the casting is corrected
Dirack
added a commit
that referenced
this issue
Mar 23, 2021
Use VFSA optimization to locate nipsources. Do the process for each nipsource at time
Dirack
added a commit
that referenced
this issue
Mar 23, 2021
Use Makefile to run the experiment: 'make help' to get help. This experiment uses a two interfaces model with sfstereoniptomo
Dirack
added a commit
that referenced
this issue
Mar 23, 2021
Output the inverted velocity model after sfstereoniptomo finishes
Dirack
added a commit
that referenced
this issue
Apr 3, 2021
Dirack
added a commit
that referenced
this issue
Apr 3, 2021
Dirack
added a commit
that referenced
this issue
Apr 3, 2021
Merged
4 tasks
Merged
4 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
🎉 Feature request
Is your feature request related to a problem? Please describe.
The ray tracer should receive the RNIP and BETA parameters in order to determine CRE traveltime curve. From NIP point, two reflection rays are traced with angle TETA in relation to the normal determined by the normal ray that reaches NIP. Both rays should reach the acquisition surface.
After that, CMP and Offset coordinates are calculated and the time misfit is given by the difference between the CRE traveltime calculated and the sum of the traveltimes between these two reflection rays.
Describe the solution you'd like
A clear and concise description of what you want to happen.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered: