|
|
|
|
DVcomb_mesh_and_data
Synopsis
combine a Mesh object and a Node_Data object into a field
module DVcomb_mesh_and_data {
Mesh+IPort2 &in_mesh ;
Node_Data+nres+IPort2 &in_nd;
Mesh+Node_Data+OPort2 &out => merge(in_nd, in_mesh);
};Description
DVcomb_mesh_and_data takes two inputs, any Mesh and Node_Data, and combines them together to form a new field.Many base module visualization objects input only the mesh of a field object (for example, DVmirror), and do not care if Node_Data is present or not. Other base module objects input only an object's Node_Data (for example, DVclamp), and do not care if a mesh is present. Yet one may presume that the user usually wants both the Mesh and Node_Data objects of his/her original field rejoined prior to further processing. The DVcomb_mesh_and _data base module object performs this rejoining.The actual effect of DVcomb_mesh_and_data is slightly more subtle. What actually happens is that references to the input Mesh and input Node_Data are merged. A reference object named out is defined that points to this merging. Graphically, the operation looks like the following figure (again using DVclamp as the example):Any object referencing the out port will receive a reference to the merged in_mesh and in_node. This will in turn reference the appropriate subobject of either Mesh or New Node_Data.The following table lists which base modules work only on the mesh or only on the Node_Data, and hence may require DVcomb_mesh_and_data:
Input
Output
Example
Libraries.Main.Filters.threshold Libraries.Main.Filters.clamp Libraries.Main.Mappers.scat_to_fld
File
See also
|
|
|
|