analysis collate_contacts
Sets the tolerance value for track data and reference marker with respect to which contact data is computed.
Format:
analysis collate_contacts |
|---|
analyis_name = | existing analysis |
contact_name = | new contact |
tolerance = | real |
reference_marker = | existing marker |
Example:
analysis collate_contacts & |
|---|
analysis_name = | last_run & |
contact_name = | contact_between_part_1_and_2 & |
tolerance = | 0.1 & |
reference_marker = | marker_3 |
Description:
Parameter | Value Type | Description |
|---|
analysis_name | Existing analysis | Specifies an existing analysis. |
Contact_name | Existing contact | Specifies an existing contact. |
tolerance | Real | Specifies the distance used to decide if two successive impacts of two geometries used by the same contact belong to the same track. If you do not provide it, Adams Solver computes the tolerance, which can take a long time. |
reference_marker | Existing marker | Specifies the marker with respect to which the track data is computed. Otherwise, the track data is in the global reference frame. |
Extended Definition:
1. A track is a sequence of individual impacts between two particular geometries specified by a single contact object. The two geometries for a particular track should always be the same at every impact along that track.
It is possible for a contact object and two of its geometries to have more than one track. For example, if a contact and two of its geometries have more than one impact at the same time, each separate impact must belong to a separate track to remove ambiguity. Also, when the separation between impacts is great enough according to either an automatic or given criteria, the impacts may be assembled into separate tracks.
There is an experimental method of specifying a delta value for the separation criteria that will make the program skip the automatic criteria, sometimes saving a significant amount of time. This can be done by setting the tolerance parameter using the
analysis collate_contacts command. By using a large tolerance value, you can coerce tracks together that may have been separated by the automatic criteria. See
Knowledge Base Article KB8015944 for more information.
Automatic criteria for a contact and an I and J geometry:
■The geometric center (centroid) of all the impacts over the entire simulation is found in three frames: the global frame and the I and J part frames.
■The average distance of the impacts from the centroid is computed, again in each of the three frames.
■The standard deviation of the impacts from this average distance is computed in the three frames. This value for the standard deviation is used as a delta to decide if any two impacts are close enough to be considered to belong to the same track. The frame with the minimum distance is used for the comparison.
To force a pair of locations on two different parts to belong to separate tracks you can place a small separate piece of geometry at that particular point on each part. For example, instead of making a table out of a single piece of geometry and letting the algorithm try to find the separate legs as four separate tracks, placing a cap at the end of each leg will force separate tracks.
2. You can identify an entity, such as a marker or force, by typing its name or by picking it from the screen. If the entity is not visible on the screen, you must type the name. You may also find it convenient to type the name even if the element is displayed.
If an entity is available by default, you can identify it by entering its name only. If it is not, you must enter its full name. To identify a entity under a different part, you may need to enter the model and part names as well. For example, you can specify marker 'pivot' from model 'links', part 'lower_arm' by entering ".links.lower_arm.pivot".
If you type a "?", Adams View lists the entity available by default.
You must separate multiple entity names by commas. If the entity is visible in one of your views, you can identify it by picking it. You need not separate multiple element picks by commas.
Notes: | ■If you created a marker by reading an Adams Solver dataset or graphics file, the marker name is the letters MAR followed by the dataset marker ID number. For example, the name of MARKER/101 is MAR101. If you created the marker during preprocessing, you gave it a name at that time. ■You may have explicitly named an analysis when you created it by reading one or more Adams output files (graphics (.gra), request (.req), or results (.res)). By default, the name of the analysis is the root name of the Adams output files without the extension. If you created the analysis by reading an Adams graphics file, for example, the analysis name is the name of the graphics file without the .gra extension ■You need to be using the XML Results File (XRF) format in order for the contact incident data to be available for collation. |