This module is used for reading internally produced data. The main objectives is whenever the user submitted a processing workflow comprising of Seismic loop or Migration procedure, it will creates a ".tmp" file along with .gsd & .gsd.sgy. The .tmp file stores all the processing information like how many sequences/gathers/files are processed etc. For an instance, if the procedure got interrupted or the procedure is not successfully executed/run, .tmp file knows that what is the last good sequence/gather/files. Next time when the user submits the job, it grabs the information from the .tmp file and start working from the next sequence/gather/file onwards. This way the user won't have to resubmit the job again from the scratch. This avoids repetition and saves lot of machine time.
When the user resubmits the job again, make sure to change the writing mode to DIRECT
Regarding the sequence numbering, the user must keep in mind that the sorting order is the one that gives the information about total number of sequences. For example, the user sorted the data in FFID - Channel sorting and information tab shows the total number of sorted gathers as 251 which means the sequence numbers are starting from 0 to 251. Similarly, if the sorting order is CDP - Offset and information tab of the Sort traces is showing as 1282 total number of sorted gathers then the user must provide these number in the parameters tab where Clear From and Clear To values.
Input data tab is disabled and all the input data information has to be provided at the Parameters tab.
Input file name - browse and select the .tmp file
ClearFrom - specify the starting sequence/gather/file to clear the information. It will clear all the information from the user specified location.
ClearTo - specify up to what sequence/gather/file information to clear the information.
Skip - By default, FALSE(Unchecked). This option helps to bypass the module from the workflow.
Header - generates the updated headers information.
NumCalc - displays the total number of calculated sequences/gathers/files
NumFaild - displays the total number of failed sequences/gathers/files
In this example workflow, we create a dataset inside Seismic loop. Later, we add band pass filter procedure to the same dataset. Prior to that, we clear certain CDPs using GService File Reader Procedure module and run the same workflow with band pass filter procedure. The output file name should remains the same. Create Stack and compare the difference between before and after the exercise.
In the 1st flow, we sorted the data in CDP-OFFSET domain and did a NMO correction inside the seismic loop. Output the data(gservice-file-reader-before.gsd.sgy).
In the 2nd flow, we read the NMO corrected gathers created from the 1st flow and created a stack section for initial QC.
In the 3rd flow, we took the NMO corrected gathers (.tmp file) and cleared CDP 200 - 400.
In the 4th flow, we've added Bandpass filter procedure and re-executed the workflow with same output name (gservice-file-reader-before.gsd.sgy) with DIRECT mode without overwriting option.
In the 5th & last flow, we've created stack and compared the previous stack and current stack. The user can see clearly observe a difference in both the displays.
Inside GServiceFileReaderProcedure, we read the .tmp file as shown below.
If we compare both of them next to each other, we can clearly see a difference. This way, the user can utilize this procedure to adjust the processing parameters for a particular region by clearing the area and re-execute them with different parameters etc.
There are no action items available for this module.
YouTube video lesson, click here to open [VIDEO IN PROCESS...]
Yilmaz. O., 1987, Seismic data processing: Society of Exploration Geophysicist
* * * If you have any questions, please send an e-mail to: support@geomage.com * * *
