文档库

最新最全的文档下载
当前位置:文档库 > 在Abaqus中使用梁单元进行计算

在Abaqus中使用梁单元进行计算

在Abaqus中使用梁单元进行计算

在Abaqus中使用梁单元进行计算

(2012-03-26 11:28:00)

转载▼

标签:

分类:ABAQUS

abaqus

杂谈

xiaozity助理工程师:

在练习老庄的Crane例题时,欲提取梁元的截面应力。反复折腾后,小小体会,总结如下:(1)书中讲到:“线性梁元B21、B31及二次梁元B22、B32是考虑剪切变形的Timoshenko 梁单元;而三次梁元B23、B33不能模拟剪切变形,属Euler梁单元”。

(2)众所周知,当要考虑剪切变形时,例如深梁,采用Timoshenko梁单元比较合适。三次梁元由于可模拟轴线方向的三阶变量,因而对static问题,一个构件常常用一个三次单元就足够,特别对于分布载荷的梁,三次梁元的精度相当高。

(3)Abaqus会默认在积分点处的若干截面点输入应力值;但用户可自定义应力输出的截面点位置,这通过property-section-manage-edit-output points 来定义输出应力值的截面点;(4)特别要指出的是,无论B22还是B33还是其它梁元,其输出的应力分量只有S11,如图所示;那么,现在的问题是:

1:S11代表什么应力,根据经验,大家会认为11是1方向的正应力或主应力等等

2:为什么没有S22、S33、S12......

下面分别说明:

1:S11表达的是梁元的弯曲应力,即局部坐标系下截面上的正应力

2:只输出S11,而无其它应力,这是因为梁元之所以成为梁元,有一基本前提就是用梁元来模拟的构件,其正应力是最主要的,而剪应力是可忽略的;一个基本的佐证就是:众所周知,在建立梁的总势能方程时,总是讲剪切应变能是小量,因而它总是被忽略掉的;忽略剪应力的一个结果是:mises应力将与S11在数值上完全相同,不仅Abaqus如此,Ansys 也是如此,

这也难怪有人讲:“Timoshenko梁单元是骗人的,它根本没有考虑剪应力”;对这件事情,我想作如下评价:

(A)不仅Timoshenko梁单元,其它梁元(不考虑剪切变形)确实在应力的层面没有考虑剪应力的影响,这可从mises应力与S11的比较看出来;而为什么这样处理,理由如上所述,剪应力是高阶量,可忽略,否则就认为不能用梁元来模拟。

(B)尽管应力层面没有考虑剪应力,但在变形层面Timoshenko梁单元还是考虑了剪切的影响;所以说Timoshenko梁单元是骗人的说法,本人不太同意。

怪兽 :助理工程师

楼上的问题有些是重复的,但为了清晰,还是独立回答

(1)变形层面考虑剪切具体有两个方面:

1:在单元刚度中考虑了剪切刚度;

2:从所周知,梁元的变形是由结点位移插值获得;考虑剪切变形的位移的影响就体现在插值过程中考虑剪切变形;比如Timoshenke梁元采用弯曲和剪切独立插值的形状函数;

所谓应力层面不考虑剪切,是因为:

1:Abaqus/Ansys在计算Mises应力时只考虑了正应力,而没有把剪应力拿进去,所以它的Mises应力并非真正的等效应力,只是正应力取绝对值而已;

2:另外,说程序在应力层面不考虑剪切,也在于它根本就没有去计算剪应力,也因此而没有剪应力的输出选项;

为了更清楚的回答你的问题,有必要提一下有限元的过程:结点位移?插值获得单元位形?几何方程导出应变?本构方程获得应力;应力是在结果的最未端,只是程序认为剪应力太不重要,在与应力有关的结果中,没有去理会它而已。

(2)如果第一个问题我说清楚了,我想第二个就不是问题了

(3)所谓考虑剪切变形,具体的就在于:在梁元的单刚方程和插值函数中考虑了剪切变形的影响;影响谁呢,影响着原本不考虑剪切刚度的弯曲刚度和弯曲变形;也就是说,考虑剪切的影响,其实质在于:在弯曲刚度中把剪切刚度加进去,以使梁更刚硬一些,以模拟剪切变形不能忽略的“深梁”。

