User Method Registration
- StressToolMethodRegistration.xml
- StressToolAttributeRegistration.xml
The default location of these files is installdir\hwdesktop\hm\scripts\EngineeringSolutions\aerospace\StressTool\WorkingDirectory. You can copy these files into any working directory and point to StressToolMethodRegistration.xml.
Attribute Registration
Registered attributes are either model information queried from the HyperMesh database or result information queried from result files. Result data types must match names in the result file. Most of the time, the result reader provides aggregated vector or tensor data types. For better portability of method registration, it is recommended to use such aggregated data types instead of direct raw scalars that are subject to change depending on element formulation. For example, cbar versus cbush force, or depending on the file format used, even for the same solver (*.xdb and *.op2 have different spelling scalars). All result attribute paths (key “value=”) start with HMDb.Results. HMDb is the design point that will be queried. Whenever the design point is made of several elements, the framework will loop through the design point content.
- HMDb.property.PCOMP_MID.MAT8_Xt will query the ply’s material Xt allowable based on the order of precedence.
- HMDb.element.property.PCOMP_MID.MAT8_Xt will always use the local element’s property no matter which property is assigned (or not) to the structural property.
- HMDb.element.thickness will retrieve elemental thickness in a panel (metallic and composite).
- HMDb.structuralproperty.thickness enforces to use attribute thickness for Panel_metallic.
If an attribute can have multiple values on an element, certification will manage during the query loop layer per layer.
Method Registration
- name
- type
- category
- display name
- path
- InputArgList
- Define mapping between method inputs and attributes defined by the name in the AttributeRegistration file. The list of parameters must be ordered in the same way as method arguments.
- OutputArgList
- Methods can output multiple results. Variable number of outputs is not supported. You can give a display name for each method output. This name will become the header of the method table column.
Sorting
- The type of envelope is: Min| Max| AbsMin| AbsMax.
- The value can be any float parameter from InputArgList/OutputArgList. It is used as a comparison metric.
- Domain can be a cumulative list among keys: DDP |elementid |layerindex |loadcase.
- DP|elementid|layerindex: On each layer retains the critical metric across loadcases (LC).
- DDP|elementid: Retains one value per element which is a critical metric across layers and LC.
- DDP|elementid|loadcase: Retains one value per element per LC.
- DDP| loadcase: Performs spatial aggregation across elements (layers if applicable) per LC.
- DDP: Retains the critical metric across LC:
- If method was element/layer based there will be spatial aggregation.
- If method was a DDP level method (one value per DDP) it is an envelope.
- Whenever there are critical values across loadcases, contour is available only for envelope loadcases.
- Whenever results across layers are aggregated, contour is available only at the element level.
- Whenever an aggregation is done across elements (on a design point) the table will have the following: DDP|elementid|loadcase|..inputs|..outputs| metric, where metric uses critical values. As a result, only one element ID is kept per design point. The contour method feature has the ability to select ddpid as an entity, which contours a constant value on all elements inside the design point.
Aggregation
In addition to post evaluation sorting, attributes can be sorted before sending them to method for evaluation. This enables some flexibility in method evaluation. For example, you can declare the method input parameter as:
<Parameter name = "Composite Stress XX
perlayer="0"
sort=”min|max|minmax|sum|avg|absmin|absmax” (optional)
/>
- perlayer=”0|1”
- perelement=”0|1”
- perloadcase=”0|1”
You cannot mix these keys and only one of them can be “0” at a time. This means that you cannot aggregate the attribute both across layers and loadcases at the same time. This enables you to create a “designpoint method” level. For example, panel shear buckling considers the maximum shear stress XY among its elements. This value will be sent for math evaluation.
You can mix attribute aggregation and method sorting. In some cases, results might be more useful from tabular data exported to a report than contour, considering some of the limitations. The contouring tool has a filter for layer and loadcase and a selector for data type to plot. Only float data types are available for contouring. In the event of LC envelope (by sort) it is not possible directly to contour “critical subcase ID” on all elements (subcase is now a string). Information is available in the loadcase selector that contours only elements that have the critical value for this selected loadcase.