Online version Topic: 3.3 Input parameters
×
Menu
Index

3.3 Input parameters

 
The input parameters to the MigriX model are defined in the Properties/Input section in the Project Workspace tree. A table listing of all the input parameters to MigriX can be found in the Parameter overview section.   In Figure 3.8, we choose the Vsh parameter, and MigriX  therefore plots the Vsh values for all active layers in the model.
 
Figure 3.8: Operating on Vsh property for all layers (left) and on a single layer (right)
 
In order to modify Vsh for a single layer, we select this layer by clicking it in the workspace or in the 3D view. The border around the layer will then be marked with a thin yellow line. Then we select once more the Vsh input property and MigriX  shows the value for this layer. The value can be changed by simply changing the values in the text field. The changes will usually take effect immediately and be ready for use in a simulation run. The exception is the parameters related to the model geometry, such as depth grids, ages, fault traces as well as some lithology parameters.
 
When any of these parameters are changed, the Update Model icon in the Standard toolbar will change to a red colour (see Figure 3.9). In order for the updates to take effect, the user will then need to press the Update Model button. In most of these cases, MigriX will need to save the project before the update is ready.
 
Figure 3.9 Standard (project) toolbar. The Update Model button is the second from the left. The red colour indicate that some model parameters which requires a model update have been changed. Press this button to save the project and apply the updates.
 
Parameters that have been changed after the project was loaded will be shown in a bold font type, while parameters that have been changed earlier and differ from the default values are shown in italic font. If any of the parameters contain errors (e.g. invalid values or missing input files), the parameter will be shown with a red colour.
 
 
 
comments powered by Disqus