420 Posts in 208 Topics by 63 members
If this is your first visit, you will need to register before you can post. However, you can browse all messages below.
| Thread | Order: Newest | Oldest | Title | RSS Feed |
|
Common Offset planes
i have used GENSORT module to sort data in offset and cdp order but KPRET2D not wprk with this sort of data. you suggested in your reply use DSOR_OFF module to sort data on offset planes, my question is that is this sort work with KPRET2D module? please explain with example. thanks 7 years ago |
||
|
Common Offset planes
You can use the DSORT_OFF module to sort data into common offset planes. DSORT_OFF is a specially configured version of the DISCSORT module, and sorts into OFFSET planes with CDP as the secondary key. Once you have your data sorted in common offset planes, most migration modules should take the data in this order and migrate each offset plane separately. Just double check the parameters of the migration module you are using. For instance the FDMIG module has a USELASTTR parameter which lets... 7 years ago |
||
|
Common Offset planes
how we sort data in common offset planes. After sorting the data , what is the order of primary key and secondary key. how we migrate each offset plane separately. please share examples. thanks 7 years ago |
||
|
Common problems with running MPI processes
Another common issue is using the wrong MPI implementation. Claritas is built with MPICH2, and will require MPICH2 to run correctly. There are several other MPI2 implementations around, including OpenMPI, LAM-MPI, MVAPICH2, etc. While these will provide MPI commands like "mpicc" and "mpif90", they won't work correctly with Claritas, because Claritas compiles and links code at runtime and therefore needs to use the same libraries. Ubuntu has the correct MPICH2 packages in it's default reposit... 6 years ago |
||
|
Common problems with running MPI processes
A common problem often encountered when running MPI processes is that the .mpd.conf file does not have the correct permission set. This file should be located in your home directory and is setup by the user to contain the MPD_SECRETWORD. This file is interrogated by MPI processes for this MPD_SECRETWORD and if the file can't be accessed the MPI processes will fall over. The correct setting for the permissions of this file can be set using the following command in a terminal window - [b]chmod 60... 6 years ago |
||
|
Compare Stack 3D
How many crosslines are there in inline 3001? It looks to me to that the crossline range is 2188 - 2302? So 115 traces - this is the value you want to set the N_ENS parameter to. N_ENS = number of traces in the inline you have selected to display (3001) = 115. When you are displaying multiple stacks on indiviual panels in XVIEW the N_ENS parameter should be equal to number of traces read in for the stacks (or inlines in your case). In the flow where you use N_ENS =100 and overlap=0 I think what... 4 years ago |
||
|
Compare Stack 3D
The idea is not to display 100 traces from each stack, the idea is to display two same inlines but when N_ensem=100 and Overlab=0 the two inlines are not the same but when N_ensem=100 and Overlab=100 it looks similar but this have one trace moved as you can see in the presentation. I attached a presentation more descriptive of parameters and images. thanks 4 years ago |
||
|
Compare Stack 3D
Sorry, I got things a bit wrong. If you only want to display 100 traces from each stack then you will need to limit the stacks to 100 traces as you read them in - that is make use of the PKEYLIST parameter or add the required primary key list to the end of each line in a LISTFILE. When displaying mulitple panels of stacks in XVIEW the N_ENS parameter cannot be used to limit the number of traces to 100. In this case the N_ENS parameter should not be less than the number of traces read in for the... 4 years ago |
||
|
Compare Stack 3D
Keleigh, thanks for the reply. What you mention is what we try to do, we set the N_ENS parameter with the same amount of traces we want to display, but during the execution of the flow, XVIEW shows at the very beginning a warning saying that the OVERLAP is higher than the N_BLOCKS-1 and that is reduced to fit. But there is no N_BLOCKS option in XVIEW to check, at least in the latest version of the software. And then what we see is that there is an offset of exactly one trace between the two st... 4 years ago |
||
|
Compare Stack 3D
The N_ENS parameter in the XVIEW module defines the number of ensembles (eg shots or stacked CDPs) to display at a time. If you are doing a repeat panel then N_ENS must equal the number of ensembles (or stacked traces) per repeat loop. So if you want to display 100 traces from each of the stacks then N_ENS=100, as you already have. If you want to plot two separate stacks on separate panels for comparision try setting the OVERLAP parameter to zero. The OVERLAP parameter is only used to specify ho... 4 years ago |
||