OPH_MERGECUBES2¶

Description¶

Type

Data Process.

Behaviour

It merges the measures of n input datacubes with the same fragmentation structure and creates a new datacube with the union of the n measures. NOTE: only single measure data cubes can be merged and a new implicit dimension will be created.

Parameters

• cubes: name of the datacubes to merge. The names must be in PID format. Multiple-value field: list of cubes separated by “|” can be provided.
• schedule: scheduling algorithm. The only possible value is 0, for a static linear block distribution of resources.
• container: name of the container to be used to store the output cube; by default, it is the input container.
• dim: name of the new dimension to be created; by default a unique random name is chosen.
• dim_type: data type of the new dimension. Default value is “long”.
• number: number of replies of the first cube; by default the first cube is considered only once.
• description: additional description to be associated with the output cube.

System parameters

• exec_mode: operator execution mode. Possible values are async (default) for asynchronous mode, sync for synchronous mode with json-compliant output.
• ncores: number of parallel processes to be used (min. 1).
• sessionid: session identifier used server-side to manage sessions and jobs. Usually, users don’t need to use/modify it, except when it is necessary to create a new session or switch to another one.
• objkey_filter: filter on the output of the operator written to file (default=all => no filter, none => no output, mergecubes => shows operator’s output PID as text).

Examples

Merge the datacubes identified by the PIDs “URL/1/1” and “URL/1/2”:

[OPH_TERM] >>  oph_mergecubes2 cubes=URL/1/1|URL/1/2;

Arguments¶