defaults adams_output
The ADAMS_OUTPUT command is used to set parameters that control the organization and statement format of Adams datasets written by VIEW.
Format:
defaults adams_output |
|---|
statement_order = | statement_order |
arguments_per_line = | argument_count |
text_case = | text_case |
indent_spaces = | integer |
write_default_values = | on/off |
scientific_notation = | integer |
trailing_zeros = | on/off |
decimal_places = | integer |
zero_threshold = | real |
round_off = | on/off |
significant_figures = | integer |
active_only = | on/off |
export_all_graphics = | on/off |
Example:
Defaults adams_output & |
|---|
statement_order = | markers_with_parts & |
arguments_per_line = | single |
This statement specifies that in the dataset markers are written as a group after the part to which they belong. Graphics that belong to a single part are written after the markers for that part, and graphics that connect one or more parts are written after all the parts are written. Also only one argument will be written in one line as shown below.
PART/1 , QG = 0.5, 0, 0 , REULER = 0D, 90D, 0D , MASS = 1.2
MARKER/101 , PART = 1 , QP = -0.5, 0, 0
Description:
Parameter | Value Type | Description |
|---|
statement_order | Markers_with_parts, Markers_where_used, Submodels_and_AdamsId, Submodels_and_ObjName, As_found_in_file | This controls the organization of the statements within the dataset. |
arguments_per_line | Single/multiple | This controls how many arguments are written on each line of an Adams dataset statement. The default is a single argument per line. |
text_case | Upper/lower/mixed | This controls the case of the text written for the statement's keywords and parameters. |
indent_spaces | Integer | This controls the number of spaces after the comma in column one used to indent a continuation line of a statement. |
write_default_values | On/off | This controls whether or not arguments that have default values are written explicitly into the dataset. The default is that the arguments with default values are not written into the datset. |
scientific_notation | Integer | This controls the lower and upper powers of ten where the format for real numbers switches from a fixed point format to scientific notation. |
trailing_zeros | On/off | This controls whether or not trailing zeros are printed for real numbers. |
decimal_places | Integer | This controls how many places are written after the decimal point for real numbers. The default value is ten decimal places. |
zero_threshold | Real | This specifies the threshold value for numbers being written to an Adams data set. |
round_off | On/off | This turns the round off feature for real numbers on or off. The actual numbers of places retained during rounding off is controlled by the SIGNIFICANT_FIGURES argument. |
significant_figures | Integer | This controls how many significant figures of a real number are retained during round off when it is enabled by setting the value of the ROUND_OFF argument to ON. |
active_only | On/off | This controls the writing of inactive objects as comments.
Default value is off. |
export_all_graphics | On/off | On -Select Export All Graphics to write all the graphics into the dataset.
Off - If this option is not checked, only the dataset graphics that are supported by the solver (such as BOX) and those that are referenced by contacts, are included in the dataset. |
Extended Definition:
1. The default for statement order is AS_FOUND_IN_FILE, unless the model was originally created in view, in which case the default is MARKERS_WITH_PARTS. Note that the order of the arguments within a statement are written in a fixed order.
AS_FOUND_IN_FILE
The order of the statements in the original dataset is maintained when the model is written back to a dataset. Any new statements added to the original model are written after all the original statements, and both sections are labelled to indicate which statements came from the original dataset and which statements are new.
MARKERS_WITH_PARTS
Markers are written as a group after the part to which they belong. Graphics that belong to a single part are written after the markers for that part, and graphics that connect one or more parts are written after all the parts are written.
Statements of the same type, such as JOINTs, JPRIMs, BUSHINGs, and so on, are written as a group, in order of ascending Adams id number.
In general, statements are written before other statements that depend on them. For example, markers are written before the joints that use them, joints are written before any couplers that connect them, and so on.
MARKERS_WHERE_USED
Markers are written immediately after certain types of statements that depend on the existence of those markers. The types of statements for which this is done is as follows:
BEAM BUSHING FIELD SFORCE SPRINGDAMPER VFORCE VTORQUE GFORCE NFORCE JOINT JPRIM REQUEST MREQUEST CVCV PTCV
If a marker is not used by any of these statements, it is written after the part to which it belongs.
Graphics that belong to a single part are written after the markers for that part, and graphics that connect one or more parts are written after all the parts are written.
Statements of the same type, such as JOINTs, JPRIMs, BUSHINGs, etc., are written as a group, in order of ascending Adams id number.
In general, the order in which the different types of statements are written into the dataset is similar to the order used in View 1.0 and 6.0.
2. For the arguments_per_line parameter,there are 2 choices:
SINGLE
Write only one argument and its values for each line of the statement. An example of how this would look is as follows:
PART/1 , QG = 0.5, 0, 0 , REULER = 0D, 90D, 0D , MASS = 1.2
MARKER/101 , PART = 1 , QP = -0.5, 0, 0
MULTIPLE
Write as many arguments and their values that will fit within 80 columns for each line of the statement. An example of how this would look is as follows:
PART/1, QG = 0.5, 0, 0, REULER = 0D, 90D, 0D, MASS = 1.2
MARKER/101, PART = 1, QP = -0.5, 0, 0
3. The text_case parameter does not affect comments, function expressions, titles, or filenames that are used as values of arguments. The default is UPPER.
■UPPER Text for keywords and parameters in the dataset are written in upper case.
■ LOWER Text for keywords and parameters in the dataset are written in lower case.
■MIXED Text for keywords and parameters in the dataset are written in mixed case. The first character of each word is in upper case, and the remaining characters are in lower case.
The text case control will not affect certain types of string valued arguments. They following arguments will be written into the dataset the way they are stored in the database.
TIRE: TPF and RDF RESULTS: COMMENT MATRIX:
FILE and NAME MADATA: COMMENT STRING: STRING REQUEST:
TITLE, COMMENT, FUNCTION, and F1 to F8 MREQUEST: COMMENT UCON:
FUNCTION MOTION: FUNCTION FIELD: FUNCTION SFORCE:
FUNCTION GFORCE: FUNCTION VFORCE: FUNCTION VTORQUE:
FUNCTION VARIABLE: FUNCTION CURVE: FUNCTION DIFF:
FUNCTION GSE: FUNCTION SENSOR: FUNCTION
4. The allowed values for indent_spaces are between zero and four spaces. Five or more spaces would make the subsequent text on the line a comment. The default is one space.
The text for function expressions is not indented for continuation lines. It is assumed that the user will add any leading spaces that they wish for indentation. Any indentation added by the dataset writer would interfer with the the user's, often used to show nesting of IF functions. The argument list for a user function will be indented if it requires more than one line.
The values of an argument that has multiple string values separated by colons will be preceded by a comma and indented if it has to be placed on a continuation line. This applies to the PART/EXACT and COUPLER/TYPE arguments. The exception is the REQUEST/TITLE argument that doesn't allow imbedded blanks. This will be preceded by a comma, but not indented.
5. The default values are -4 and 5, meaning that any number less than or equal to 1.0E-04 or greater than or equal to 1.0E+05 will be written in scientific notation.
6. When enabled, all the digits after the decimal point will be printed, whether they are zero or not. When disabled, any zeros at the end of the fractional part of the number will be dropped, leaving the last digit as a non-zero digit.
7. If a number has an absolute value smaller than the zero threshold value, the it will be written out as zero. This value is independent of units.
Note: | The above is not applicable for values of an Adams Array. They will be written out as-is, irrespective of the zero threshold value. |
8. The default for significant_figures parameter is to use ten significant figures.
This number is distinct from the number of places actually printed for a real number, controlled by the DECIMAL_PLACES argument.
9. The values assigned to the parameters will remain in effect until reassigned or the end of program execution.