(4)4\5是一个问题,一并回答;具体如何证明,我考虑单独在Abaqus中用算例证明好象行不通;

要想了解特定的梁元是否考虑剪切变形,根据我现在的经验,只能看它的理论手册,一看单元刚度方程,二看插值函数。

如果假定程序给出了插值阶数相同的梁元A、B,其中:

A?考虑剪切

B?不考虑剪切

那么,在其它条件相同的情况下,A算出来的位移应该有小一些,因为它更刚硬;

如果一定要通过上述思路进行算例证明,考虑用ansys的梁元与Abaqus梁元进行上述比较,前提是选取的梁元插值阶数要相同。

不知道我说清楚没有~欢迎讨论

megvin助理工程师:

我猜,wong兄所提弯曲刚度提高了,可能是基于插值阶数降低之后,弯曲变得刚硬.这没问题;

我强调的是,比较的前提是:选取相同的插值阶段;更具体一点,是选取相同的弯曲插值阶次;只有

在这个条件下,才能比较两者的差别.

选取相同的弯曲插值阶次的目的在于:固定其弯曲刚度

chsxiaolin助理工程师:

按照上面的说法,与其说“应力层面不考虑剪应力,变形层面考虑剪切变形”,还不如说“只考虑弹性剪切,不考虑塑性剪切及其影响”。单说不考虑剪应力又哪里来的剪切刚度呢?

针对楼上提法,稍稍再补充一下:

1:Abaqus/Ansys(其它程序不清楚)中,考虑剪切的影响,一律认为剪切永远是弹性的;如果说程序一定要计算剪应力,其本构也一定是基于弹性本构确定。为什么认为剪切不会进入塑性,可能是因为:

如前所述,还是基于梁元的特点,认为剪切一般只会处于弹性;而且对梁元而言,剪切变形总是弯曲的小量,能考虑一下剪切影响已经很不错了~

2:剪切刚度是构件的抗剪切变形的能力,是刚度层次;剪应力则属于是截面层次;也就是说:在变形的时候考虑剪切刚度的影响,但在计算应力的时候,并没有去理会到底产生了多大的剪应力。

From:http://58.213.153.47/viewthread.php?tid=1150914

合理选用梁单元——Beam Elements in ABAQUS

作者:麦田

本文内容主要译自ABAQUS Documents

1.梁理论

1.1应用梁单元之前,首先应当考察问题是否适合用梁单元建模。

梁理论是用一维近似三维,近似的前提是长细比假定,即梁的截面尺寸相比于梁轴线方向的典型尺寸足够小。所谓典型尺寸是一种整体尺寸,而非单元长度,比如:

?支座间的距离;

?发生显著改变的梁截面间的距离;

?感兴趣的最高阶振动模态的波长;

梁单元是三维或二维空间中的一维线单元,具有一定的抵抗线(梁轴线)变形的刚度。这种变形包含轴向变形、弯曲变形,发生于梁轴线与横截面间的横向剪切变形,空间中还包含扭转变形。ABAQUS/Standard中的部分梁单元还包含翘曲变形(发生在梁横截面上的不均匀的出平面变形)。梁单元的主要优势在于几何构造简单,并且自由度较少。它以“参考线”(梁轴线)的运动代替实际上的三维实体梁的运动,这种几何上简化的前提是假定梁的全部变形可以仅仅从“参考线”(梁轴线)位置的函数得到。应用梁单元的关键在于判断这种一维建模方法是否合适。

基本假定是垂直于梁轴线的平面,即梁截面不能在其在身平面内变形(除了梁截面面积的不断变化,这可能发生在几何非线性分析中,并且梁截面上各个方向具有相同的应变)。使用任何梁单元前都应仔细考察此假定是否成立,尤其是分析承受大量弯矩或轴向拉、压荷载的非实体截面,比如管道、I形及U形截面。这些截面可能发生崩溃(section collapse),使截面性能变的很差,不能被梁理论预测。类似地,薄壁弯曲管道的抗弯性能更弱,也不能被梁理论预测,因为管壁很容易在自身平面内弯曲,这是由于上述基本假定导致的梁理论所不能考虑的另一种效应。

1.2在动力分析和特征值分析中应用梁单元

