Importing Results

PCL and Customization > Accessing the Patran Database > Importing Results

XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX''">XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX''">

Importing Results

Results may be imported and stored in the Patran database for post- processing. The steps necessary to add results to the database are:

• Drop indexing on results data stored in the database to more efficiently add new results data.

• Find existing loadcase(s) or create a new one(s).

• Create subcase(s) for the loadcase(s) to which the results will be associated

• Create global variables (if needed) for result subcases.

• Associate related global variables.

• Create result types for each type of result (displacement, von Mises stress, strain tensor, etc.).

• Associate related result types.

• Create element position descriptions for each element location for results.

• Create section position descriptions for each result section position.

• Create layer position descriptions for each layer within each section position.

• Add results to the database as nodal or element based scalar, vector or tensor data.

• Associate global variables to subcases (e.g., Time, Load Increment).

• Re-create indexing on results data stored in the database and create results summary table.

Drop Results Indexing

For efficiency reasons, the indexing on results data should be dropped prior to adding new results to the database. The following function will drop results indices from the current database.


db_drop_res_index	()


Output:
INTEGER	<Return Value>	This function returns a value of 0 when executed successfully and a non zero value to indicate a change in status or an error.

Notes:

The C name differs. It is DbFDropResIndex.

int DbFDropResIndex ()

If the indexing on results data is dropped prior to adding results data, these indices must be re-created after all new results data has been added. See the Re-create Results Indexing, 788.

Create/Find Loadcases

The first step in importing results is determining which load case to associate the results. If the user knows the name of the load case, he can determine whether it exists or not and, if it exists, its internal ID by using the db_get_load_case function described in Load Cases, 692. If the load case does not exist or, if for some other reason the user wants to create a new load to associate the results to, he can use the db_create_load_case function described in Load Cases (p. 692).

Create Result Subcases

To create a subcase for a set of results the following routine is used.


db_create_sub_case	( loadcase_id, sub_case_title, sub_case_id, result_case_id)


Description:
This function creates a sub and result case associated to a load case.
Input:
INTEGER	load_case_id	This value specifies the load case id value.
INTEGER	sub_case_title[31]	This value specifies the sub case title.
Output:
INTEGER	sub_case_id	This value returns the sub case id value.
INTEGER	result_case_id	This value returns the results case id value.
INTEGER	<Return Value>	This function returns a value of 0 when executed successfully and a non zero value to indicate a change in status or an error.

Notes:

The C name differs. It is DbFCreateSubCase.

int DbFCreateSubCase ( lcid,sctitle, scid, rcid )

int 	lcid

char 	*sctitle

int 	*scid

int 	*rcid

Create Global Variables

Global variables are associated with result cases (db_create_subcase) to hold global data pertaining to all results stored within a result case. The most common global variables are time for transient analyses, frequency for modal analyses or load increment for non-linear static analyses. These are examples of common usages of global variables. Any real, complex or imaginary scalar, vector or tensor value may be stored as a global variable. The routine to create a global variable is as follows:


Note:	For the current release, there is no means of determining the global variable type. Therefore, all global variables are assumed to be scalar values


dbt_create_global_variables	( num, rcid, label, numform, csys_type, cid, code, gvid, values )


Input:
INTEGER	num	ALWAYS assign num=1.
INTEGER	rcid	Existing result case ID.
STRING	label[]	Label for the global variable. This is used to match with other global variables assigned to other result cases.
INTEGER	numform	Integer code for the numeric form of the data where 1-Real, 2=Imaginary, 3-Complex Magnitude, 4=Complex Phase, 6=Complex Real, 7=Complex Angle.
INTEGER	csys_type(num)	An array of coordinate system types where: -1=Unknown, 0=Global, 1=Nodal, 2=Element, 3=User, 4=Material, 5=Ply, 6=On Edge, 7=On Curve, 8=Data Dependent.
INTEGER	cid(num)	Existing coordinate frame ID (csys_type=3).
STRING	code[]	A label descriptor for the analysis code name.
REAL	values(6)	An array of real values (only the first used at this time).
Output:
INTEGER	gvid	Database ID pointer to the global variable entity.
INTEGER	Return Value	This function returns a value of 0 when executed successfully and a non zero value to indicate a change in status or an error.

Notes:

