CHAPTER 3 - INPUT DEFINITION

Slides:



Advertisements
Similar presentations
Testing Relational Database
Advertisements

Chapter 3 – Web Design Tables & Page Layout
Chapter 8 Improving the User Interface
Tutorial 8: Developing an Excel Application
The Web Warrior Guide to Web Design Technologies
Chapter 9 Describing Process Specifications and Structured Decisions
1 / 31 CS 425/625 Software Engineering User Interface Design Based on Chapter 15 of the textbook [SE-6] Ian Sommerville, Software Engineering, 6 th Ed.,
The scanf Function The scanf function reads input from the standard input device into one or more variables Example: scanf(“%lf”, &miles); Reads a real.
Chapter 2 Basic Elements of Fortan
Modules, Hierarchy Charts, and Documentation
Asynchronous Solution Appendix Eleven. Training Manual Asynchronous Solution August 26, 2005 Inventory # A11-2 Chapter Overview In this chapter,
CHAPTER 6 FILE PROCESSING. 2 Introduction  The most convenient way to process involving large data sets is to store them into a file for later processing.
Copyright 2006 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Third Edition Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Chapter.
Chapter 3 Planning Your Solution
Data Structures and Programming.  John Edgar2.
Microsoft Office Word 2013 Expert Microsoft Office Word 2013 Expert Courseware # 3251 Lesson 4: Working with Forms.
Chapter Seven Advanced Shell Programming. 2 Lesson A Developing a Fully Featured Program.
XP New Perspectives on XML Tutorial 3 1 DTD Tutorial – Carey ISBN
Introduction to Systems Analysis and Design Trisha Cummings.
Internet Skills An Introduction to HTML Alan Noble Room 504 Tel: (44562 internal)
Database Applications – Microsoft Access Lesson 2 Modifying a Table and Creating a Form 45 slides in presentation Accessibility check 9/14.
Chapter 8: Systems analysis and design
IS 320 Notes for Chapter 8. ClassX Problems: Low-Tech Fix Use last year's videos on ClassX  Select "Semesters" tab  Select IS 320  Select the week/lecture.
Fortran 1- Basics Chapters 1-2 in your Fortran book.
Chapter 9 CAD & Parameters
OCAN College Access Program Data Submissions Vonetta Woods HEI Analyst, Ohio Board of Regents
Creating a Web Site to Gather Data and Conduct Research.
9 Chapter Nine Compiled Web Server Programs. 9 Chapter Objectives Learn about Common Gateway Interface (CGI) Create CGI programs that generate dynamic.
Introduction to SAS. What is SAS? SAS originally stood for “Statistical Analysis System”. SAS is a computer software system that provides all the tools.
Computational Methods of Scientific Programming Lecturers Thomas A Herring, Room A, Chris Hill, Room ,
The DATA DIVISION Chapter 3. COBOL Data Organization Field - group of characters forming a meaningful unit or basic fact –Characters in a name or digits.
3-1 Chapter 3. To familiarize you with  Ways in which data is organized in COBOL  Rules for forming data-names  Defining input and output files in.
3-1 The DATA DIVISION Chapter Chapter Objectives To familiarize you with Systems design considerations Ways in which data is organized Rules for.
 Whether using paper forms or forms on the web, forms are used for gathering information. User enter information into designated areas, or fields. Forms.
Chapter 5: Windows and Frames
Object-Oriented Program Development Using Java: A Class-Centered Approach, Enhanced Edition.
Structured Programming
C OMPUTING E SSENTIALS Timothy J. O’Leary Linda I. O’Leary Presentations by: Fred Bounds.
March 2004 At A Glance autoProducts is an automated flight dynamics product generation system. It provides a mission flight operations team with the capability.
Chapter 9: Advanced SQL and PL/SQL Guide to Oracle 10g.
1.  Introduction  The Benefits of the Report Writer Module ◦ For Detail and Summary Printing ◦ For Control Break Processing ◦ For Printing Headings.
8 Chapter Eight Server-side Scripts. 8 Chapter Objectives Create dynamic Web pages that retrieve and display database data using Active Server Pages Process.
NAS101, Appendex A, Page 1 DOCUMENTATION This section briefly describes the MSC.Nastran documentation. A quick overview of these documents is shown in.
COBOL for the 21 st Century Nancy Stern Hofstra University Robert A. Stern Nassau Community College James P. Ley University of Wisconsin-Stout (Emeritus)
Introduction Complex and large SW. SW crises Expensive HW. Custom SW. Batch execution Structured programming Product SW.
Operating System Discussion Section. The Basics of C Reference: Lecture note 2 and 3 notes.html.
Chapter – 8 Software Tools.
Page 1 Introduction to Lagrange Chapter 13 - RIGIDSMSC.Dytran Seminar Notes CHAPTER 13 - RIGIDS.
HEI/OCAN College Access Program Data Submissions.
Chapter 4: Variables, Constants, and Arithmetic Operators Introduction to Programming with C++ Fourth Edition.
System is a set of interacting or interdependent components forming an integrated whole.
Linear Buckling Analysis
Fundamentals of Programming I Overview of Programming
CSC201: Computer Programming
Structured Programming
Text by: Lambert and Osborne
Software Documentation
Other Kinds of Arrays Chapter 11
Chapter 7: Introduction to CLIPS
Programmable Logic Controllers (PLCs) An Overview.
Designing and Debugging Batch and Interactive COBOL Programs
Chapter 3 The DATA DIVISION.
Introduction to Systems Analysis and Design
An Introduction to Structured Program Design in COBOL
Structured COBOL Programming
Smart Integration Express
CHAPTER 17 The Report Writer Module
Chapter 11 Describing Process Specifications and Structured Decisions
The ultimate in data organization
Chapter 1: Programming Basics, Python History and Program Components
Presentation transcript:

