15.11.2012 Views

Mechanical APDL Basic Analysis Guide - Ansys

Mechanical APDL Basic Analysis Guide - Ansys

Mechanical APDL Basic Analysis Guide - Ansys

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Command<br />

GUI Menu Paths<br />

Main Menu> Solution> Load Step Opts> Sol'n Control<br />

( : <strong>Basic</strong> Tab)<br />

Main Menu> Solution> Load Step Opts> Output<br />

Ctrls> DB/Results File<br />

Main Menu> Solution> Load Step Opts> Output<br />

Ctrls> DB/Results File<br />

Purpose<br />

and results file and how<br />

often it is written.<br />

OUTPR Main Menu> Preprocessor> Loads> Load Step Opts> Controls what is printed<br />

Output Ctrls> Solu Printout<br />

(written to the solution<br />

Main Menu> Solution> Load Step Opts> Output output file, Job-<br />

Ctrls> Solu Printout name.OUT) and how of-<br />

Main Menu> Solution> Load Step Opts> Output<br />

Ctrls> Solu Printout<br />

ten it is written.<br />

The example below illustrates using OUTRES and OUTPR:<br />

OUTRES,ALL,5 ! Writes all data every 5th substep<br />

OUTPR,NSOL,LAST ! Prints nodal solution for last substep only<br />

You can issue a series of OUTPR and OUTRES commands (up to 50 of them combined) to meticulously<br />

control the solution output, but be aware that the order in which they are issued is important. For example,<br />

the commands shown below will write all data to the database and results file every 10th substep and<br />

nodal solution data every fifth substep.<br />

OUTRES,ALL,10<br />

OUTRES,NSOL,5<br />

However, if you reverse the order of the commands (as shown below), the second command essentially<br />

overrides the first, resulting in all data being written every 10th substep and nothing every 5th substep.<br />

OUTRES,NSOL,5<br />

OUTRES,ALL,10<br />

As another example,<br />

OUTRES,NSOL,10<br />

OUTRES,NSOL,ALL,TIP<br />

writes the solution at all DOFs every 10th substep and the solution at the node component "TIP" every<br />

substep. Again, if you reverse these you will only obtain output at all DOF every 10th substep.<br />

Note<br />

The program default for writing out solution data for all elements depends on analysis type; see<br />

the description of OUTRES in the Command Reference. To restrict the solution data that is written<br />

out, use OUTRES to selectively suppress (FREQ = NONE) the writing of solution data, or first<br />

suppress the writing of all solution data (OUTRES,ALL,NONE) and then selectively turn on the<br />

writing of solution data with subsequent OUTRES commands.<br />

A third output control command, ERESX, allows you to review element integration point values in the<br />

postprocessor.<br />

Command(s): ERESX<br />

GUI: Main Menu> Preprocessor> Loads> Load Step Opts> Output Ctrls> Integration Pt<br />

Main Menu> Solution> Load Step Opts> Output Ctrls> Integration Pt<br />

Main Menu> Solution> Load Step Opts> Output Ctrls> Integration Pt<br />

Release 13.0 - © SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information<br />

of ANSYS, Inc. and its subsidiaries and affiliates.<br />

2.6.4. Setting Output Controls<br />

61

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!