VELOCITY

I/O Options and Subcase Information Entry

VELOCITY - Output Request

Description

The VELOCITY command can be used in the I/O Options or Subcase Information sections to request velocity vector output for all subcases or individual subcases, respectively.

Format

VELOCITY(sorting,format,form,rotations,random,peakoutput,fourier,type) = option

Argument	Options	Description
sorting	<SORT1, SORT2> Default = blank	This argument only applies to the PUNCH format (.pch file) or the OUTPUT2 format (.op2 file) output for normal modes, frequency response, and transient subcases. It will be ignored without warning, if used elsewhere.
		SORT1:	Results for each frequency/ timestep are grouped together.
		SORT2:	Results for each grid/element are grouped together (Comment 7).
		blank:	For frequency response analysis, if grid SET is not specified, SORT1 is used, otherwise, SORT2 is used; for transient analysis, SORT2 is used.

format	<HM, H3D, OPTI, PUNCH, OP2, HG, PLOT, blank> Default = blank	HM:		Results are output in HyperMesh results format (.res file).
		H3D:		Results are output in Hyper3D format (.h3d file).
		OPTI:		Results are output in OptiStruct results format (.disp file).
		PUNCH:		Results are output in Nastran punch results format (.pch file).
		OP2:		Results are output in Nastran output2 format (.op2 file) (Comment 10).
		HG:		Results are output in HyperGraph presentation format (_freq.mvw file and _tran.mvw file) – see OUTPUT keywords HGFREQ and HGTRANS.
		PLOT:		Results are output in Nastran output2 format (.op2 file) when PARAM, POST is defined in the bulk data section. If PARAM, POST is not defined in the bulk data section, this format allows the form for complex results to be defined for XYPUNCH output without having other output.
		blank:		Results are output in all active formats for which the result is available.

form	<COMPLEX, REAL, IMAG, PHASE, BOTH> Default (HM only) = COMPLEX Default (all other formats) = REAL	COMPLEX (HM only), blank:		Provides a combined magnitude/phase form of complex output to the .res file for the HM output format.
		REAL or IMAG:		Provides rectangular format (real and imaginary) of complex output (Comment 8).
		PHASE:		Provides polar format (magnitude and phase) of complex output. Phase output is in degrees (Comment 8).
		BOTH (HM only):		Provides both polar and rectangular formats of complex output.

rotations	<ROTA, NOROTA> Default = NOROTA	ROTA:		Requests output of rotational velocity results (in addition to rotational velocity results).
		NOROTA:		Rotational velocity results are not output.

random	<PSDF, RMS> No default	PSDF:		Requests PSD and RMS results from random response analysis to be output. Only valid for the H3D format. The "RMS over Frequencies" output is at the end of the Random results.
		RMS:		Requests only the “RMS over Frequencies” result from random response analysis to be output. Valid only for the H3D format.

peakoutput	<PEAKOUT> Default = blank	If PEAKOUT is present, only the filtered frequencies from the PEAKOUT card will be considered for this output.

type	<NORMAL> Default = blank	NORMAL:		If present, the normal velocity results for grids on the surface of shell and solid elements are output (Comment 12).
		Blank:		Normal velocity results are not output.

FOURIER	<FOURIER> Default = Blank	FREQ:		If present, velocities in the frequency domain are output for Modal Transient Response Analysis with Fourier Transformation (Comment 13).
		TIME:		If present, velocities in the time domain are output for Modal Transient Response Analysis with Fourier Transformation (Comment 13).

option	<YES, ALL, NO, NONE, SID> Default = YES	YES, ALL, blank:		Velocity is output for all nodes.
		NO, NONE:		Velocity is not output.
		SID:		If a set ID is given, velocity is output only for nodes listed in that set.

Comments

1.	When the VELOCITY command is not present, velocity vector is not output.

2.	Velocity output is available for frequency response and transient analysis solution sequences.

3.	The form argument is only applicable for frequency response analysis. It is ignored for other analysis types.

4.	The forms BOTH and COMPLEX do not apply to the .frf output files.

Multiple formats are allowed on the same entry; these should be comma separated. If a format is not specified, this output control applies to all formats defined by the OUTPUT command, for which the result is available. See Results Output for information on which results are available in which formats.

6.	Multiple instances of this card are allowed; if instances are conflicting, the last instance dominates.

7.	For optimization, the frequency of output to a given format is controlled by the I/O option OUTPUT.

In general, HyperView does not recognize the SORT2 format for results from the .op2 file. When results are output only in SORT2 format (<Result Keyword> (SORT2, OUTPUT2, ….)), the results are written by OptiStruct into the .op2 file in SORT2 format, but when the .op2 file is imported into HyperView, the results in SORT2 format are not recognized. Therefore, the SORT1 option is recommended for results output in OUTPUT2 format and SORT2 option is recommended for results output in PUNCH format.

Results in binary format (.h3d or .op2) are always output in PHASE/MAG form, regardless of the options specified in the FORM field. The corresponding post-processors (HyperView/HyperGraph) can easily convert the PHASE/IMAG format to the required formats. Results in ASCII formats are output in the specified/requested FORM.

10.	The four-letter abbreviation VELO is interchangeable with VELOCITY.

11.	format=OUTPUT2 can also be used to request results to be output in the Nastran output2 format (.op2 file).

12.

For NORMAL velocity output, the surface grids are automatically selected from within the specified GRID SET. Alternately, if option=ALL is input, the normal velocity is output for all surface grids in the model. Normal results are only available for Frequency response analysis and in the H3D format.

13.	The FREQ and TIME options are only valid for modal transient analysis with Fourier transformation. When FREQ is present, the velocities in frequency domain would be output in a dummy frequency subcase, which shares the same ID with the transient subcase.