The C name differs. It is DbFCreateGlobalVariables.

int DbFCreateGlobalVariables ( num, rcid, label, numform, csys_type, cid, code, gvid, values )

int 	num

int 	rcid

char 	*label

int 	*numform

int 	*csys_type [num]

int 	*cid [num]

char 	*code

int 	*gvid

float 	values [ ][6]

Associate Global Variables

If global variables contain complex or imaginary values, a pair of global variable entities must be created for each value (real/imaginary or magnitude/phase). Once the pair of variables is created they must be associated using the following routine.


dbt_assoc_global_variables	( <num>, <rcid>, <label>, <numform>, <csys_type>, <cid>, <code>, <gvid>, <values> )


Input:
INTEGER	<num>	Number of global variable pairs to associate.
INTEGER	<rcid>	Result case to which these variables belong.
INTEGER ARRAY
	<list1>	(num) global variable IDs to be associated with list2.
INTEGER ARRAY
	<list2>	(num) global variable IDs to be associated with list1.
Output:
INTEGER	<Return Value>	This function returns a value of 0 when executed successfully and a non zero value to indicate a change in status or an error.

Notes:

The C name differs. It is DbFAssocGlobalVariables.

int DbFAssocGlobalVariables ( num, rcid, list1, list2 )

int 	num

int 	rcid

int 	*list1

int 	*list2

Create Result Types

Result types are created for each type of result to be imported. Result types are not unique to each result case. The same result type ID may be used in many result cases. If results have both contain components with differing numerical forms (real, imaginary...) then multiple result types using the same labels must be created. The following routine is used to create result types.


dbt_create_res_types	( <num>, <pri_label>, <sec_label>, <datatype>, <numform>, <from_code>, <units>, <rtid> )


Input:
INTEGER	<num>	Number of global variable pairs to associate.
CHARACTER STRING
	<pri_label>	Primary label result descriptor.
CHARACTER STRING
	<sec_label>	Secondary label result descriptor.
INTEGER	<datatype>	Integer code for the result datatype where 0=Unknown, 1=Scalar, 2=Vector, 3=Tensor
INTEGER	<numform>	Integer code for the numeric form of the data where 1-Real, 2=Imaginary, 3-Complex Magnitude, 4=Complex Phase, 6=Complex Real, 7=Complex Angle.
CHARACTER STRING
	<from_code>	Analysis code from which results were derived.
INTEGER	<units>	Assign units=0. NOT USED.
Output:
INTEGER	<rtid>	Database ID pointer for the result type created.
INTEGER	<Return Value>	This function returns a value of 0 when executed successfully and a non zero value to indicate a change in status or an error.

Notes:

The C name differs. It is DbFCreateResTypes.

int DbFCreateResTypes ( num, pri_label, sec_label, datatype, numform, from_code, units, rtid )

int 	num

char 	*pri_label

char 	*sec_label

int 	*datatype

int 	*numform

char 	from_code [ ]

int 	*units

int 	*rtid

Associate Result Types

If result types contain complex or imaginary values, a pair of result type entities must be created for each value (real/imaginary or magnitude/phase). Once the pair of result types is created they must be associated using the following routine.


dbt_assoc_res_types	( <num>, <pri_label>, <sec_label>, <datatype>, <numform>, <from_code>, <units>, <rtid> )


Input:
INTEGER	<num>	Number of result type pairs to associate.
INTEGER ARRAY
	<list1>	(num) result type IDs to be associated with list2.
INTEGER ARRAY
	<list2>	(num) result type IDs to be associated with list1.
Output:
INTEGER	<Return Value>	This function returns a value of 0 when executed successfully and a non zero value to indicate a change in status or an error.

Notes:

The C name differs. It is DbFAssocResTypes.

int DbFAssocResTypes ( num, list1, list2 )

int 	num

int 	*list1

int 	*list2

Create Element Positions

Element position descriptions are required for element based results. A unique element position entity must be created for each position within an each element type where results are defined. The coordinates entered are used to locate the results at nodes, centroids or Gauss points in a generic way. The following routine is used to create element position entities.


dbt_create_elem_positions	( <num>, <ctype>, <coords>, <epid> )


