Indeed, we offer discounts to universities and the academia. Universities, as well as other educational and academic research institutes qualify for 50% discount from our regular license prices. This univesrsity discount does not imply any additional restrictions to the license - you will be able to use it for both teaching/research and for commercial projects.
Moreover, if you need the software to teach students, when you buy a regular license with the university discount, in addition we can offer you a complementary multi-user classroom license. (This complementary classroom license, however, will be restrictred to teaching only.)
[Note: the above conditions are valid for most parts of the world when you buy directly from us. However, in some territories for some software configurations this offer is not available. The conditions may also vary when you buy from our partners. Please, contact us with a detailed request for more information.]
When you buy a license directly from us, we will offer you a 3-day training of one person at our office in Moscow for free. Alternatively, you can always order a training course either at our office or at your location on a paying basis.
Please, note the dates of the training subject to availability of our trainers and their schedules. Any training shall be agreed and arranged at least a month in advance -- please, contact us as early as possible.
How can I move a RadExPro processing project to a new location, for example to a different computer?
Each RadExPro processing project occupies a separate folder on your hard disk. You can see the path to this folder when selecting the project in the Project Manager dialog list -- the path to the project directory will be displayed at the bottom of the dialog window. To move a project to a new location, simply copy the whole project folder there. Then launch RadExPro Plus and in the Project Manager dialog click the Select Project button to add the new project location to the list of registered projects.
There are two important notes. First, it is recommended that the raw data files are stored within the project folder (normally, inside the project folder we create a 'Data' sub-folder and put all original data files there). This would ensure that the original data will be copied to the new location together with the project. Second, make sure that the project files are not marked as 'read only'. (This can happen if you copy the project from a CD-ROM).- Indeed, a gather or trace ensemble is completely defined by sorting keys selected in Trace Inputroutine that enters data into processing flow. A gather consists of all traces with the same value of the primary sorting key specified. For example, if the sorting in the Trace Input routine is defined by 2 trace header fields as following:CDPOFFSETthen all traces with the same CDP number will be considered in the flow as members of one and the same ensemble so you will have CDP gathers. If the sorting is defined another way around, that is:OFFSETCDPthen an ensemble (gather) will be formed of traces with common offset, you will have common offset gathers.The relative order of the sorting keys affects how the traces will enter the flow. In the former examples, the traces will be sorted by CDP's and within each CDP-gather -- by offsets. In the latter example, the traces will be sorted by offsets, and within each common-offset gather -- by CDP number.You can use more than 2 sorting keys (in fact you can use for sorting as many trace header fields as you like) -- the idea will be the same.
- For reflection processing, the following trace headers must be correctly filled in:
TRACENO - sequential trace number within the file.
If the field is not filled, open your dataset in Geometry Spreadsheet, select the appropriate column and use Ins key to define the sequential numbering.
FFID - field record number (shot number).
CHAN - channel number.
These two values can be easily calculated from the trace sequential number and the number of channels. You need to evaluate correct formula and apply it through the Trace Header Math.
SOU_X - source coordinate.
REC_X - receiver coordinate.
If the acquisition scheme is regular, you can always define an expression to calculate these values from the shot number (FFID) and channel number (CHAN). As usual, the expression can be applied through the Trace Header Math.
OFFSET - distance between the source and the receiver = [SOU_X]-[REC_X] (or vice versa, just keep it always the same within a project).
AOFFSET = abs([OFFSET])
CDP_X - coordintate of the CMP(CDP) position = ([SOU_X] + [REC_X])/2
CDP - sequential number of the CMP, normally evaluated by rounding of the CDP_X coordinate to the desired bin size (which, traditionally is taken as half-distance between the neighbouring receivers).
SCDP - number of a super-gather (containing several CMP gathers) for velocity analysis. If the super-gathers are formed by the dedicated Super Gather routine (recommended), this header field will be filled-in automatically. Otherwise, in case you are going to make velocity analysis for each single CMP gather, use Trace Header Math to make SCDP = [CDP].
Of course, if the geometry is stored in SPS-files or other ASCII table files, you can import it into the data using dedicated tools of the Geometry Spreadsheet.
Besides, the data must always have correct values in DT (sampling interval, ms) and NUMSMP (samples per trace) header fields. In case, these headers are not filled, you shall fill them directly after the data is loaded into the project using Trace Header Math from the Geometry Spreadsheet menu, prior to execution of any processing flows. - You can do the following. Add a Trace Header Math routine into the flow and using this routine assigne some unused trace header field by either 1 or -1, depending on the channel number. This can be made with the help of cond function. For example, if we need to invert polarity of traces from channels 1 and 2, and we would like to use PICK1 header, we should type the following expression into Trace Header Math edit field:
pick1 = cond([chan]=1 | [chan]=2, -1, 1)
(see User Manual, Trace Header Math routine description for the details of cond usage).
Then we add to the flow a Trace Math routine (from the Trace Editing group). In its dialog we shall select the following parameters: Mode: Trace/Scalar, Operation: Multiply by scalar, and at the bottom of the diaog switch on Header option (i.e. each trace in the flow will be multiplied by scalar, that will be taken from a trace header field). In the edit field to the right we need to specify the header word where the scalar is to be taked from, in our example it is PICK1. Thus, as a result of the execution of this flow, each trace in the flow will be multiplied by either 1 or -1, depending on its channel number.
EN ĐÓ

