ECHO - Output Control ECHOON - Output Control ECHOOFF - Output Control
Description
The ECHO command can be used in the I/O Options section causing the output of the interpreted forms of subcase information and bulk data entries to the .out file.
The ECHOON command can be used in the I/O Options, Subcase Information, or Bulk Data sections causing the (verbatim) output of any subsequent I/O options, subcase information, or bulk data entries to the .out file until an ECHOOFF command is encountered.
The ECHOOFF command can be used in the I/O Options, Subcase Information, or Bulk Data sections suppressing the output of any subsequent I/O options, subcase information, or bulk data entries to the .out file until and ECHOON command is encountered.
Format ECHO = option1 ECHOON = option2 ECHOOFF Example ECHO = SORT(EIGR,EIGRL,ASET1,SPOINT,PARAM,SPC1,SPCADD,MPCADD, DLOAD,RLOAD2,DAREA,DPHASE,FREQ1,TABLED1,TABDMP1)
Argument Options Description
option1 <SHORT, PUNCH,
{cardname}, EXCEPT
{cardname}, blank>
<MAT, PROP, ELEM> Default = blank
SHORT: Only entries having less than 20 instances are echoed to the .out file.
PUNCH: Writes interpreted echo of all bulk data entries to the .echo file.
{cardname}: Only bulk data entries with the
given {cardname} are echoed to the .out file.
Argument Options Description
EXCEPT
{cardname}:
Only bulk data entries with the given {cardname} are not echoed.
blank: Writes interpreted forms of all subcase information and bulk data entries to the .out file. MAT, PROP,
ELEM:
Adds all cards of the specified class to the list for ECHO.
Option2 <PARSED> Default = blank
PARSED: Bulk data entries are converted to free format (comma
separated) before echoing.
blank: Bulk data entries are echoed
verbatim. Comments
1. When an ECHO command is not present, no input information is echoed.
2. The interpreted echo always includes SUBCASE cards (solution related), but not output control cards.
3. The cards are organized within groups, for example, optimization cards appear after model definition cards, and most cards are sorted by their numerical IDs.
4. The interpreted echo may contain some cards that are automatically generated or
converted during reading (for example, a CQUADR card shows as CQUAD4, or a CMASS1 card shows as a CMASS3 when only scalar points are referenced). Unreferenced cards may not show in the printout. PARAM,DOPTRM,OSDIAG will not be shown.
5. ECHO will be produced from internal representation of each card, thus it will be equivalent, but not identical to the input:
For most of the optional fields, the blank from input will be printed in ECHO as default value.
Fields which are not recognized or not used by OptiStruct are left blank. Some values which would generate warning on the input will be printed after adjustment.
6. The interpreted echo is always printed using a fixed field format (8 character fields) except GRID and DMIG cards, which are printed using free format (comma separated fields) with 10 decimal digits accuracy. Note that the use of IDs larger than 99,999,999 is allowed, but ECHO will not be usable in these cases as such IDs cannot be printed in fixed format.
DMIG c ards are usually very large and are not shown in the interpreted ec ho. Adding the card:
OSDIAG,167,1
anywhere in the control section will force full printout of DMIG cards if the interpreted echo is requested.
7. {cardname} contains the list of all cards which are to be included in the interpreted echo (or excluded, if EXCEPT keyword is present). This list may contain ELEM, MAT, or PROP keywords, which is equivalent to listing all valid element, material, or property names, respectively.
8. Multiple ECHO cards are allowed; all parameters of these cards are accumulated in the order in which they are input. EXCEPT may appear anywhere (for example, before or after {cardname} list) and may be repeated on multiple cards.
9. ECHOON / ECHOOFF cards may appear in any section of the input deck.
10. All comment cards, empty cards, and characters after the $ character on any card will not be printed in any ECHO format.
11. The .echo file generated when 'ECHO = PUNCH' is defined represents a copy of the input deck in a form suitable to use for another solution which, when used with the same Subcase Information and I/O Options entries, should generate identical results (round off error may be noticeable if the original input deck uses large field format). However, in some cases, the ECHO may require manual editing before being acceptable as input for OptiStruct. In particular, some optimization cards may be printed with information already modified internally, and they will be not correct. Also some cards with a negative ID may be printed in ECHO; those cards are automatically generated internally to OptiStruct, and should simply be deleted.
EDE
I/O Options and Subcase Information Entry EDE - Output Request
Description
The EDE command can be used in the I/O Options or Subcase Information sections to request element energy loss per cycle and element energy loss per cycle density output for all
subcases or individual subcases respectively. Format
EDE (format_list, type, dmig) = option
Argument Option Description
format <HM, H3D, PUNCH, OP2, PLOT, blank> Default = blank
HM: Results are output in HyperMesh
results format (.res file).
H3D: Results are output in Hyper3D format
(.h3d file).
PUNCH: Results are output in Nastran punch results format (.pch file).
OP2: Results are output in Nastran output2
format (.op2 file) (see comment 8). PLOT: Results are output in Nastran output2
format (.op2 file) when PARAM, POST is defined in the bulk data section.
blank: Results are output in all active formats for which the result is available.
type <AVERAGE, AMPLITUDE, PEAK> Default = AVERAGE see Comment 7
AVERAGE: In frequency response analysis average energy is output.
AMPLITUDE: In frequency response analysis the amplitude of energy is output. PEAK: In frequency response analysis the
peak energy is output. This is the sum of AVERAGE and AMPLITUDE.
Argument Option Description
dmig <DMIG, NODMIG> Default =
NODMIG
DMIG: Results are provided for external superelements in the .out file. NODMIG: Results are not provided for external
superelements in the .out file.
option <YES, ALL, NO, NONE, SID> Default = ALL
YES, ALL, blank:
Element damping energy and damping energy density are output for all elements.
NO, NONE: Element damping energy and damping energy density are not output.
SID: If a set ID is given, element damping energy and damping energy density are output only for elements listed in that set.
Comments
1. When an EDE command is not present, element damping energy and damping energy density is not output.
2. Initial thermal strain is included in the calculation of element energy loss per cycle and element energy loss per cycle density.
3. Multiple formats are allowed on the same entry; these should be comma separated. If no format is specified, then this output control applies to all formats defined by OUTPUT or FORMAT commands for which the result is available. See Results Output for information on which results are available in which formats.
4. Multiple instances of this card are allowed; if instances are conflicting, the last instance dominates.
5. For optimization, the frequency of output to a given format is controlled by the I/O option OUTPUT. In previous versions of OptiStruct, a combination of the I/O options FORMAT and RESULTS were used; this method is still supported, but not rec ommended as it does not allow different frequencies for different formats.
6. Type only applies to frequency response analysis.
7. There are three ways to calculate the Element Damping Energy in Frequency Response Analysis. They are listed as follows:
Type of Output Formula Average Amplitude Peak Where, E = Elemental Energy
{Ur } = Displac ement (Real Part)
{Ui } = Displac ement (Imaginary Part)
[Be ] = Elemental Damping
8. format=OUTPUT2 can also be used to request results to be output in the Nastran output2 format (.op2 file).