CHAPTER 3 - INPUT DEFINITION

CONTENTS MSC.Dytran Documentation Data Input Format of the Input MSC.Nastran Style Input File Management Section, Executive Control and Case Control Format Bulk Data Format Bulk Data Input Format Differences from MSC.Nastran

MSC.Dytran USER’S MANUAL 1 – Online Documentation Available in pdf-format in MSC.Dytran Explorer 2 – Hardcopy Available in 2 volumes

MSC.Dytran User’s Manual Volume 1 Section 1 - Introduction Gives an overview of MSC.Dytran and its applicability, as well as a description of the explicit method of time integration and the Lagrange and Euler processors. Section 2 - Modeling Describes all the features of MSC.Dytran and what they can be used to model. The entry used to define the features is listed. Section 2 covers all of the capabilities of MSC/DYTRAN, both Lagrange and Euler. Section 3 - Running the Analysis The process of running the analysis is described from modeling to results post- processing. This section describes the commands necessary to run, restart and rezone the analysis and the files produced by MSC.Dytran. The use of user subroutines is also explained.

MSC.Dytran User’s Manual (Cont’d) Volume 2 Section 4 - Input Data This section is essentially a reference section. The format of each entry is described; the contents of each field, the type of data in it and the default values assumed if it is left blank. There are five main subsections: FMS Executive Control Case Control Bulk Data Parameter Values Section 5 - Diagnostic Messages Format of all the error and warning messages issued by MSC/DYTRAN. Section 6 - References

MSC.Dytran User’s Manual (Cont’d) Appendix A - Using XDYTRAN Describes how to use XDYTRAN, a UNIX based GUI to launch MSC.Dytran runs and to create customized executables. Appendix B - Using XDEXTR Describes how to XDEXTR, a UNIX based GUI that translates result s in the archive and time history files into various third party import file formats. Appendix C – MSC.Dytran and Parallel Processing Appendix D - Using ATB Describes how to use MSC.Dytran in conjunction with ATB (Articulated Total Body) for occupant modeling. Appendix E - Using MSC.Dytran with TNO/MADYMO Describes how to use MSC.Dytran in conjunction with TNO/MADYMO to solve problems involving the interactions of occupants with deformable components. Appendix F - Example Input Data Appendix G - Using USA Describes how to use the MSC.Dytran in conjunction with USA (Underwater Shock Analysis) code by DeRuntz et al.

DATA INPUT Input File MSC.Dytran is designed to run in batch mode. All the data required for a job is provided in an input file, either created using an editor, or more often, created by a modeling package or preprocessor. The input file is compatible with that for MSC.Nastran and consists of four main sections: FMS Executive Control Case Control Bulk Data The input file is the same regardless of the type of computer you are using. The file is in ASCII format, so it can be easily transferred between different computers. Job Control In order to run the batch job the computer requires some job control which is unique to the type of machine being used. The submission package used to submit the job will generate all the job control required to run the analysis and create the appropriate files. The Installation and Execution Guide describes how to MSC.Dytran can run on. In all cases no knowledge of the intricacies of the computer system being used is required.

INPUT FILE FORMAT Input File Structure ... File Management Section ... ... Executive Control ... CEND ... Case Control ... BEGIN BULK ... Bulk data entries ... ENDDATA

INPUT FILE FORMAT File Management Section (FMS) Controls file usage and type of analysis. Executive Control Sets resource limits. Case Control Selects the type of output required and how often it is produced (No results output is produced by default). Makes data selections from the Bulk Data section.Controls the termination criteria for the analysis. Bulk Data Contains all the data necessary to define the analysis model. This typically includes: Geometry Element Connectivity Element Properties Material Properties Constraints Loading Interaction Sets the parameters used to control the analysis.