对于细长梁结构,通常梁横截面的转动惯量影响并不显著(绕梁轴线的扭转除外)。因此,ABAQUS/Standard忽略了欧拉-伯努力(Euler-Bernoulli)梁元弯曲变形时梁截面的转动惯量。对于较厚的梁,转动惯量对动力分析有一定影响,但影响程度要比剪切变形小。

对于铁木辛克(Timoshenko)梁元,程序通过横截面的几何特性计算惯性特性,与扭转模态和弯曲模态相关的转动惯量是不同的。对于非对称横截面,转动惯量在各个弯曲方向也不相同。ABAQUS允许用户选择铁木辛克梁元的转动惯量公式,如果选择近似的各向同性公式,在ABAQUS/Standard中,所有的转动自由度都被赋予和扭转模态关联的转动惯量,而在ABAQUS/Explicit中,则被赋予放大了的弯曲惯量,通过放大系数的选择使稳定时间增量最大化;梁横截面的质量中心位于节点处。当采用精确的各向异性公式时,弯曲和扭转对应的转动惯量是不同的,而且当梁截面的质量中心不在节点处时,在梁截面定义中包含平动自由度和转动自由度的耦合。使用精确的转动惯量公式(默认)时,可以定义附加质量和附加转动惯量,它们仅影响梁的惯性反应,不增加结构的刚度。

2.梁单元的选择

ABAQUS中的梁单元分为欧拉-伯努力梁元和铁木辛克梁元两类,支持实心截面、薄壁闭口截面、薄壁开口截面。

ABAQUS/Standard中的梁单元包括:

?平面及空间的欧拉-伯努力(细长)梁;

?平面及空间的铁木辛克(剪切变形)梁;

?线性、二次、三次插值公式;

?翘曲(开口截面)梁;

?管单元

?杂交梁,通常用于具有明显转动的非常刚硬的梁;

ABAQUS/Explicit中的梁单元包括:

?平面及空间的铁木辛克(剪切柔性)梁;

?线性及二次插值公式;

2.1欧拉-伯努力梁

欧拉-伯努力梁元(B23, B23H, B33, B33H)仅在ABAQUS/Standard中提供。不允许横向剪切变形;初始垂直于梁轴线的平截面变形后依然保持平面(如果没有翘曲),并垂直于梁轴线。只能用于模拟细长梁:梁截面尺寸相比于梁轴线方向的典型尺寸,即长细比较小。对于由均一

材料构成的梁,只有当典型梁截面尺寸小于梁轴线方向典型尺寸的1/15时,横向剪切变形才

可以忽略。

单元不包含由压力产生的荷载刚度。

插值:

欧拉-伯努力梁元采用三次插值公式,这对于梁上分布荷载是精确的。因此,适合于动力振动

分析——因为d’Alembert荷载(达朗贝尔荷载,即惯性力)也是分布的。

三次梁单元适合于分析小应变、大转动问题。由于采用近似的方程,不适合分析扭转稳定问题,也不适合分析有特别大转动的问题(比如约180度),此时,应该采用一次或二次梁单元。

质量公式:

欧拉-伯努力梁元采用一致质量公式。绕梁轴线扭转时的转动惯量和铁木辛克梁元一样。不能

定义附加惯量。

2.2铁木辛克梁

铁木辛克梁(B21, B22, B31. B32, B31OS, B32OS, PIPE21, PIPE22, PIPE31, PIPE32及对应的杂

交单元)允许横向剪切变形。既可分析厚梁,又可细长梁。对于由均一材料构成的梁,对于截面尺寸达到轴向典型尺寸或对于结构反应有显著贡献的最高阶振动波长的1/8的梁,剪切变形

梁理论能够提供有用的结果。在这个比例以外,如果还仅仅用梁轴线位置的函数来描述构件的行为,将得不到足够准确的结果。

ABAQUS假定铁木辛克梁的横向剪切变形是线弹性的,具有固定的模量,因此独立于梁截面

的轴向拉、压和弯曲反应。

对于大部分梁截面,ABAQUS会自动计算横向剪切刚度,用户也可以自定义。如果程序不能

从输入部分得到剪切模量值,将无法计算缺省的剪切刚度,比如使用子程序(UMAT, UHYPEL, UHYPER, VUMAT)定义材料的情况。对于这些情况,用户必须自己定义剪切刚度值。