Input:
INTEGER	<num>	Number of result type pairs to associate.
INTEGER	<ctype>	Flay specifying which coordinate system is used to express the postion within the element. 0 = unknown cordinate system. [0, 0, 0, 0]. 1 = parametic coordinate system standardly used for line elemnts, quadrilateral surface elements and hexahedral solid elements. [c1, 0, 0, 0], [c1, c2, 0, 0], or [c1, c2, c3, 0]. 2 = area coordinate system standardly used for triangular surface elements. [c1, c2, c3, 0]. 3 = volume coordinate system standardly used for tetrahedral and pentahedral solid elements. The difinition of this sytem differs depending upon the element type being referenced. For tetrahedral solid elements, the standard volume coordinate system is used. For pentahedral solid elements a hybrid between the area coordinate system and the parametric system is used. The first three values are area coordinates of the postion within the local XY plane of the element. The fourth value is the parametric value of Z. [c1, c2, c3, c4].
REAL ARRAY
	<coords>(4)	The coordinates of the position within the element in the coordinate system specified by <ctype>. Always an array of four values. Use zeroes for any array positions which have no meaning.
Output:
INTEGER	<epid>	The internal ID assigned to the newly created element position.
INTEGER	<Return Value>	This function returns a value of 0 when executed successfully and a non zero value to indicate a change in status or an error.

Notes:

None.

Some of the element position definitions used in the Patran MSC Nastran interface are given below as an illustration. Alternatively, the user can define all his element positions using the parametric coordinate system for all element types. For more details about element coordinate systems, refer to the Patran element library.


position	coord. type	c1	c2	c3	c4
Line element
center	1	0.5	0.0	0.0	0.0
node 1	1	0.0	0.0	0.0	0.0
node 2	1	1.0	0.0	0.0	0.0
Triangular Surface element
center	2	0.333	0.333	0.333	0.0
node 1	2	1.0	0.0	0.0	0.0
node 2	2	0.0	1.0	0.0	0.0
node 3	2	0.0	0.0	1.0	0.0
Quadrilateral Surface element
center	1	0.5	0.5	0.0	0.0
node 1	1	0.0	0.0	0.0	0.0
node 2	1	1.0	0.0	0.0	0.0
node 3	1	1.0	1.0	0.0	0.0
node 4	1	0.0	1.0	0.0	0.0
Tetrahedral Solid element
center	3	0.25	0.25	0.25	0.25
node 1	3	1.0	0.0	0.0	0.0
node 2	3	0.0	1.0	0.0	0.0
node 3	3	0.0	0.0	1.0	0.0
node 4	3	0.0	0.0	0.0	1.0
Pentahedral Solid element
center	3	0.333	0.333	0.333	0.5
node 1	3	1.0	0.0	0.0	0.0
node 2	3	0.0	1.0	0.0	0.0
node 3	3	0.0	0.0	1.0	0.0
node 4	3	1.0	0.0	0.0	1.0
node 5	3	0.0	1.0	0.0	1.0
node 6	3	0.0	0.0	1.0	1.0
Hexahedral Solid element
center	1	0.5	0.5	0.5	0.0
node 1	1	0.0	0.0	0.0	0.0
node 2	1	1.0	0.0	0.0	0.0
node 3	1	1.0	1.0	0.0	0.0
node 4	1	0.0	1.0	0.0	0.0
node 5	1	0.0	0.0	1.0	0.0
node 6	1	1.0	0.0	1.0	0.0
node 7	1	1.0	1.0	1.0	0.0
node 8	1	0.0	1.0	1.0	0.0


Note:	The C name differs. It is DbFCreateElemPositions.

int DbFCreateElemPositions ( num, ctype, coords, epid )

int 	num

int 	ctype

float 	coords [ ][4]

int 	*epid

Create Section Positions

At least one section position entity is needed for loading results. Multiple section positions may be created with unique labels to segregate multiple results of the same type defined at a give node or element position. If the results are not defined at multiple section positions, a section position with a blank label should be defined. The routine to create section positions is defined as follows:


dbt_create_sect_pos	( <num>, <label>, <ctype>, <coords>, <secid> )


Input:
INTEGER	<num>	ALWAYS assign num=1.
CHARACTER STRING
	<label>	Label for the section position which may be blank if the results are not section based.
INTEGER	<ctype>	NOT USED, assign ctype=0.
REAL ARRAY
	<coords>	NOT USED.