ADVANTAGES OF MSC/NASTRAN STYLE INPUT Flexible Input Format This form of data input is very flexible: Free or Fixed format can be used Entries can be in any order with any numbering system Industry standard input Since MSC.Nastran is so widely used, its form of input is virtually an industry standard for finite element analysis. Many programs can read and write this form of data file. Compatible with most preprocessors Virtually all major preprocessing programs can write MSC.Nastran input files. This means that they can also write MSC.Dytran input files, due to the compatibility of the programs. One input file for all analyses Given a certain amount of forethought, the same model and input file can be used for all types of analysis, be they performed with MSC.Nastran or MSC.Dytran. MSC.Dytran will accept all valid MSC.Dytran data. If it is not required for an MSC.Dytran analysis, a warning message is issued and the data is ignored.

ADVANTAGES OF MSC.NASTRAN STYLE INPUT (continued) Minimize user training Engineers and analysts already familiar with MSC.Nastran will find learning to use MSC.Dytran fairly easy, since not only are the input files essentially the same, but the documentation is very similar as well. Time spent training is therefore minimized, and engineers who normally run MSC.Nastran will be able to use MSC.Dytran on an occasional basis.

FMS, EXECUTIVE CONTROL AND CASE CONTROL FORMAT Free Format The FMS, Executive Control and Case Control sections are in free format. That means that data items can appear anywhere on the line and are separated by commas or spaces. ENDTIME = 1.0E-3 SET 1 = 1, 2, 101, 102

FORMAT OF DATA ITEMS Data Types The description of the entry in the User’s Manual gives the type of data required. It can be of three types: • Integer • Real • Character The integer and real numbers are used for numeric data; character input is used to select options on a number of entries and should consist of an alphanumeric string of characters matching one of the options available. Variations of Real Number Input Real numbers can be entered in a variety of ways. The following are all exactly the same as far as MSC.Dytran is concerned: 7.0 7 0.7E1 0.7+1 .70+1 7.+0 70.-1 70.0E-01

BULK DATA FORMAT Three Formats There are 3 distinct styles of Bulk Data input which can be freely mixed within the input file: Free Format This is the one you should use most of the time. The various fields on the entry can appear anywhere on the line, the individual items being separated by commas. GRID,10, ,7.5,8.6,9.0, ,456 Free field format is denoted by the presence of a comma in the first ten columns. Small Field Fixed Format Each line is split into 10 fields of 8 columns each. The data for a particular field must be in the columns associated with that field, although it can appear anywhere within the field. This type of format is identified by the absence of a comma.

BULK DATA FORMAT Large Field Fixed Format The entry occupies two lines of the input file. The first and last fields on each line consist of 8 columns each. The intermediate columns have 16 columns each. This type of format is denoted by the presence of a * after the entry mnemonic in field 1A on the first line and an * in the first column of the second line. The continuation mnemonics in fields 10A and 1B must be identical apart from the first character. It is recommended that you make them the same. If all the fields on the second line are blank, then it may be omitted.

CONTINUATION LINES Definition An entry may take up more than one line of the data file. All lines after the first are called continuations. Examples Parent CHEXA,10,100,3,4,5,6,7,8,+CONT Continuation +CONT, 9, 10 Parent CHEXA,10,100,3,4,5,6,7,8,+ Continuation +, 9, 10

CONTINUATION LINES Input Rules Field 1 of the Continuation must be the same as Field 10 of the preceding Line The characters in field 1 of the continuation must be the same as those in field 10 of the preceding line, except the first character. It is recommended that the two fields are identical. The Continuation Line must start with a * for large fixed Format Continuation Lines must follow their Parent Each continuation line must directly follow the line which it is a continuation of. Note that this restriction does not apply in MSC.Nastran. Formats can be mixed There is no restriction to the format of the parent and its continuation lines. Free, small or large fixed format can be freely mixed. For example a small fixed format entry can have a free format continuation or a free format line may have a large fixed format continuation.

DIFFERENCES FROM MSC.Nastran Free format data fields can have more than 8 characters The fields on a free format entry can be up to 16 characters as long as the whole entry fits onto one line of the input file. Real numbers can be entered as integers It is not necessary to have a decimal point in fields containing real numbers. If fields 5 to 8 are blank on a large format entry, the continuation line can be omitted. If the continuation line is omitted, fields 5 to 8 will be blank and therefore set to the default values. Continuation mnemonics need not be unique The same continuation mnemonic can be used many times. Indeed the mnemonic is not really necessary and it is simplest to simply leave it blank. Continuation lines must follow their parent Since the continuation mnemonics need not be unique, the continuation line must directly follow its parent. If you use MSC.Nastran do not use this increased flexibility