铁木辛克梁元可以承受很大的轴向变形,并假定由扭转引起的轴向应变很小。在拉(压)-扭组合荷载下,只有当轴向应变不太大的时候,才能精确计算扭转引起的剪应变。关于剪切刚度的计算可参考帮助文档。

插值:

程序为有限轴向应变、剪切变形梁单元提供一次和二次插值。

单元B21, B31, B31OS, PIPE21, PIPE31及对应的杂交单元采用线性插值。特别适合于分析接触问题,比如沟渠或海底管线的铺设,钻头和井孔的接触,及它们对应的动力学问题。

单元B22, B32, B32OS, PIPE22, PIPE32及对应的杂交单元采用二次插值。

质量公式:

线性铁木辛克梁元采用集中质量公式。ABAQUS/Standard中,二次铁木辛克梁元采用一致质量公式,但动力分析中将按照1:4:1的分布,采用集中质量公式。ABAQUS/Explicit中的二次铁木辛克梁元也采用上述形式的集中质量公式。

转动惯量和附加惯量:

缺省情况下,铁木辛克梁采用精确的(各向异性,位移-转角耦合)转动惯量公式,也可以采用各向同性的、解耦的近似方法。

例外是,对于静力分析中采用自动稳定控制(automatic stabilization)的情况,程序在计算铁木辛克梁的质量矩阵时,直接假定转动惯量为各向同性,忽略指定的转动惯量类型。

在一些结构应用中,对于具有复杂几何形状和质量分布的截面,梁单元是一种一维的近似。沿梁长度方向,梁截面上可能存在着对结构刚度没有贡献,但却对惯性有贡献的分布质量,如机器、船舱中的货物、装满流体的容器等。这种情况下,可以在梁截面定义中定义附加质量和附加转动惯量。还可以定义与附加惯量相关的质量比例阻尼。程序根据质量比例,通过对材料阻尼和附加惯性阻尼进行加权平均,确定单元的质量比例阻尼。

翘曲(开口)梁:

在三维空间中使用梁单元时,必须注意梁截面上可能存在的由于扭矩引起的翘曲变形,除了圆形截面外,所有的截面在承受扭矩时都会发生出平面变形。翘曲将改变截面上的剪应变分布。

如果翘曲没有得到有效约束,开口截面很容易发生扭曲,尤其是梁截面壁厚较薄的情况。

单元B31OS, B32OS以及对应的杂交单元通过在每个节点处增加一个自由度来考虑翘曲,并假定翘曲变形是截面上位置的函数,仅翘曲幅度随截面在梁轴线上的位置而改变,并且上述单元只能在ABAQUS/Standard中使用。它们可用于分析薄壁、开口截面,对于这些截面,翘曲约束起一定作用,由翘曲引起的轴向变形不可忽略,例如I形截面和任意开口截面。在其他的梁单元中,翘曲被认为是自由的,翘曲引起的任何轴向应力都被忽略。用这些单元分析薄壁、开口截面梁时,扭转不能被很好的反映。

通常,只有当通过节点的梁轴线是连续的,并且节点两侧的梁横截面相同时,翘曲幅度才是连续的。因此,如果开口梁在节点处相交,那么就需要为这个具有不同轴线方向的交叉梁定义单独的节点,并且需要为两个相交构件在这个节点处翘曲幅度定义合理的约束。例如,如果接点被加强,翘曲变形就可能被消除;那么,在接点连接处,作为边界条件,翘曲自由度7应该在合适的构件上被完全约束。

参考资料:

ABAQUS, Inc. 2008.Abaqus Theory Manual, Version 6.8. Providence, Rhode Island: DassaultSystèmes.

From: http://www.wendangku.net/doc/ef6c66d826fff705cc170a52.html/s/blog_59f421580100do3p.html

在进行梁单元截面内力的后处理时,会遇到SF1、SF2、SF3、SM1、SM2、SM3,其具体含义是什么呢?

根据23.3.8 Beam element library的解释

Section forces, moments, and transverse shear forces

SF1 Axial force.——梁单元轴力

SF2 Transverse shear force in the local 2-direction (not available for B23, B23H, B33,

B33H).——n2方向的横向剪力

SF3 Transverse shear force in the local 1-direction (available only for beams in space, not available for B33, B33H).——n1方向的横向剪力

