Lesson 12 Final
Lesson 12 Final
Objectives:
I Become familiar with MSC/NASTRAN error and warning messages arising from common modeling mistakes. I Import an Analysis Model into MSC/PATRAN via the MSC/NASTRAN Input File. I Use MSC/PATRAN to verify the validity of an existing MSC/NASTRAN model.
12-2
LESSON 12
Model Description:
The model used for this exercise is identical to the model used for Lesson 8. 0.5 psi Stiffener 5.0 (typ) 2.0 A a A 20.0 0.1 a b 0.1
20.0
Y
Z X
View A-A
b 1.0
Elastic Modulus: Poisson Ratio: Density: Plate Thickness: Bar cross sectional area: Iaa: Ibb: J:
10.3E6 psi 0.3 0.101 lbs/in3 0.1 in 0.38 in2 0.2293 in4 0.0168 in4 0.0013 in4
12-3
Exercise Procedure:
Imagine being hired by a major structural engineering rm. On your rst day, your manager gives you a legacy MSC/NASTRAN input le and all of one hour to submit the model for analysis and prepare a strength report which your manager plans to support his bid for a major contract. Sounds easy enough, right? Think again! It is enough of a challenge for you to generate a valid nite element model on your own, but to inherit a model of which you nothing about from someone you wouldnt know from Adam?? Well, it does happen.... And it is going to happen here... fortunately for you we are informing you that the model for this exercise is "broken". We took the solution MSC/NASTRAN input le from Lesson 8 and DELIBERATELY embedded common modeling errors encountered in industry. Your job is nd out what these errors are and resolve them. 1. 2. The MSC/NASTRAN input le you will be starting with is lesson12_work.bdf. Submit this le to the MSC/NASTRAN solver for analysis. To do this, nd an available xterm window and at the prompt enter:
nastran lesson12_work.bdf scr=yes Monitor the run using the UNIX ps command. 3. When the run is completed, edit the lesson12_work.f06 le and search for the words WARNING and FATAL.
Although WARNING messages are, for the most part, informative and will not interrupt an analysis, it is a good idea to review these messages just in case they may be an indication of a more serious problem. FATAL messages, on the other hand, indicates a denite problem with your system, input le format and/or the integrity of your model and will halt the analysis once encountered. These should be addressed as soon as possible. 4. The MSC/NASTRAN solver will nd all of the errors we embedded in the "broken" input le for this exercise. The CAVEAT is that it may not nd ALL of them during the same run!
LESSON 12
6.
File/New... New Database Name: OK In the New Model Preference form set the following: Tolerance: Analysis Code: Analysis Type: OK NDefault MSC/NASTRAN Structural lesson12
7.
Import your model via the <jobname>.bdf which spawned your most current <jobname>.f06 into MSC/PATRAN.
N Analysis Action: Object: Method: Select Input File... Filter Selected Input File: select the desired .bdf le
12-5
N Analysis Action: Object: Method: Select Results File... Filter Selected Results File: OK Apply When translation is completed and the Heartbeat turns green, bring up the Results form. N Results Action: Object: Create Quick Plot select the desired .op2 le Read Output2 Result Entities Translate
Choose the desired result case in the Select Result Cases list and select the result(s) in the Select Fringe Result list and/or in the Select Deformation Result list. And hit Apply to view the result(s) in the viewport. 9. Use the MSC/PATRAN model verication and postprocessing features to assess whether or not the model & results make sense (relative to the model & results for Lesson 8). If they do make sense, great job!. If not, you have a little more work to do before giving the results to you manager. If there are still problems with your model, resolve these problems in MSC/PATRAN. Once completed, generate a new input le using the the same preparation procedures used in Lesson 8.
10.
12-6
LESSON 12
NOTE: In a real-life situation, you would have veried the original input le in a pre-processor such as MSC/PATRAN before submitting the input le to the solver. Had we used MSC/PATRAN rst for this Lesson, we may have been spared a few iterations. But in the event that a pre/post-processor is not available at your site, the iteration process you underwent prior to verifying model & results in MSC/PATRAN is realistic.
12-7
Provided below is a log where you can document the problems you encounter during this Exercise.
WARNING/ FATAL Message Number
Item
Message
12-8