Output:
INTEGER	<secid>	Integer Database ID pointer to the section position entity created.
INTEGER	<Return Value>	This function returns a value of 0 when executed successfully and a non zero value to indicate a change in status or an error.

Notes:

The C name differs. It is DbFCreateSectPos.

int DbFCreateSectPos ( num, label, ctype, coords, secid )

int 	num

char 	*label

int 	*ctype

float 	coords [ ][2]

int 	*secid

Create Layers

At least one layer entity is needed for each section position. Multiple layers with unique composite layer IDs may be created for each section position.The routine to create layers is defined as follows:


dbt_create_layers	( <num>, <comp_id>, <secid>, <layerid> )


Input:
INTEGER	<num>	ALWAYS assign num=1.
INTEGER	<comp_id>	Composite layer ID. May be 0 if there is no layered data.
INTEGER	<secid>	Database ID of an existing section position entity to which this layer is assigned.
Output:
INTEGER	<layerid>	Integer Database ID pointer to the layer entity created.
INTEGER	<Return Value>	This function returns a value of 0 when executed successfully and a non zero value to indicate a change in status or an error.

Notes:

The C name differs. It is DbFCreateLayers .

int DbFCreateLayers ( num, comp_id, secid, layerid )

int 	num

int 	*comp_id

int 	*secid

int 	*layerid

Add Nodal Results

Nodal results are added using any of six routines. These routines will add scalar, vector or tensor results either by constant result type or by constant layer. These routines require an existing result case (db_create_subcase), an existing or set of existing result types (dbt_create_res_types), and an existing or set of existing layers (dbt_create_layers). The following routine is used to add a nodal scalar result for a set of nodes using a constant result type ID.


db_add_s_nod_res_by_type	( <num>, <rtid>, <rcid>, <layerids>, <nids>, <results> )


Input:
INTEGER	<num>	Number of nodes/results input.
INTEGER	<rtid>	Existing result type ID.
INTEGER	<rcid>	Existing result case ID.
INTEGER ARRAY
	<layerids>	(num) sized array of layer ID for the result at each node.
INTEGER ARRAY
	<nids>	(num) sized array of node IDs.
REAL ARRAY
	<results>	(num) sized array of scalar results at each node/layer.
Output:
INTEGER	<Return Value>	This function returns a value of 0 when executed successfully and a non zero value to indicate a change in status or an error.

Notes:

The C name differs. It is DbFAddSNodResByType.

int DbFAddSNodResByType ( num, rtid, rcid, layerids, nids, results )

int 	num

int 	rtid

int 	rcid

int 	*layerids

int 	*nids

float 	*results

The following routine is used to add a nodal scalar result for a set of nodes using a constant layer ID.


db_add_s_nod_res_by_pos	( <num>, <rtids>, <rcid>, <layerid>, <nids>, <results> )


Input:
INTEGER	<num>	Number of nodes/results input.
INTEGER ARRAY
	<rtids>	(num) sized array of existing result type IDs.
INTEGER	<rcid>	Existing result case ID.
INTEGER	<layerids>	Existing layer ID.
INTEGER ARRAY
	<nids>	(num) sized array of node IDs.
REAL ARRAY
	<results>	(num) sized array of scalar results at each node/result type.
Output:
INTEGER	<Return Value>	This function returns a value of 0 when executed successfully and a non zero value to indicate a change in status or an error.

Notes:

Not Callable from C.

The following routine is used to add a nodal vector result for a set of nodes using a constant result type ID.


db_add_v_nod_res_by_type	( <num>, <rtid>, <rcid>, <layerids>, <nids>, <csys_type>, <cid>, <results> )


Input:
INTEGER	<num>	Number of nodes/results input.
INTEGER	<rtid>	Existing result type ID.
INTEGER	<rcid>	Existing result case ID.
INTEGER ARRAY
	<layerids>	(num) sized array of layer ID for the result at each node.
INTEGER ARRAY
	<nids>	(num) sized array of node IDs.
INTEGER ARRAY
	<csys_type>	(num) sized array of coordinate system types where: -1=Unknown, 0=Global, 1=Nodal, 2=Element, 3=User, 4=Material, 5=Ply, 6=On Edge, 7=On Curve, 8=Data Dependent.
INTEGER ARRAY
	<cid>	(num) sized array of CIDs (csys_type=3).