SM1 Bending moment about the local 1-axis.——绕n1轴的弯矩

SM2 Bending moment about the local 2-axis (available only for beams in space).——绕

n2轴的弯矩

SM3 Twisting moment about the beam axis (available only for beams in space).——绕

梁单元轴线的扭矩

ABAQUS的任务管理命令可以暂停、恢复、和终止一个正在背景运行的任务,方

法如下(在命令行输入并运行):

1、暂停一个正在运行的任务:

abaqus suspend job=job-name

2、恢复一个暂停的任务:

abaqus resume job=job-name

3、终止一个正在运行的任务:

abaqus terminate job=job-name

其中任务暂停(suspend)的时候,windows任务管理栏中仍会保留standard/explicit 的计算线程,只是不再使用CPU资源,当任务恢复(resume)的时候继续工作。

任务终止则就像CAE中提交的任务的KILL功能类似,直接cut掉正在运行的任务,不可恢复。其实也就和在windows任务管理栏中强行终止差不多,但属于合法操作。

ABAQUS中USER TIME/SYSTEM TIME/TOTAL CPU TIME/WALL CLOCK的意义

2011-02-24 21:56:29| 分类:ABAQUS | 标签:time cpu total clock wall |字号订

USER TIME refers to the CPU time spent executing ABAQUS.

SYSTEM TIME refers to the amount of OS kernel CPU time spent by the operating system doing work on behalf of the ABAQUS process.

TOTAL CPU TIME is the sum of these two numbers.

WALL CLOCK time refers to the actual physical time spent for the analysis process to complete. If the analysis job is running on a single CPU, and the job has exclusive access to that CPU, the difference between TOTAL CPU TIME and WALL C LOCK TIME is largely the time taken to perform all I/O requests.

求解器算法比较应当用Total CPU,对用户感到的时间用Wall clock

在进行壳单元截面内力的后处理时,会遇到SF1、SF2、SF3、SF4、SF5、SF6、SM1、SM2、SM3,其具体含义是什么呢?

根据23.6.8 Continuum shell element library 的解释

Section forces, moments, and transverse shear forces

SF1 Direct membrane force per unit width in local 1-direction.——n1方向单位宽度内的正拉(压)力

SF2 Direct membrane force per unit width in local 2-direction.——n2方向单位宽度内的正拉(压)力

SF3 Shear membrane force per unit width in local 1–2 plane.——n1-n2平面内单位宽度内的剪力

SF4 Transverse shear force per unit width in local 1-direction.——n1方向单位宽度内的横向剪力

SF5 Transverse shear force per unit width in local 2-direction.——n2方向单位宽度内的横向剪力

SF6 Thickness stress integrated over the element thickness.——壳单元厚度方向的集中力

SM1 Bending moment force per unit width about local 2-axis.——绕n2轴的弯矩

SM2 Bending moment force per unit width about local 1-axis.——绕n1轴的弯矩

SM3 Twisting moment force per unit width in local 1–2 plane.——n1-n2平面内的扭矩

File extensions

abq

State file, only used by Abaqus/Explicit. It is written by the analysis, continue, and recover options. It is read by the convert and recover options. This file is required for restart.

axi

Symmetric model data file, only used by Abaqus/Standard. It is written during symmetric model generation by the datacheck and analysis options.

bsp

Text file containing beam cross-section properties for meshed section profiles. It is written by Abaqus/Standard during meshed beam cross-section generation.

cid

Auto-release file, which contains information needed for license recovery and suspension. com

Command file, created by the Abaqus execution procedure.

dat

Printed output file. It is written by the analysis, datacheck, parametercheck, and continue options. Abaqus/Explicit does not write analysis results to this file.

eig

Lanczos eigenvector file. This is a temporary scratch file that is used to store the eigenvectors calculated by the Lanczoseigensolver during the solution procedure.

f

User subroutine or other special-purpose FORTRAN file.

fct,uft

Sparse solver factor files. These temporary scratch files are used by the sparse solver in Abaqus/Standard. The uft file is created only when the unsymmetric solver is used.

fil

Results file. It is written by the analysis and continue options in Abaqus/Standard and by the convert=select and convert=all options in Abaqus/Explicit.

fin

