feap example manual
LINK 1 ENTER SITE >>> Download PDF
LINK 2 ENTER SITE >>> Download PDF
File Name:feap example manual.pdf
Size: 2636 KB
Type: PDF, ePub, eBook
Category: Book
Uploaded: 27 May 2019, 16:38 PM
Rating: 4.6/5 from 729 votes.
Status: AVAILABLE
Last checked: 9 Minutes ago!
In order to read or download feap example manual ebook, you need to create a FREE account.
eBook includes PDF, ePub and Kindle version
✔ Register a free 1 month Trial Account.
✔ Download as many books as you like (Personal use)
✔ Cancel the membership at any time if not satisfied.
✔ Join Over 80000 Happy Readers
feap example manualIn part these include:Source code of the fullConstitutive models include linear and finite elasticity, viscoelasticityR.L. Taylor and published by Elsevier, Oxford, 2013.This is a site to post questions, get answers, and interact with other users. We encourageIt is just in its beginning stage but already contains some useful information for new andPlease have a look and provide feedback and content.The elements given belowAn interface for FEAP is provided by the user solution command routineThe routine is fully operational with the 7.5 release of FEAP andOutput to file 'tang' nonzero terms in tangent. This permits FEAP to beThe interface is available from. David Bindel at the web site listed below.The routine given below providesGeneral information at:Compile andSubsequent commands 'tang' or 'utan' will then use SuperLU.General information and source may be obtained from:The interface may be obtained from:General information and licensing requirements may be obtained from:The FEAP interface may be obtained from:Google Pardiso for information on use. Also available with Intel compilers.Contains examples for user functions as well as a C interface forBindel. A MATLAB interface to FEAP which permits simultaneous access to both. For the use of these existing features the algorithm can be treated as a black box. When implementing new contact formulations the algorithm may be treated partially as a black box. New contact formulations can be added similar to the way continuum elements are added; hence, the user is not directly involved in the management of arrays for history variables or in modifying some crucial data (e.g., the column height vector for the global stiffness matrix). In the next paragraphs the basic input data organization is described. Moreover, the basic structure of the algorithm and the currently available features also are described.http://anadolumatbaa42.com/genelresimler/engrish-instruction-manual.xml
- Tags:
- feap example manual, feap example manual, feap example manual pdf, feap example manual for a, feap example manual transmission, feap example manual model.
Finally, information is provided for users who are interested in implementing new features or their own contact formulation. This manual is not intended to provide any detailed information about contact solution algorithms. However, it is assumed that the reader has some knowledge about how contact algorithms are solved using the finite element method. The data input for a contact interaction is provided after the initial mesh is defined. Accordingly, contact data must follow the END mesh command and any TIE mesh manipulation commands. The description of the contact algorithm is initiated by a CONTact command and is terminated by an END command. Contact input data is divided into three main categories: 1. SURFace definitions. The SURFace definition is purely a geometrical description of any surfaces which may be considered in any analysis involving contact between bodies. A surface is defined as a group of element facets. A facet may be any geometric shape which the contact formulation can consider. The MATEerial parameter definition defines the constitutive characteristics of a contact surface. For analyses in which there is no constitutive equation for the normal direction but frictional behavior for sliding, the pseudo material model is called standard and defined by a STANdard command. 3. PAIR definitions. The PAIR definition defines two surfaces which can interact, as well as, the associated material constitution(s) and details for the solution algorithm to be employed. FEAP uses the surface and material data sets to construct two independent control arrays which guide the overall solution process. As part of the control array construction, FEAP determines the total number of facets, number of material parameter sets, and the sets of pair data. A user need not specify the total number of pairs, facet or material sets (e.g., this is similar to FEAP’s ability to determine the total number of mesh nodes, elements, and element material sets in the problem).http://coracconstrucciones.com/dleyes/admin/fotos/engravestudio-manual.xml The pair data sets use the control array data sets to define and activate all contact elements which may then be assembled into the residual and tangent arrays during an analysis step. The use of the whole data structure is not mandatory. Consequently, a user may define contact surfaces or contact materials that are not used CHAPTER 1. INTRODUCTION 3 within an analysis. This provides a flexibility to rapidly modify the characteristics of contact interactions. Moreover each contact pair may be enabled or disabled by specifying a feature option, without removing any data. Finally, the treatment of the contact part of an analysis can be deactivated simply by setting a flag. This feature permits a very efficient check on other features of the analysis without altering any contact data. 1.1.1 Surface definition Each surface is defined as a group of facets. A facet is defined within the FEAP system by a sequence of global node numbers. For example, in a two-dimensional analysis involving surface interactions between solid elements modeled by three-node triangular finite elements (or four-node quadrilateral finite elements) a planar facet is defined by two nodes which are sequenced to traverse a boundary such that an outward normal points away from the body (i.e., the body lies to the left of the facet). This involves a counter clockwise traversing of the boundary curve. A user has the option to use the FACEt command and define each facet by a its global node numbers (generation options are provided as described later) or to define a surface segment (similar to the BLOCk or BLENd mesh commands) and let FEAP locate the facets which lie near the region defined by the surface segment. END of mesh CONTact SURFace 1. Define second surface 19 16 16 13 13 10 PAIR 1. For the PAIR command a penalty method is requested and its parameters are associated with the solution algorithm, not material characteristics.http://superbia.lgbt/flotaganis/1655355977 On the other hand, if a frictional contact is necessary, a frictional constitutive model must be defined. The structure of the algorithm consists of a basic skeleton which can be treated as a black box also from the programmers view point. This skeleton governs the whole data management and the data exchange within FEAP. The user can program and add new subroutines for data input of particular geometry, or automatic geometry data generation. In the same way routines to read data for a user specified material model can be added, as well as the implementation of completely new contact algorithms. Data input is organized by keywords. A dictionary of keywords is defined is defined by the programmer and, in the case of new algorithms, every new keyword should be recorded within the subprogram CONTINIT. 1.1.2 Restrictions on input data For the currently implemented input data forms there are some restrictions on use. These are: 1. A contact surface must be defined with facets all of the same type and number of nodes. 2. The surface element definition is strictly related to the continuum discretization. 3. A surface should pertain to only one region. 4. The same material properties are attributed to the entire surface or to the whole pair. They may be nonlinear or involve history type variables to model such phenomena as wear. CHAPTER 1. INTRODUCTION 1.2 6 Contact input commands All the contact commands should be placed immediately after the END of mesh data and any mesh manipulation data (i.e., TIE or LINK commands, and should be included within the contact start command CONTact and the end command END. Contact data are divided into three basic parts: (a) Definition of surfaces; (b) Definition of contact constitutive laws; and (c) Definition of contact pairs. There is complete independence of the data between the contact surfaces and the contact material sets. The coupling is carried out by a proper set of input data for the PAIR command. Notice that there is no need to duplicate the blank record which closes the last subcommand of a command. All the commands have a fixed input structure, which identifies the associated data set (i.e., Surface 100 Comment; Material 1 Comment; Pair 11 Comment). It is not necessary to adopt a progressive numbering of surfaces, materials or pair sets, numbering does not affect memory allocation, which is based only on the number of commands input. This implies that one can define a problem with two contact surfaces whose numbers are 100 and 500, and then define a contact pair with number 123 that uses these surface numbers. Internally, FEAP will define a sequential numbering and assign tag number 100 to the first set and tag number 500 to the second (assuming they are input in this order). The CONT main command has an option string and two numeric data values which are not used for normal purposes, but are very useful in debugging. The command CONTact OFF causes all contact data to be skipped. This option is useful for a preliminary checks on mesh data without contact. Special debug routines perform output of various arrays and each contact routine write its name on a file each time they are called. The two related numbers define respectively the file unit for list of call outputs and for array outputs, respectively. Default unit numbers are 99 and 98. Use of CONTact ON 1 Another option is to place a.Command data sets should terminate with a blank record. Each command can contain one or more additional data records. In particular, the type declaration of the MATE command permits one to define the subprogram to read material data, and the type declaration of the pair command permits one to describe the corresponding contact element. A type declaration does not have a second string description and accepts a maximum of 15 numerical input values. Each specified string description is converted in a numerical value which corresponds to the position within the control array. The values of all numerical parameters input are stored in the type column of the command control table (see section on control tables below). A type declaration can be followed by additional CHAPTER 1. INTRODUCTION 10 data records. This data is input by user subroutines, hence the format may vary in each instance depending on how much is input; however a standard format consisting in two strings and up to 14 numerical data is strongly recommended. Such data are stored in suitably allocated arrays, e.g., the material vector. This is the case for the material data record FRIC COUL 0.15 in the previous example where the value of the friction coefficient must be stored as a material parameter (i.e., there are 50 values possible for each material set in the CM array). A feature record contain information that characterizes basic choices in more detail than a type declaration. A feature data permits one to specify certain options available within the same contact element, e.g., the solution method using penalty or Lagrangian multipliers. Also in this case a numerical translation of the feature and option string is performed, and the data stored in a feature column of the command control table (see section on control tables). The number of the column correspond to the number of the feature within the control table (These are set by the order given in the subprogram CONTINIT). Finally a sub-command declaration can be used to input and store data in the same way that the type declaration does. Subcommand data is terminated by a blank record. FACEt is a subcommand which has no options and no numeric variables on the same records. It causes input of the subsequent data records (i.e., nodal connections for each element). BLOCk and BLENd are a sub-commands which generate automatically nodal connections along an edge whose characteristics are declared in subsequent data records. Sub-command dependent data records are read in user subroutines hence the input format has no restrictions; however, in this case also we strongly suggest to keep the feature data structure, i.e., two string data items and up to 14 numeric data items. A programmer has the possibility to list in the database new type declarations, new features and feature options, new sub-command and sub-commands options. CHAPTER 1. INTRODUCTION 11 A programmer also has also the possibility to add routines to input type declaration and sub-command data. Basic modifications proceed by making appropriate modifications to the subprogram CONTINIT. However the current capability to input surface geometry can manage with most practical cases. Note that the availability of the input routines for the various geometries does not imply the existence of any contact driver to solve a problem (In particular no use of the beam type is available). These options are simply provided to the user to input data in a standard manner and to build the control arrays. We emphasize again that construction of control tables does not imply one will use it. All the input commands simply generate and arrange the data in a suitable way for developing the compute CHAPTER 1. INTRODUCTION Option 1 Number SURF 1 LINE 2 TRIA 3 QUAD 4 BEAM 5 POIN 6 RIGI 12 Commands 2 3 MATE PAIR2 STAN NTOS NLFR PTOP USER NTON PTOR NTOR TIED CEL1 to CE20 Table 1.1: COMMAND Options capability. The possibility to solve a specific problem is checked by verifying what the available contact drivers (i.e., the subprograms CELMT01 to CELMT20) can do. No features are actually listed for the SURF command, instead it has the above cited sub-commands (i.e., FACE BLOC and BLEN), as well as, any additional ones listed in the FEAP user manual. Table 1.2 summarizes the available subcommand options for each of the surface input sub-commands. Subcommands Option 1 2 3 4 5 Number FACE BLOC BLEN REGI FUNC 1 GAP GAP CYLI 2 SEGM SEGM SPHE 3 POLA EXTE CART 4 CART PLAN 5 REGI POLY Table 1.2: Surface SUB-COMMANDS Options The FACE subcommand performs input of data as the standard ELEM command in mesh; however, there is no material or region associated for the contact case. If an increment different from zero is specified automatic generation of the missing CHAPTER 1. INTRODUCTION 13 elements between the current and the next one is performed. Such generation is based on the node number of the first element and on the specified increment. Node numbers of the next element are not involved. MATErial descriptions The MATErial command is used to input contact surface material characteristics. It should be recalled that for simple contact without friction the satisfaction of the nonpenetration conditions can be performed without any material command defined. In this case contact is treated as a purely geometrical constraint (frictionless contact). In case of frictional contacts the material friction coefficient must be specified as a material parameter. We note that in the case of a penalty method one more parameter is necessary, (i.e., the penalty value). Due to the fact that this is not a material value, but a solution strategy value, it is specified as parameter in the a feature record of the PAIR command. The MATE commands should be followed by the TYPE record. Material data are specified in following feature-dependent data records. For the material currently available only a Coulomb friction model is available. FRIC,COUL, friction coefficient 2. NLFR - Nonlinear friction model. 3. USER - User specified model. It should be noted that the choice to place the input for the friction coefficient on a separate record, declaring the friction model COUL, will permit one to easily add different friction models later. PAIR descriptions The PAIR command collects information from the SURF and MATE data to complete the data for each contact problem. Moreover some features that pertain to the solution strategy to be employed are specified. All options have a default value, except the solution method (SOLM), which requires specification of the method and any values needed (e.g., PENA and the value of the penalty parameters). It is the programmers responsibility to develop specific contact drivers which use specific combinations of the above features. CHAPTER 1. INTRODUCTION Option 1 2 3 Number SWIT SOLM DETA 1 OFF PENA BASI 2 ON LAGM SEMI 3 TIMF CROC RIGI 4 CONS 5 SHAK 6 RATT 15 Features 4 5 6 7 MATE AUGM TOLE ADHE OFF NONE INFI BASI PENE STRE HSET OPEN LISE OUTS SMAU Table 1.3: Contact pair FEATURE options Other command descriptions All other commands READ, SAVE, END are executed by calling existing subroutine of the MESH section, hence they are properly described in the FEAP Manual. 1.3 Description of subprogram structure The contact algorithm structure is modular. The FEAP system connections to data are limited only to a contact switch(CSW). All the connections are performed by calling the same routine with a proper value of the switch. The main routine then performs a set of calls to a contact driver routine or to other FEAP subprograms in order to satisfy the input request. In case of data exchange with the rest of the program the contact driver routine retrieves the necessary arrays. There is no direct data exchange through the parameters of the call. Some data is exchanged by accessing FEAP common blocks. The main contact driver routine is called each time the element library is called. For a solution step there are two calls: (a) One just before the finite element array (residual and tangent) computations; and (b) the second just after. Allocate memory for the material data vector (CM). Allocate memory for the nodal connections data (ICS). At this stage the number of nodes to be stored is not known. (f) PCONT Main driver routine of the input phase. All the input commands are filtered here. (g) PALLOC Extend memory area for nodal connection vector, allocate memory for the history variable management correspondence array (HIC). (h) DEFAULTP Set default of all non explicitly declared options for the contact pair. (i) CONTLIB Switch to the requested contact element to perform the initialization phase. (j) STOHMAN Store history management correspondence vector. (k) PALLOC Allocate memory for the contact history variables (vector CH). This vector is then fragmented in three vectors, CH1, CH2, CH3, which correspond to the continuum element vectors H1, H2 and H3, respectively. The listed subroutines call the following second, third and fourth level routines: The following call structure is the simplest one, because it requires a direct call to the contact driver with the appropriate contact switch value.We are a non-profit group that run this service to share documents. We need your help to maintenance and improve this website. MATFEAP's capabilities. The Iblock2 input deck in the example subdirectory describes a square mesh with n elements on a side, where the parameter n is not defined in the input deck. In this manual we provide some examples of problems which can be set up and solved using the FEAP program. We begin by describing some of the methods which may be used to define an input data file for some simple finite element analyses. The manual is organized to start with very basic methods for inputs and Ab der Version 2005 sind im Manual Hyperlinks eingefuhrt. To illustrate the form of an input file for FEAP we consider the simple king-post truss shown in Fig. 1.1. For simplicity we shall Manuals and free instruction guides. Find the user manual. FEAP - - A Finite Element Analysis Program. Version 8.5 Programmer Manual. Robert L. Taylor. 88. 7 Adding a user solver. 89. A Example: 2-Node Truss Element. 91. B Compiling in C. In this part of the FEAP manual some of the options to extend the capabilities of the program are described. We begin by describing User elements may be added to the FEAP system to extend solution capabilities (See FEAP Programmer Manual). The elements given below are examples of elements which are useful in educational applications to demonstrate the behavior of finite element solutions of classical applications. Version 8.4 Programmer Manual. Robert L. Taylor. Department of Civil and Environmental Engineering. University of California at Berkeley. Berkeley, California 94720-1710. Revised June 2014. ContentsElements with Finite Rotation Parameters......Energy Computation. A Non-linear Theory for a Truss............Sample. Sample. UMESHn module. UMESH module. UMATI1 module. UMATLn module. UMANLn module. UMACRn module. UPLOTn moduleFEAP Element Subprogram. Part 2. FEAP Element Common Blocks. FEAP Element Common Blocks using Includes.Element residual for two node truss. Truss Tangent Matrix. Part 1. Truss Tangent Matrix. Part 2. Element variable projection routine.......Triangular surface type elements in FEAP library. Quadrilateral surface type elements in FEAP library. Tetrahedron solid type elements in FEAP library. Brick solid type elements in FEAP library......List of TablesSolution Array Names, Numbers and Sized. Element Array Names, Numbers and Sizes. Element connection array IX use for element e. Element control array IE use for material number ma..........Task Options for FEAP Element Subprogram.Quadrature for tetrahedra. Color pallet for FEAP plots. Values for control of plots.We begin by describing the utilities provided in FEAP forThe size of problems which may be solved by FEAP depends on the amount of memoryMemory for the mainFurther information on use of these routines isThe IPR parameter in the feap84.f module controls the specification of the ratio of. REAL to INTEGER variables. For typical UNIX and PC systems all real variables shouldNormally FEAP reads each input data line as text data and checks each character forFor very large data sets thisIf all dataIt is also possible to use the PARSe and NOPArseIn Windows versions it is sometimes desirable to obtain the input file name from aDuring the input of plot commands FEAP has the option to either set input optionsSetting DEFALT to true indicates that all default optionsIf DEFALT is set false, a prompt for contour intervals mayFEAP has options to produce encapsulated PostScript output files in either gray scalePSREVS. Setting PSCOLR true indicates the PostScript files will be in color (unless setThe PSREVS variable reverses the colorThe last parameter which may be set in the feap84.f module is the level for displayingThat is, setting:It is possible to raiseWhen developing program modules it is often desirable to have output of specificThis device supplements use of available debuggers on the computer.FEAP contains many COMMON statements that are used to pass parameters and smallUsers may either place the commonIn FEAP all include files have the same name as the commonAll include files are located in the directoriesIt is highly recommended that users use include files rather than giving equivalentIf later releases of the FEAP program revise contents inAlso, by defining the correct path inChapter 2The subroutines PINPUT and TINPUT are input subprograms used by FEAP to inputThese routines also should be used to input data inThe PINPUT routine returns data to the callingThe following statements may be included asThe parameters defined in the include file (common block) are:If an error occurs during input from the keyboard FEAP returns a value of true for theFor inputs from a file, the program will stop and an error message indicating the typeIf any td(i) is to be used as an. That is, the followingPINPUT may be used to input up to 16 individual expressions on one input recordThe routine TINPUT differs from PINPUT by permitting text data to also be input. It is useful for writing user commands or to input data described by character arrays. The routine is used asThe parameter nt specifies the number of text values to input and the nn specifies theThe value for parameter nt or nn may be zero. Thus the use ofThe text stringTwo subprograms exist to output arrays of integer and real (double precision) data. The routine MPRINT is used to output real data and is accessed by the statement:For example the statements:The MPRINT routine adds row and column labels as well as the character label. The routine IPRINT is used to output integer data and is accessed by the statement:Chapter 3The pointers in the integer8Size of problems is limited only by the availableFor example use ofTo avoid thisA type of correct length isThe basic use of the routines is provided by anUpon initial assignment of any array its valuesIf the array is to be reused or resized (seeEach routine which makes directAs an example for the use of the above allocation scheme consider a case where it isA short list of the mesh arrays available in FEAP is given in Table 3.1, for solutionThe array IX(nen1,numel) is used to store basic information for each element in theIn addition,Table 3.1: Mesh Array Names, Numbers and SizesCMASn. JPnTANGnUTANnConsistent Mass. Damping. Profile pointer. Lump Mass. Symmetric tangent. Unsymmetric tangent. Table 3.2: Solution Array Names, Numbers and SizedTables 3.4, 3.5 and 3.6 describe the use of individual entries in the arrays IX, IE, and. IEDOF, respectively. The subprograms PALLOC and UALLOC may also be used to destroy a previously definedA call to PALLOC or UALLOC for any previously defined array but with a different nonzero length causes the size of the array to be either increased or decreased.Angle. Assembly nos. Element vector. Element matrix. Temperature. Solution array. Coordinates. Table 3.3: Element Array Names, Numbers and SizesIX(nen,e). IX(nen1,e). IX(nen1-1,e). Description. Global node 1Global node nen. H1 history data pointer. H2 history data pointer. H3 history data pointer. Lagrange multiplier tag. Lagrange multiplier data pointer. Element material type number. Inactive region 0 numerically differentiate residual to obtain tangent. IE(nie-8,ma). Equation number for element Lagrange multiplier. IE(nie-9,ma). Partition number for element Lagrange multiplier. IE(nie-10,ma) Global equation number. Table 3.5: Element control array IE use for material number maIEDOF(ndf,i,ma). Degree of freedom 1 for node i of material ma.Degree of freedom ndf for node i of material. Table 3.6: Element degree of freedom assignment array IEDOF use for material numberThe subroutine PGETD also may be used to retrieve internal data arrays by NAME for useFor example, if a development requires the nodal coordinateIf the retrieval is successfulThe precisionThe use of pgetd can leadFor such cases a call to pgetdOn the other hand, referenceChapter 4To add a mesh input command a subprogram with the name UMESHn, where n has aThe parameter TX is a character array which is assigned by the input and UPRT is aThe common block UMAC1The defaultAssignment of a uniqueWhen FEAP begins execution it scans all of the UMESHn routines and replaces theThus, when the command. HELP is issued while in interactive MESH mode, the user name will appear in thePurpose: User defined routine to input mesh data to FEAPInputs:Outputs:Set name ’mes1’ to user definedUser execution function statements followFigure 4.1: Sample UMESHn moduleWith this facility it isIt is possible to include up to 8 data items on the command line for user functions. AllIf the information is of type character itFor example if a userGETData VALUes 35The second parameter will be in TX(2)To recover the numerical value for the third parameter theIf more than 8 items are desired on the input line it is possible to recover their valuesTo recover their valuesIf users wish to add more than 10 material models it is possible to use the user function. UMESH which has the formUsers may add material models to elements by appending subprograms UMATIn and. UMATLn (where n have values from 0 to 9) to the FEAP system. The subprogram. UMATIn defines parameters used by the model and the subprogram UMATLn is called byTo activate a user material model the input data for the mesh MATErial commandFor example in a solid elementMATErial ma. SOLId. UCONstitutive xxxx v1 v2. The role of the xxxx and vi data will be described in Section 4.2.1. It is possible to use standard input parameters defined in Tables 5.5 to 5.8, as wellFor example, ifPurpose: User mesh command interfaceInputs:Outputs:Match on ’USER’: Add as many checks as desired with ’user’Figure 4.2: Sample UMESH moduleSOLId. ELAStic ISOTropic e nu. No standard commands should follow the UCON command. Alternatively, users may input elastic properties as part of their UMATIn module. IfIn all cases at least one blank record is always neededA sample module for a user constitutive model is shown in Fig. 4.3. As shown in thisThe name of the constitutive equationThe second parameter passesUsers may also provide additional input within the. UMATIn module using the routines PINPUT or TINPUT described in Sect. 2.1. The values.