REAL ARRAY
	<results>	(num,3) sized array of vector results at each node/layer.
Output:
INTEGER	<Return Value>	This function returns a value of 0 when executed successfully and a non zero value to indicate a change in status or an error.

Notes:

The C name differs. It is DbFAddVNodResByType.

int DbFAddVNodResByType ( num, rtid, rcid, layerids, nids, csys_type, cid, results )

int 	num

int 	rtid

int 	rcid

int 	*layerids

int 	*nids

int 	*csys_type

int 	*cid

float 	results [ ][3]

The following routine is used to add a nodal vector result for a set of nodes using a constant layer ID.


db_add_v_nod_res_by_pos	( <num>, <rtids>, <rcid>, <layerid>, <nids>, <csys_type>, <cid>, <results> )


Input:
INTEGER	<num>	Number of nodes/results input.
INTEGER ARRAY
	<rtids>	(num) sized array of existing result type IDs.
INTEGER	<rcid>	Existing result case ID.
INTEGER	<layerid>	Existing layer ID.
INTEGER ARRAY
	<nids>	(num) sized array of node IDs.
INTEGER ARRAY
	<csys_type>	(num) sized array of coordinate system types where -1=Unknown, 0=Global, 1=Nodal, 2=Element, 3=User, 4=Material, 5=Ply, 6=On Edge, 7=On Curve, 8=Data Dependent.
INTEGER ARRAY
	<cid>	(num) sized array of CIDs (csys_type=3).
REAL ARRAY
	<results>	(num,3) sized array of vector results at each node/result type.
Output:
INTEGER	<Return Value>	This function returns a value of 0 when executed successfully and a non zero value to indicate a change in status or an error.

Notes:

Not Callable from C.

The following routine is used to add a nodal tensor result for a set of nodes using a constant result type ID.


db_add_t_nod_res_by_type	( <num>, <rtid>, <rcid>, <layerids>, <nids>, <csys_type>, <cid>, <results> )


Input:
INTEGER	<num>	Number of nodes/results input.
INTEGER	<rtid>	Existing result type ID.
INTEGER	<rcid>	Existing result case ID.
INTEGER ARRAY
	<layerids>	(num) sized array of layer ID for the result at each node.
INTEGER ARRAY
	<nids>	(num) sized array of node IDs.
INTEGER ARRAY
	<csys_type>	(num) sized array of coordinate system types where: -1=Unknown, 0=Global, 1=Nodal, 2=Element, 3=User, 4=Material, 5=Ply, 6=On Edge, 7=On Curve, 8=Data Dependent.
INTEGER ARRAY
	<cid>	(num) sized array of CIDs (csys_type=3).
REAL ARRAY
	<results>	(num,6) sized array of tensor results at each node/layer.
Output:
INTEGER	<Return Value>	This function returns a value of 0 when executed successfully and a non zero value to indicate a change in status or an error.

Notes:

The C name differs. It is DbFAddTNodResByType.

int DbFAddTNodResByType ( num, rtid, rcid, layerids, nids, csys_type, cid, results )

int 	num

int 	rtid

int 	rcid

int 	*layerids

int 	*nids

int 	*csys_type

int 	*cid

float 	results [ ][6]

The following routine is used to add a nodal tensor result for a set of nodes using a constant layer ID.


db_add_t_nod_res_by_pos	( <num>, <rtids>, <rcid>, <layerid>, <nids>, <csys_type>, <cid>, <results> )


Input:
INTEGER	<num>	Number of nodes/results input.
INTEGER ARRAY
	<rtids>	(num) sized array of existing result type IDs.
INTEGER	<rcid>	Existing result case ID.
INTEGER	<layerid>	Existing layer ID.
INTEGER ARRAY
	<nids>	(num) sized array of node IDs.
INTEGER ARRAY
	<csys_type>	(num) sized array of coordinate system types where -1=Unknown, 0=Global, 1=Nodal, 2=Element, 3=User, 4=Material, 5=Ply, 6=On Edge, 7=On Curve, 8=Data Dependent.
INTEGER ARRAY
	<cid>	(num) sized array of CIDs (csys_type=3).
REAL ARRAY
	<results>	(num,6) sized array of tensor results at each node/result type.