Results file created when changing the format of the .fil file using the abaqusascfil command. It can be in either ASCII or binary format. (See ―Execution procedure for

ASCII translation of results (.fil) files,‖ Section 3.2.9.) The ASCII format is convenient for data transfer between machines that do not have compatible binary data formats.

inp

Analysis input file. It is read when the analysis, datacheck, and parametercheck options are selected.

ipm

Interprocess message file. It is written when an analysis is run from Abaqus/CAE, and it contains a log of all messages sent from Abaqus/Standard or Abaqus/Explicit to Abaqus/CAE.

lck

Lock file for the output database. This file is written whenever an output database file is opened with write access; it prevents you from having simultaneous write permission to the output database from multiple sources. It is deleted automatically when the output database file is closed or when the analysis that creates it ends. The ask_delete environment file parameter setting will not affect the lock file.

lnz

Lanczos vector file. This is a temporary scratch file that is used to store the Lanczos vectors and weighted Lanczos vectors.

log

Log file, which contains start and end times for modules run by the current Abaqus execution procedure.

mdl

Model file. It is written by the datacheck option in Abaqus/Standard and

Abaqus/Explicit. It is read and can be written by the analysis and continue options in Abaqus/Standard. It is read by the analysis and continue options in Abaqus/Explicit. Multiple model files may exist if the element operations are executed in parallel in an Abaqus/Standard analysis. In such a case a process identifier is attached to the file name. This file is required for restart.

msg

Message file. It is written by the analysis, datacheck, and continue options in Abaqus/Standard and Abaqus/Explicit. Multiple message files may exist if the element operations are executed in parallel in an Abaqus/Standard analysis. In such a case a process identifier is attached to the file name.

nck

Nickname file used by Abaqus/Standard. It stores a set of internal identifiers for the degrees of freedom in a model.

odb

Output database. It is written by the analysis and continue options in Abaqus/Standard and Abaqus/Explicit. It is read by the Visualization module in Abaqus/CAE

(Abaqus/Viewer) and by the convert=odb option. This file is required for restart.

opr

Sparse solver operator file, which is a temporary scratch file used by the sparse solver in Abaqus/Standard.

pac

Package file, which contains model information and is used by Abaqus/Explicit only. It is written by the analysis and datacheck options. It is read by the analysis, continue, and recover options. This file is required for restart.

par

Modified version of original parametrized input file showing input parameters and their values.

pes

Modified version of original parametrized input file showing input free of parameter information (after input parameter evaluation and substitution has been performed).

pmg

Parameter evaluation and substitution message file. It is written when the input file is parametrized.

prt

Part file. This file is used to store part and assembly information and is created even if the input file does not contain an assembly definition. The part file is required for restart, import, sequentially coupled thermal-stress analysis, symmetric model generation, and underwater shock analysis, even if the model is not defined in terms of an assembly of part instances. This file may also be needed for submodeling analysis.

psf

Python scripting file. You must create this type of file to define a parametric study.

res

Restart file, which contains information necessary to continue a previous analysis. The restart file is written by the analysis, datacheck, and continue options. It is read by any restarted analysis.

scr

Lanczos scratch file. This is a temporary scratch file that is used to hold temporary information required by the Lanczos solver.

sct

Perturbation results scratch file. This file temporarily holds element results needed for output in Abaqus/Standard perturbation steps.

sdb

Sparse solver database file. This is a temporary file that is used by the sparse solver.

sel

Selected results file, used by Abaqus/Explicit. It is written by the analysis, continue, and recover options and is read by the convert=select option. This file is required for restart.

sim

Linear dynamics data file. It is written during the frequency extraction procedure in SIM-based linear dynamics analyses (see ―Using the SIM architecture for mode-based linear dynamic analyses‖ in ―Dynamic analysis procedures: overview,‖ Section 6.3.1, for details) and is used to store eigenvectors, substructure matrices, and other modal system information. This file is required for restart.

sol

Sparse solver file used to store the solution vectors for a problem. This file is a temporary file used by the sparse solver in Abaqus/Standard.

sst

Sparse solver scratch file. This temporary scratch file is used by the sparse solver in Abaqus/Standard.

sta

Status file. Abaqus writes increment summaries to this file in the analysis, continue, and recover options.

stt

