Hypermesh知识总结.docx
- 文档编号:5444357
- 上传时间:2022-12-16
- 格式:DOCX
- 页数:17
- 大小:27.81KB
Hypermesh知识总结.docx
《Hypermesh知识总结.docx》由会员分享,可在线阅读,更多相关《Hypermesh知识总结.docx(17页珍藏版)》请在冰豆网上搜索。
Hypermesh知识总结
Hypermesh知识总结
1.如何从体单元提取面单元
TOOL->faces->find faces
2.在Hypermesh中使用OptiStruct求解器的重力、离心力、旋转惯性力施加方法
在HyperMesh中采用定义loadcols组件(colletors)的方式定义重力、离心力以及惯性力。
(1)重力
重力的施加方式在的card image中选择GRAV,然后create/edit,在CID中输入重力参考的坐标系,在G中输入重力加速度,在N1、N2、N3中输入重力方向向量在重力参考坐标系中的单位分量,然后返回即可。
(2)离心力
离心力的施加方式在的card image中选择RFROCE,然后create/edit,在G中输入旋转中所在节点编号,在CID中输入离心力所参考 的坐标系,在A中输入旋转速度,在N1、N2、N3中输入离心
力方向向量在离心力所参考坐标系中的单位分量,返回即可创建离心力;如果需要定义旋转惯性力,在RACC中输入旋转加速度即可,二者可以同时创建,也可单独创建。
如果在一个结构分析中,需要同时考虑结构自身的重力和外界施加的外载荷,那么可以建立重力load collector,但是外部载荷的load collector怎么建立?
是同时建立在重力的load
collector中吗?
如果是,那边有一个十分混淆的问题:
在你建立重力的load collector的时候,你选择了GRAV卡片,那么你凡是建立的该重力load collector之中的力都带有GRAV卡片属性
,这显然是不对的。
但是,如果你重新建立一个新的load collecotr,然后把外部载荷建立在其中,那么就有重力和外部载荷两个load collectors,但是在你建立subcase的时候你只能选择
一个load collector,那么你无论选择哪一个都必将失去另外一个,这就与我们的本意相矛盾了,我们是希望同时考虑结构自重和外部载荷的联合作用下进行分析的,这个时候应该怎么办?
?
怎么获得结构同时在自身重力和外部载荷作用下的变形和应力?
方法1:
工况组合; 使用"LOAD"卡片叠加重力载荷和其他载荷;创建一个load collector;card image选LOAD;点击create/edit;把下面的load_num_set改成你所要组合的载荷的数目;然后在
上面L1,L2,L3....选中你要组合的项,前面的s1,s2,s3,,,,是载荷组合时候的权重系数。
一般默认为1;
方法2:
其实还有个办法,也是新建个load collector,no card image,重力和外界施加的外载荷在之前加载后,通过Tool>organize>loads,将重力和外界施加的外载荷move到新建的load
collector中去,这样在建立subcase的时候就只有一个load了。
3. volume和volumefrc的区别?
volume是总体积(绝对数值),即优化后体积要达到多少;
volumefrc是体分比,即优化后体积占优化前的比例
4.hypermesh中N1 N2 N3 B的作用
用于确定方向的。
N1,N2,N3代表三个节点(或几何点),一般而言,这三个点都是临时节点,用过之后就自动消失。
三个不在一条直线上的点,可以唯一确定一个平面,而一个平面具有唯一的一个法向,也就
是3个点,确定了一个方向。
如果指指定N1,N2,那就是直接由N1到N2的方向向量。
B是进行某种操作的基点。
N1,N2,N3只是确定了方向,如果要切割一个面或者其他操作,有时候仅仅有方向还不够,还要通过B点来确定确切的切割位置。
如:
要将移动一条直线,需要指定移动方向(N1,N2),和移动的基点(即,从何处开始移动)
5.Hypermesh的缺省单位是什么?
答:
吨,mm和s。
6. 如何检测单元质量:
答:
除了check elems之外,还有qualityindex下的optimize功能。
7 component的作用?
component是hm的基本存储单位,所有的单元的实体都存储在component里面,如果不指定的话,
系统会默认一个component的,如果你对cad比较熟的话,这个类似cad里面的图层。
component中可以存储几何模型和单元,
8 HM中可以不设定单元属性(也就是选用什么单元),就直接对几何体划分网格?
答:
刚开始学ansys时,对先指定单元类型反而觉得有点别,HM和ansys不同,不过更加符合有限元的处理思路。
HM是一个通用的有限元前处理软件,这个前处理的概念不只是划分网格,还包括定义求解器认可的单元类型和边界条件,
无论最后使用ansys、nastran、Abaqus、Marc等求解,都可以划分好网格然后在hm里选择相应的模板为网格定义单元属性。
不过推荐的方式还是先定义好模板。
9.mesh,w/o surf mesh,delete surf mesh,Keep surf mesh,w/o surf surface Only的区别?
mesh, keep surf和mesh, dele surf,两者的划分网格方式都是要先生成曲面,再用automesh的功能在这个曲面上划分网格,这两者本质上没有区别的,只不过在划分网格以后一个保留曲面
,一个不保留。
关于mesh,w/o surf的问题,首先要明确的是w/o的含义,就是without。
w/o surf与曲面无关的,而且最重要的是它并不使用HyperMesh的automesh功能。
它有一点像Patran中的Isomesh。
它的
优点体现在对一些规则曲面(如长方形和梯形)划分网格的过程中。
surface Only仅生成表面而不进行网格分析
我们用ruled面板为一个长方形划分网格:
如果使用keep surf方式,可以看到当你调整一条边上的节点数量时,其对边上的节点数量并不发生改变,因此当两条对边上节点数量不一样时,生成的网格就不是规则的了,而如果用w/o
surf方式,无论如何改变一条边上的节点数量,其对边上的节点数量始终与其保持一致,这样生成的网格肯定也是规则的。
而only surface就是使用节点、曲线等生成曲面而不划分网格。
10 HM如何把一些node编入单独的collector?
答:
shift+f11或者Tools-organize
11 Hypermesh的缺省快捷键?
F1:
(hidden line)
F2:
(delete)删除
F3:
(replace)合并节点
F4:
(distance)测量距离
F5:
(mask)隐藏
F6:
(edit element)对单个网格进行编辑(如建立、合并、划分等)
F7:
(node edit)编辑节点 shift+F8功能与F7一样
F8:
(node)建立节点
F9:
(line edit)编辑线
F10:
(check elems)网格质量检查
F11:
(quick edit)几何清理常用工具
F12:
(automesh)自适应网格划分
Shift+F1:
(color)改变组件颜色
shift+F2:
(temp nodes)删除节点
shift+F3:
(edges) 合并节点,寻找自由边
shift+F4:
(translate)平移(模型,单元,节点等)
Shift+F5:
(find)查找(节点,单元等)
Shift+F7:
(project)投影(节点,线等)
Shift+F9:
(surface edit)裁剪面
Shift+F10:
(normals)调整单元法线方向
Shift+F11:
(organize)组件编辑
Ctrl+鼠标左键:
旋转
Ctrl+鼠标由键:
平移
Ctrl+鼠标滚轮:
缩放
F键:
模型全屏幕
12 如何设置快捷键?
答:
tools-》build meun
13 Ainite的三边原理和钱币原理是什么?
(1)两平面相接一定会有顶点;
(2)平面与曲面相接多半没有顶点,但相切一定有顶点;
(3) 凸面与凸面相接、凹面与凹面相接没有顶点;
(4) 凸面与凹面相接多半会有顶点;
(5)多边形有多个顶点,随便找个对角以线分面,即可减少顶点;
(6) 带有曲边的面多半会出现顶点不够的情况,根据俺的钱币原理(中国古代的钱币)将其分开,就会获得更多的顶点。
14 Hypermesh中face和顶点是如何确定的?
答:
HYPERMESH是通过FACE识别顶点的。
在OPTIONS=>MODELING=>FEATURE ANGLE中有定义角度。
当两个或两个以上相邻面的FEATURE ANGLE 小于设定角度时即被认为是一个FACE .
我不确定SOLID MAP中默认值是多少,但顶点VERTEX的识别即通过FACE
来使别的,即两个FACE之间会产生一个VERTEX。
15 Hyperworks文件的扩展名说明。
.out
OptiStruct output file containing specific information on the file set up, the set up of your optimization problem, estimate for the amount of RAM and disk space
required for the run, information for each optimization iteration, and compute time information. Review this file for warnings and errors that are flagged from
processing the .fem file.
.res
HyperMesh binary results file.
.hgdata
HyperGraph file containing data for the objective function, percent constraint violations and constraint for each iteration.
.his_data
OptiStruct history file containing iteration number, objective function values and percent of constraint violation for each iteration.
_optimization.HM.comp.cmf
HyperMesh command file used to organize elements into components based on their density result values. This file is only used with OptiStruct topology optimization
runs.
_optimization.HM.ent.cmf
HyperMesh command file used to organize elements into entity sets based on their density result values. This file is only used with OptiStruct topology optimization
runs.
sshield_optimization.oslog
OptiStruct log file containing compliance and volume calculations for each optimization iteration. In your UNIX or DOS shell, you can edit this file to see how many
iterations OptiStruct has completed.
_optimization.oss
Ossmooth file with a default density threshold of 0.3. The user may edit the parameters in the file to obtain the desired results.
_optimization.sh
Shape file for the final iteration. It contains the material density, void size parameters and void orientation angle for each element in the analysis. The .sh file
may be used to restart a run and, if necessary, run OSSmooth files for topology optimization.
.parm
Contains the I/O options and subcase information sections.
.fem
Contains the bulk data section.
The results file. Contains stress, displacement, shape, thickness and density information for all load cases at each iteration specified in the I/O options section.
Contains the element and possibly nodal, material density or topography information for each iteration specified in the I/O options section.
Component generating command file. This is a HyperMesh command file. When executed, it organizes all elements in the model into 10 new components based on their
material densities at the final iteration. The components are named 0.0-0.1, 0.1-0.2, 0.2-0.3, and so on, up to 0.9-1.0. All elements with a material density between
0% and 10% are contained in 0.0-0.1, all elements with a material density between 10% and 20% are contained in 0.1-0.2, and so on. This helps you visualize the results
by turning components on and off.Since elements cannot be in more than one component in HyperMesh, the original components do not contain any elements.
Entity set generating command file. This is a HyperMesh command file. It performs the same function as the
entity sets rather than components. The advantage of this method is that the elements remain in their original components but can still be selected and masked by
entity set.
Model and results file if the ANALYSIS I/O option is specified. Contains nodes, elements, stresses, strains, and displacements. Each load case, eigenmode is stored as
a time step. The contents of this file are controlled by the I/O options specified.
Model and optimization results file for the design iteration. Contains nodes, elements, shape, thickness, and density data for each iteration step. The contents of
this file are controlled by densres in the I/O section.
Model and static analysis results file for the design iteration. Contains nodes, elements, displacement, and stress data for each iteration step.
defined load step number. The contents of this file are controlled by results in the I/O section.
Model and normal modes analysis results file for the design iteration. Contains nodes, elements, displacement, and stress data for each iteration step.
eigenmode number. The contents of this file are controlled by results in the I/O section.
OptiStruct density file.Contains the element material densities for all iterations specified by densres the I/O section.
OptiStruct displacement file.Contains the nodal displacements for all load cases and eigenvectors in all iterations specified by results in the I/O section.
OptiStruct stress file.Contains the element stresses for all load cases in all iterations specified by results in the I/O section.
Element force file. Contains the forces acting on ELAS, ROD, BAR and BEAM elements. Output is specified by ELFORCE or FORCE in the I/O section.
Grid point force balance table file. Contains all forces acting on each grid point. Output is specified by GPFORCE in the I/O section.
The shape file for the final iteration of a topography/shape optimization. Contains the grid point coordinates. The format is that of the GRID card. The .grid file may
be used to restart a run. This file is an input file for OSSmooth.
The shape file for iteration N in a topography/shape optimization. Identical format to the
Output is specified by shres the I/O section.
Optimization history file. Contains the iteration history of the objective function, constraint functions, design variables, response functions. Output is specified by
deshis, and hisout in the I/O section.
Design history file. Contains the iteration history of the objective function and maximum constraint violation
Appl
- 配套讲稿:
如PPT文件的首页显示word图标,表示该PPT已包含配套word讲稿。双击word图标可打开word文档。
- 特殊限制:
部分文档作品中含有的国旗、国徽等图片,仅作为作品整体效果示例展示,禁止商用。设计者仅对作品中独创性部分享有著作权。
- 关 键 词:
- Hypermesh 知识 总结
![提示](https://static.bdocx.com/images/bang_tan.gif)