Output:
INTEGER	<Return Value>	This function returns a value of 0 when executed successfully and a non zero value to indicate a change in status or an error.

Notes:

Not Callable from C.

Add Element Results

Element based results are added using any of six routines. These routines will add scalar, vector or tensor results either by constant result type or by constant layer. These routines require an existing result case (db_create_subcase), an existing or set of existing result types (dbt_create_res_types), an existing or set of existing element position entities for each result location within each element type (dbt_create_elem_positions), and an existing or set of existing layers (dbt_create_layers). The following routine is used to add an element scalar result for a set of elements using a constant result type ID.


db_add_s_elem_res_by_type	(<num>, <rtid>, <rcid>, <epids>, <layerids>, <elids>, <results> )


Input:
INTEGER	<num>	Number of elements/results input.
INTEGER	<rtid>	Existing result type ID.
INTEGER	<rcid>	Existing result case ID.
INTEGER ARRAY
	<epids>	(num) array of element position IDs for each element.
INTEGER ARRAY
	<layerids>	(num) sized array of layer ID for the result at each element position.
INTEGER ARRAY
	<elids>	(num) sized array of element IDs.
REAL ARRAY
	<results>	(num) sized array of scalar results at each element/layer position.
Output:
INTEGER	<Return Value>	This function returns a value of 0 when executed successfully and a non zero value to indicate a change in status or an error.

Notes:

The C name differs. It is DbFAddSElemResByType.

int DbFAddSElemResByType ( num, rtid, rcid, epids, layerids, elids, results )

int 	num

int 	rtid

int 	rcid

int 	*epids

int 	*layerids

int 	*elids

float 	*results

The following routine is used to add an element scalar result for a set of elements using a constant layer ID/element position ID.


db_add_s_elem_res_by_pos	( <num>, <rtids>, <rcid>, <epid>, <layerid>, <elid>, <results> )


Input:
INTEGER	<num>	Number of results for a given element input.
INTEGER ARRAY
	<rtids>(num)	Sized array of existing result type IDs.
INTEGER	<rcid>	The result case id to be associated with each of the values.
INTEGER	<epid>	Existing element position ID.
INTEGER	<layerid>	Existing layer ID.
INTEGER	<elid>	Existing element ID.
REAL ARRAY
	<results>(num)	Sized array of scalar results at each element per result type.
Output:
INTEGER	<Return Value>	This function returns a value of 0 when executed successfully and a non zero value to indicate a change in status or an error.

Notes:

Not Callable from C.

The following routine is used to add an element vector result for a set of elements using a constant result type ID.


db_add_v_elem_res_by_type	( <num>, <rtid>, <rcid>, <epids>, <layerids>, <elids>, <csys_type>, <cid>, <results> )


Input:
INTEGER	<num>	Number of elements/results input.
INTEGER	<rtid>	Existing result type ID.
INTEGER	<rcid>	Existing result case ID.
INTEGER ARRAY
	<epids>	(num) array of element position IDs for each element.
INTEGER ARRAY
	<layerids>	(num) sized array of layer ID for the result at each element.
INTEGER ARRAY
	<elids>	(num) sized array of element IDs.
INTEGER ARRAY
	<csys_type>	(num) sized array of coordinate system types where: -1=Unknown, 0=Global, 1=Nodal, 2=Element, 3=User, 4=Material, 5=Ply, 6=On Edge, 7=On Curve, 8=Data Dependent.
INTEGER ARRAY
	<cid>	(num) sized array of cids (csys_type=3).
REAL ARRAY
	<results>	(num,3) sized array of vector results at each element/layer position.
Output:
INTEGER	<Return Value>	This function returns a value of 0 when executed successfully and a non zero value to indicate a change in status or an error.

Notes:

The C name differs. It is DbFAddVElemResByType.

int DbFAddVElemResByType ( num, rtid, rcid, epids, layerids, elids, csys_type, cid, results )

int 	num

int 	rtid

int 	rcid

int 	*epids

int 	*layerids

int 	*elids

int 	*csys_type

int 	*cid

float 	results [ ][3]

The following routine is used to add an element vector result for a set of elements using a constant layer ID/element position ID.


db_add_v_elem_res_by_pos	( <num>, <rtids>, <rcid>, <epid>, <layerid>, <elids>, <csys_type>, <cid>, <results> )