State file. It is written by the datacheck option in Abaqus/Standard and Abaqus/Explicit. It is read and can be written by the analysis and continue options in Abaqus/Standard. It is read by the analysis and continue options in Abaqus/Explicit. Multiple state files may exist if the element operations are executed in parallel in an Abaqus/Standard analysis. In such a case a process identifier is attached to the file name. This file is required for restart. sup

Substructure file, used by Abaqus/Standard.

var

File containing information about the input file variations generated by a parametric study.

023

Communications file. It is written by the analysis and datacheck options and is read by the analysis and continue options.

ABAQUS中的文件类型详解

2011-02-13 21:19:25| 分类:ABAQUS |字号订阅

ABAQUS产生几类文件:有些是在运行是产生,运行后自动删除;其它一些用于分析、重启、后处理、结果转换或其它软件的文件则被保留,详细如下:

1.model_database_name.cae

模型信息、分析任务等

2.model_database_name.jnl

日志文件:包含用于复制已存储模型数据库的ABAQUS/CAE命令

*.cae和 *.jnl构成支持CAE的两个重要文件,要保证在CAE下打开一个项目,这两个文件必须同时存在;

3.job_name.inp

输入文件。由abaqus Command支持计算起始文件,它也可由CAE打开;

4. job_name.dat

数据文件:文本输出信息,记录分析、数据检查、参数检查等信息。

ABAQUS/Explicit 的分析结果不会写入这个文件

5.job_name.sta

状态文件:包含分析过程信息

6. job_name.msg

是计算过程的详悉记录,分析计算中的平衡迭代次数,计算时间,警告信息,等等可由此文件获得。用STEP模块定义

7. job_name.res

重启动文件,用STEP模块定义

8.job_name.odb

输出数据库文件,即结果文件,需要由Visuliazation打开

9.job_name.fil

也为结果文件,可被其它应用程序读入的分析结果表示格式。ABAQUS/Standard

记录分析结果。ABAQUS/Explicit.的分析结果要写入此文件中则需要转换,convert=select 或convert=all

10. abaqus.rpy

记录一次操作中几乎所有的ABAQUS/CAE命令

11. job_name.lck

阻止并发写入输出数据库,关闭输出数据库则自行删除

12.model_database_name.rec

包含用于恢复内存中模型数据库的ABAQUS/CAE命令

13. job_name.ods

场输出变量的临时操作运算结果,自动删除

14.job_name.ipm

内部过程信息文件:启动ABAQUS/CAE分析时开始写入,记录了从

ABAQUS/Standard或ABAQUS/Explicit 到 ABAQUS/CAE的过程日志

15.job_name.log

日志文件:包含了 ABAQUS执行过程的起止时间等

16.job_name.abq

ABAQUS/Explicit模块才有的状态文件,记录分析、继续和恢复命令。为restart所需的文件。

17.job_name.mdl

模型文件:在ABAQUS/Standard 和 ABAQUS/Explicit中运行数据检查后产生的文件,.在 analysis和continue 指令下被读入并重写,为restart所需的文件。

18.job_name.pac

打包文件:包含了模型信息,仅用于ABAQUS/Explicit ,该文件在执行 analysis、datacheck命令时写入,执行 analysis, continue, recover 指令时读入,restart时需要的文件。

19.job_name.prt

零件信息文件:包含了零件与装配信息.。restart时需要

20.job_name.sel

结果选择文件:用于ABAQUS/Explicit,执行analysis、continue、recover 指令时写入并由 convert=select 指令时读入,为restart所需的文件。

21.job_name.stt

状态外文件:数据检查时写入的文件,在ABAQUS/Standard中可在analysis 、

continue 指令下读并写入,在ABAQUS/Explicit中可在analysis 、continue 指令下读入。为restart所需的文件。

22.job_name.psf

脚本文件:用户定义 parametric study时需要创建的文件

23.job_name.psr

参数化分析要求的输出结果,为文本格式

24.job_name.par

参数更改后重写的参数形式表示的inp文件

25.job_name.pes

参数更改后重写的inp文件

ABAQUS命令汇总及参数的默认设置(ABAQUS Command Summary and Command line default parameters)

2011-02-13 20:33:50| 分类:ABAQUS |字号订阅

Command summary

