建模理论

忧郁的石油

定义地质步骤参数包，
写一个类集成described arguments by reflection

创建一个property和field to save the input and output arguments.

譬如well log和pillar gird 是输入参数
property和cell count是输出参数



Petrel allows using variables in the workflow editor. Two types of variables can be
defined:

Object Variables refer to the objects in Petrel and are also called reference
variables.

These are predefined in Petrel and can be found under the Variables
folder of the Workflows pane.

Under Variable folder, there is a special variable
called "Output" when used;

it contains the result from the latest executed process
in the workflow.

For example, after a Volume calculation workstep, the Output
variable will hold the information about the name of the Volume run.

Variables are defined by a numerical value or a string. It is defined using a “$”
sign preceding it (for example $pi = 3.14).
Any variable must be defined in the workflow before it is used.
Refer to Petrel Help for details on the usage of workflow variables in Petrel.


Variables are defined by a numerical value or a string. It is defined using a “$”
sign preceding it (for example $pi = 3.14).
Any variable must be defined in the workflow before it is used.
Refer to Petrel Help for details on the usage of workflow variables in Petrel.


Processes may be purely interactive, purely algorithmic, or a combination of the two.

An interactive process might require the user to select data on the screen or manipulate
data in space, such as creating a point set from a series of mouse clicks.

An algorithmic process requires the user to enter some inputs and maybe outputs and then run a
computation, such as creating a borehole with a well trajectory from an existing point
set.


An algorithmic process requires the user to set up the inputs and outputs before it is
run. This means the UI typically has data entry fields, Petrel blue arrows, etc. Typically
the process would invoke a workstep to actually run the algorithmic step.


An interactive process has the user give input data by manually interacting with data in
a window (typically with mouse clicks). This means the UI does not take input; it just
explains how to run the process interactively


public class Arguments:DescribedArgumentsByReflection
{
//input arguments

public int numCells{get;set;}
private Welllog m_welllog;
public Welllog Mwelllog
{
get{return m_welllog;}
set{}

public class Arguments: DescribedArgumentsByReflection
{
//input parameters
private WellLog m_welllog
public WellLog InputWellLog
{
set {welllog=value;}
internal get{ return welllog; }
}

private Grid InputGrid
{
set{gird=value;}
internal get{return gird;}

private slb.ocean.petrel.domainobject.property prop
{
get{return prop;}
internal set{ prop=value; }

}
}
}

You need to tell the system what roles the arguments have: whether they are input
arguments, output arguments, or both. This is accomplished via the accessibility of the
property get and set.
For an input argument, the system will need to give the argument value from the UI.

The set is public to allow the system to load the argument value from the UI into the
argument package.

The get for an input argument does not need to be public
because the system does not need to use it, so you make it internal by convention.

The accessibility is reversed for an output parameter.

The set that you use to export
the results is internal;
the get used by the system to retrieve the argument values
from the workstep is public.



}



private Grid m_grid;

//output arguments
private Property m_outProp;

public




}



custom upscaling argument package

well log input， pillar grid input， pillar grid property output， property cell count output
argument package

describedargumentsbyrefelction

A line UI within the petrel workflow editor
a default table based dialog ui
interoperability with the petrel workflow editor automatic support for workflow variables in the line UI

joylin

钦佩会编程的人