Input:
INTEGER	<num>	Number of elements/results input.
INTEGER ARRAY
	<rtids>	(num) sized array of existing result type IDs.
INTEGER	<rcid>	Existing result case ID.
INTEGER	<epid>	Existing element position ID.
INTEGER	<layerids>	Existing layer ID.
INTEGER ARRAY
	<elids>	(num) sized array of element IDs.
INTEGER ARRAY
	<csys_type>	(num) sized array of coordinate system types where: -1=Unknown, 0=Global, 1=Nodal, 2=Element, 3=User, 4=Material, 5=Ply, 6=On Edge, 7=On Curve, 8=Data Dependent.
INTEGER ARRAY
	<cid>	(num) sized array of CIDs (csys_type=3).
REAL ARRAY
	<results>	(num,3) sized array of vector results at each element/result type.
Output:
INTEGER	<Return Value>	This function returns a value of 0 when executed successfully and a non zero value to indicate a change in status or an error.

Notes:

Not Callable from C.

The following routine is used to add an element tensor result for a set of elements using a constant result type ID.


db_add_t_elem_res_by_type	( <num>, <rtid>, <rcid>, <epids>, <layerids>, <elids>, <csys_type>, <cid>, <results> )


Input:
INTEGER	<num>	Number of elements/results input.
INTEGER	<rtid>	Existing result type ID.
INTEGER	<rcid>	Existing result case ID.
INTEGER ARRAY
	<epids>	(num) array of element position IDs for each element.
INTEGER ARRAY
	<layerids>	(num) sized array of layer ID for the result at each element.
INTEGER ARRAY
	<elids>	(num) sized array of element IDs.
INTEGER ARRAY
	<csys_type>	(num) sized array of coordinate system types where: -1=Unknown, 0=Global, 1=Nodal, 2=Element, 3=User, 4=Material, 5=Ply, 6=On Edge, 7=On Curve, 8=Data Dependent.
INTEGER ARRAY
	<cid>	(num) sized array of CIDs (csys_type=3).
REAL ARRAY
	<results>	(num,6) sized array of tensor results at each element/layer position.
Output:
INTEGER	<Return Value>	This function returns a value of 0 when executed successfully and a non zero value to indicate a change in status or an error.

Notes:

The C name differs. It is DbFAddTElemResByType.

int DbFAddTElemResByType ( num, rtid, rcid, epids, layerids, elids, csys_type, cid, results )

int 	num

int 	rtid

int 	rcid

int 	*epids

int 	*layerids

int 	*elids

int 	*csys_type

int 	*cid

float 	results [ ][6]

The following routine is used to add an element tensor result for a set of elements using a constant layer ID.


db_add_t_elem_res_by_pos	( <num>, <rtids>, <rcid>, <epid>, <layerid>, <elids>, <csys_type>, <cid>, <results> )


Input:
INTEGER	<num>	Number of elements/results input.
INTEGER ARRAY
	<rtids>	(num) sized array of existing result type IDs.
INTEGER	<rcid>	Existing result case ID.
INTEGER	<epid>	Existing element position ID.
INTEGER	<layerid>	Existing layer ID.
INTEGER ARRAY
	<elids>	(num) sized array of element IDs.
INTEGER ARRAY
	<csys_type>	(num) sized array of coordinate system types where: -1=Unknown, 0=Global, 1=Nodal, 2=Element, 3=User, 4=Material, 5=Ply, 6=On Edge, 7=On Curve, 8=Data Dependent.
INTEGER ARRAY
	<cid>	(num) sized array of CIDs (csys_type=3).
REAL ARRAY
	<results>	(num,6) sized array of tensor results at each element/result type.
Output:
INTEGER	<Return Value>	This function returns a value of 0 when executed successfully and a non zero value to indicate a change in status or an error.

Notes:

Not Callable from C.

Re-create Results Indexing

Once all the results have been added, the indexing on results data must be re-created. The following function performs this task. This function also creates a results summary table used within Patran. Even if the indexing on results was never dropped, this function should still be called so that the results summary table gets updated.


db_post_results_load	()


Output:
INTEGER	<Return Value>	This function returns a value of 0 when executed successfully and a non zero value to indicate a change in status or an error.

Notes:

The C name differs. It is DbFPostResultsLoad.

int DbFPostResultsLoad ()