abaqus job=job-name

[analysis | datacheck | parametercheck | continue |

convert={select | odb | state | all} | recover | syntaxcheck |

information={environment | local | memory | release | support

| system | all}]

[input=input-file]

[user={source-file | object-file}]

[oldjob=oldjob-name]

[fil={append | new}]

[globalmodel={results file-name | output database file-

name}]

[cpus=number-of-cpus]

[parallel={domain | loop}]

[domains=number-of-domains]

[mp_mode={mpi | threads}]

[standard_parallel={all | solver}]

[memory=memory-size]

[interactive | background | queue=[queue-

name][after=time]]

[double={explicit | both}]

[scratch=scratch-dir]

[output_precision={single | full}]

[madymo=MADYMO-input-file]

[port=co-simulation port-number]

[host=co-simulation hostname]

[timeout=co-simulation timeout value in seconds]

[unconnected_regions={yes | no}]

Command line default parameters

The following parameters provide default values for various settings that would otherwise have to be specified on the command line (see ―Execution p rocedure for Abaqus/Standard and Abaqus/Explicit,‖ Section 3.2.2). Values given on the command line override values specified in the environment files.

cpus

Number of processors to use if parallel processing is available. The default is 1. domains

The number of parallel domains in Abaqus/Explicit. If the value is greater than 1, the domain decomposition will be performed regardless of the values of the parallel and cpus parameters. However, if parallel=domain, the value of cpus must be evenly divisible into the value of domains. If this parameter is not set, the number of domains defaults to the number of processors used during the analysis run if parallel=domain or to 1 if parallel=loop.

double_precision

The default precision version of Abaqus/Explicit to run if you do not specify the precision version on the abaqus command line. Possible values are EXPLICIT (only the Abaqus/Explicit analysis is run in double precision) or BOTH (both the Abaqus/Explicit packager and analysis are run in double precision). The default is EXPLICIT.

parallel

The default parallel method in Abaqus/Explicit if you do not specify the parallel method on the abaqus command line. Possible values are DOMAIN or LOOP; the default value is DOMAIN.

run_mode

Default run mode (interactive, background, or batch) if you do not specify the run mode on the abaqus command line. The default for abaqusanalysis is "background", while the default for abaqusviewer is "interactive".

scratch

Directory to be used for scratch files. This directory must exist (i.e., it will not be created by Abaqus) and must have write permission assigned. On UNIX platforms the default value is the value of the $TMPDIR environment variable or /tmp if $TMPDIR is not defined. On Windows platforms the default value is the value of the %TEMP% environment variable or \TEMP if this variable is not defined. During the analysis a subdirectory will be created under this directory to hold the analysis scratch files. The name of the subdirectory is constructed from your user name, the job id, and the job's process identifier. The subdirectory and its contents are deleted upon completion of the analysis.

standard_parallel

The default parallel execution mode in Abaqus/Standard if you do not specify the parallel mode on the abaqus command line. If this parameter is set equal to ALL, both the element operations and the solver will run in parallel. If this parameter is set equal to SOLVER, only the solver will run in parallel. The default parallel execution mode is ALL. unconnected_regions

If this variable is set to ON, Abaqus/Standard will create element and node sets in the output database for unconnected regions in the model during a datacheck analysis. Element and node sets created with this option are named MESH COMPONENT N, where N is the component number. The default value is OFF.

System resource parameters

The following environment file variable can be set after the code has been installed to change the resources used by Abaqus and, therefore, to improve system performance. By default, Abaqus detects the physical memory on a machine (or on each compute node in a cluster) and allocates a percentage of the available memory based on the machine platform (for details, refer to the SIMULIA Online Support System, which is accessible from the My Support page at http://www.wendangku.net/doc/ef6c66d826fff705cc170a52.html). You can override the default percentage by specifying a number followed by the percentage sign. The variable can also be defined as the number of megabytes or the number of gigabytes. More detailed information about changing the system resources used by Abaqus is given in ―Managing memory and disk use in Abaqus,‖ Section 3.4.1.

memory

Maximum amount of memory or maximum percentage of the physical memory that can be allocated during the input file preprocessing and during the Abaqus/Standard analysis phase. For parallel execution on computer clusters, this memory limit specifies the maximum amount of memory that can be allocated on each process.