RADIOSS (Bulk Data Format), OptiStruct
一、FEA Setup and Modeling
【1】How can I apply multiple constraints or loads in a subcase?
1.
Put multiple loads in one load collector, and include that one load collector in the subcase. The same method can be used in the case of multiple constraints.
2.
Create load collectors for each and every load and constraint set. When you want to apply multiple loads in a subcase, a new load collector needs to be created with the LOAD card. Then, individual load collectors can be combined using the LOAD card. The LOAD card also enables you to associate an independent weighting factor to an individual load collector. In the case of applying multiple constraints, create a new load collector with the SPCADD card, and follow the same procedure as in the multiple load case. Once the combined load collectors are created, they can be applied in a subcase.
一，设置有限元
分析
定性数据统计分析pdf销售业绩分析模板建筑结构震害分析销售进度分析表京东商城竞争战略分析
与建模
【1】如何申请多个约束在一个子用例或负载？
1。把多个负载在一个负载收藏家，包括该子用例中的一个负载收藏家。同样的方法可用于多种约束条件。
2。创建每一个载荷和约束集负载收藏家。当你想用一个子用例多个负载，一个新的集电极负载需要用在LOAD卡创建的。然后，个人收藏家负载可以组合使用LOAD卡。在LOAD卡还可以让您联想到一个独立的个体因素加权负载收藏家。在应用多约束的情况下，创建一个新的负载SPCADD卡收藏家，并按照在多工况相同的程序。一旦联合负荷收藏家的创建，它们可以应用在子用例。
【2】How can I specify an enforced displacement in a subcase (or loadstep) in an OptiStruct input deck?
There are two ways to do this:
1.
Create a single SPC definition containing the enforced displacement information and reference this within the subcase (loadstep) definition.
2.
Create an SPC, SPCD pair, with the SPC constraining the dof that is to have the enforced displacement and the SPCD defining the magnitude and dof of the enforced displacement. Both must be referenced in the subcase (loadstep) definition.
2】我可以指定如何在输入中的一个OptiStruct甲板子用例（或loadstep）被迫流离失所？
有两种方法可以做到这一点：
1。建立一个单一的定义包含最高人民法院被迫流离失所的信息和参考在子用例（loadstep）的定义这一点。
2。创建最高人民法院，SPCD与SPC制约自由度是有强迫流离失所和SPCD确定的规模和实施的位移自由度一双。两者都必须被引用在子用例（loadstep）的定义。
【3】What kinds of checking does the check run perform? What is the difference between the CHECK and ANALYSIS cards in the input deck?
The check run checks for syntax errors, input errors (i.e. missing LOAD or SPC card in subcase), and gives the recommended memory for the analysis or optimization run. All errors or warning messages will be output to the .out file.
If the CHECK card is included in the input file, chosen as a Run Option in HyperMesh, or added as a run option on the command line, OptiStruct will only perform the check run.
If the ANALYSIS card is included in the input deck, chosen as a Run Option in HyperMesh, or added as a run option on the command line, OptiStruct will perform only baseline analysis and no optimization.
Note:
A request for a check run always takes precedence over a request for an analysis run, and a request for an analysis run always takes precedence over an optimization.
【3】种什么样的检查检查运行是否执行？之间有什么检查并分析卡，在输入甲板区别？
检查错误的语法检查，运行，输入错误（即缺少子用例LOAD或最高人民法院卡），并给出了优化运行的分析或建议内存。所有的错误或警告信息将被输出到。出的文件。
如果支票卡是在输入文件作为在HyperMesh运行选项选择，或在命令行运行的选项添加，OptiStruct只会执行检查运行。
如果分析卡在输入甲板内，选择了作为一个HyperMesh运行选项，或在命令行运行的选项添加，OptiStruct只须执行基准分析，也没有优化。
注：为检查运行要求总是比一个请求的优先级运行的分析，并为分析运行的要求总是比一个优化的优先级。
【4】How can I specify the temporary directory (where all of the scratch files are written) to run OptiStruct jobs?
In an OptiStruct input, the complete path to the temporary directory (which has enough disk space for the scratch files) can be entered on the TMPDIR card. The TMPDIR card is available in HyperMesh in the control cards panel.
Also, please note that when a temporary directory is specified, it is important to verify that the directory has correct read and write permissions.
3】种什么样的检查检查运行是否执行？之间有什么检查并分析卡，在输入甲板区别？
检查错误的语法检查，运行，输入错误（即缺少子用例LOAD或最高人民法院卡），并给出了优化运行的分析或建议内存。所有的错误或警告信息将被输出到。出的文件。
如果支票卡是在输入文件作为在HyperMesh运行选项选择，或在命令行运行的选项添加，OptiStruct只会执行检查运行。
如果分析卡在输入甲板内，选择了作为一个HyperMesh运行选项，或在命令行运行的选项添加，OptiStruct只须执行基准分析，也没有优化。
注：为检查运行要求总是比一个请求的优先级运行的分析，并为分析运行的要求总是比一个优化的优先级。
【5】What is the OptiStruct equivalent of the Nastran K6ROT parameter?
In Nastran, shell elements have five degrees of freedom per node, three displacements and two rotations. The K6ROT parameter provides an in-plane rotational stiffness (so-called drilling stiffness) accounting for the missing sixth degree of freedom. The absolute stiffness value provided by K6ROT is applied to all shell elements in the same manner. This way a singular stiffness matrix is avoided for shell models.
In OptiStruct, the shell elements have a built-in drilling stiffness. Each element’s drilling stiffness is calculated from the element properties using a shape function. This way, the shell elements in OptiStruct have six degrees of freedom per node, three displacements and three rotations. The OptiStruct approach is more accurate, since it derives the drilling stiffness from the structural properties of each element. This leads to somewhat different results between OptiStruct and Nastran for shell models.
An alternative shell element formulation is available in OptiStruct that matches more closely with the Nastran formulation. The primary difference with respect to the default OptiStruct shells is the absence of drilling stiffness. Some stabilization terms and other adjustments are added for reliable performance. The resulting elements are generally more flexible than the default OptiStruct shell elements, especially on curved geometries.
【5】什么是Nastran的K6ROT参数OptiStruct相像？
在Nastran的，有五度壳单元，每节点的自由，两三个位移和旋转。该K6ROT参数提供了一个平面旋转刚度失踪自由第六度（所谓的钻劲度）会计。绝对刚度值K6ROT提供适用于所有以相同的方式壳单元。这是一个奇异的壳刚度矩阵模型避免的方法。
在OptiStruct，外壳元素有一个内置的钻井刚度。每个元素的钻井刚度计算元素使用形状函数的性质。这样，在OptiStruct壳元素六度每个节点自由，三位移和三个旋转。该OptiStruct方法更准确，因为它源于从每个元素的结构性能自钻刚度。这导致有些不同之间OptiStruct和Nastran的结果壳模型。
另一种是在壳单元制定OptiStruct可用的匹配更加紧密地与Nastran的制定。相对于默认OptiStruct炮弹的主要区别是钻井刚度缺席。稳定条款和其他一些调整，增加了可靠的性能。由此产生的元素通常比默认OptiStruct壳单元灵活，特别是在弯曲的几何形状。
【6】Is OptiStruct benchmarked?
OptiStruct finite elements are benchmarked with the MacNeal-Harder tests, NAFEMS benchmarks, and some other problems posted by individuals and companies.
The NAFEMS benchmark problems and results are documented in the OptiStruct manual.
【6】是OptiStruct基准？
OptiStruct有限元素基准与MacNeal -哈德测试，NAFEMS基准，以及其他一些问题，由个人和企业发布。
该NAFEMS基准问题和结果都记录在OptiStruct手册。
二、Optimization Problem Set Up
【7】What is the difference between volumefrac response and volume response?
Volumefrac response is the material fraction of the designable material volume. The volume response is the total volume, which includes design and non-design volume.
【8】Is minimizing mass identical to minimizing volume in OptiStruct?
Both formulations are identical as long as the same density ρρ is used for all materials in the model. When minimizing the volume, the density value in the material card does not have to be given.
If different densities ρρ exist in the design and the non-design space, then the optimization result may be different for minimizing mass and minimizing volume.
In a case where the design mass and the non-design mass are almost identical, but the design volume is much smaller than the non-design volume (Vdesign << Vnon-design), minimizing mass will give better results.
On the other hand, when the design volume and the non-design volume are almost identical, but the design mass is much smaller than the non-design mass (ρρdesign << ρρnon-design), minimizing volume will yield better results.
【9】Is there a way I can control the step size of the optimization?
You can change the move limits (the allowable change of the design variable in each iteration step) for the first iteration. The move limits are defined for each optimization type differently. The parameters are DELTOP, DELSHP, DELSIZ on the DOPTPRM statement. They can also be defined for size and shape variables on the DESVARcard.
In HyperMesh, use the opti control subpanel in the optimization panel on the Analysis page
【10】What is the procedure for restarting an OptiStruct job?
To restart an OptiStruct job, two files are needed: filename.fem (containing input data) and filename.sh (containing design variable information from the end of last complete iteration).
Please refer to Restarting OptiStruct in the Orientation and Fundamentals/Running OptiStruct section of the documentation.
【11】Is it possible to obtain rib pattern information on shell models using topology optimization?
Yes, but in order to do this, you must define the topology optimization problem differently.
Instead of defining the complete thickness of the shell element as designable, a core non-designable thickness, T0, must be provided in addition to a maximum thickness, T, which includes the core thickness and a designable region (where the ribs can be grown). The topology optimization can then be performed as usual.
The rib patterns can be interpreted by visualization of the density contour plots. Wherever the density values reach 1.0, a rib with the height of the -core plus the designable thickness is needed. Where the density values go to 0.0, no rib is required and it just retains the core thickness.
Example:
Component minimum core thickness: 1.5 mm
max thickness with ribs: 3.5 mm
The thickness on the PSHELL card is set to 3.5 mm and T0 on the DTPL card is set to 1.5.
This can lead to 2mm high ribs (max).
Note:
T0 is the mid-layer thickness. Ribs are placed within [ (T0/2) + (T/2) ] and [ (-T0/2) - (T/2) ] about the shell model, (i.e. the shell model coincides with the mid-plane of the elements).
Since shell elements are being used, the aspect ratio has to be taken into account. Do not let the expected thickness be greater than the in-plane dimensions of the elements.
【12】How can I assign and/or change the modeweights in a subcase (load case)?
Modeweights are assigned from within a model analysis subcase using the MODEWEIGHT subcase information entry.
From within the HyperMesh panels, access the optimization panel and the responses subpanel. If the wfreq or comb is chosen as the "response type," you can assign up to six modeweights to six different modes.
【13】How do I calculate the NORM factor for a combined compliance and frequency optimization problem?
【14】If the value of the subcase information entry NORM is left as 0.0 (default), then the normalization factor is estimated during the zero-th (analysis only) iteration of the optimization run (such that the static compliance and weighted frequencies are equally weighted). If you provide a value other than 0.0, that value will be used in the optimization. In HyperMesh, the value of NORM may be defined in the response panel when the "response type" is comb.
The normalization factor (NORM) is used for normalizing the contributions of static load case compliances and the inverse of eigenvalues when using the combined compliance index as the objective function. A typical structural compliance value is on the order of 1.e4 to 1.e6. However, a typical inverse eigenvalue, as in the case of using the combined compliance index as the objective function, is on the order of 1.e-5. If NF is not used, the linear static compliance requirements dominate the solution. Please refer to the Responses page of the User's Guide section of the documentation for more information on the "Combined Compliance Index" and the use of the NORM value.
【15】What is the difference between specifying a constraint on the designable volume and minimizing the designable volume?
In the first method, you can tell OptiStruct to use only a certain fraction of the designable volume (i.e. constraining the volume). OptiStruct will redistribute and reorient the amount of the material within the design domain while optimizing the objective function and satisfying any other constraints specified.
In the second method, you can choose their objective to minimize the volume. Here, OptiStruct will minimize the volume to arrive at a final topology that satisfies other constraints.
【16】What is the difference between using forces and prescribed displacements?
In order to increase stiffness, minimize compliance should be used with forces and maximize compliance with prescribed displacements.
The compliance is defined as:
Compliance ~ Force ? Displacement
When prescribed displacements are used, the reaction force must be increased to increase the stiffness. This means that the compliance has to be maximized.
In case the forces are given, a stiffer structure means having lower displacements. To achieve this goal, the compliance needs to be minimized.
【17】What is the initial value of material fraction at the beginning of an optimization run (iteration 0)?
If the objective of the design problem is to minimize volume response or mass response, the initial material fraction will be set to 0.9 by default. If a mass or volume constraint is used in the design problem, the initial material fraction will be the value corresponding to the value defined on the constraint. When mass or volume response is not being used to define the objective or the constraint, the material fraction will default to 0.6 at iteration 0.
【18】How can I assign material fraction to 1 at iteration 0?
The initial volume fraction can be assigned to 1.0 (or any other value between 0.0 and 1.0) by defining the MATINIT parameter on the DOPTPRM bulk data entry. This can be done from the HyperMesh interface by changing the value of the MATINIT parameter and checking the corresponding check box in the opti control subpanel, under the optimization panel (located on the Analysis page).
【19】Can I combine various optimization types (size with shape and/or topography)?
Yes, any type of combined optimization can be performed with OptiStruct. It is recommended, however, that different types of optimization be performed separately first. This will help you understand the performance of the structure with different kinds of optimization before attempting a combined optimization.
To set up an optimization problem using more than one optimization type, access the optimization panel and choose the subpanels for the optimization types to be performed (topology, topography, size and/or shape). If more than one subpanel is chosen in the optimization panel, (both topology and topography, for example) OptiStruct will automatically perform the combined optimization.
For details on setting up different types of optimization, please refer to the tutorial section of the manual.
【20】The results of iteration 0 in an attempted topology optimization are different from the results of a run with ANALYSIS. What is wrong?
Nothing is wrong. You have defined a design space for your topology optimization. In an analysis-only run, the density of the design space is set to 1.0. In the first iteration of the topology optimization, the density of the design space is less than 1.0, unless you have expressly set the MATINIT value, defined on the DOPTPRM bulk data entry, to 1.0. Therefore, in the first iteration, the structure appears to be not as stiff as in an analysis-only run.
For topology optimization runs with mass (volume) as the objective, the default for MATINIT is 0.9. For runs with constrained mass (volume), the default is reset to the constraint value. If mass (volume) is not the objective function and is not constrained, the default is 0.6.
To perform an analysis only run with the modal parameters set to the values that will be used for the first optimization iteration, do not use the ANALYSIS command, and set MAXITER = 0.
【21】How can I follow the iteration history while OptiStruct is running?
You can open the iteration history file .hgdata using Altair HyperGraph (or HyperView) while OptiStruct is still running and create plots of the Objective, Constraints, and Design Variables against Iteration. Using the ‘Apply’ button on the Edit Curves panel, the view can be updated periodically.
【22】Can I use stress constraints with topology or free-size optimization?
Von Mises stress constraints may be defined for topology and free-size optimization through the STRESS optional continuation line on the DTPL or the DSIZE card. There are a number of restrictions with this constraint:
?
The definition of stress constraints is limited to a single von Mises permissible stress. The phenomenon of singular topology is pronounced when different materials with different permissible stresses exist in a structure. Singular topology refers to the problem associated with the conditional nature of stress constraints, i.e. the stress constraint of an element disappears when the element vanishes. This creates another problem in that a huge number of reduced problems exist with solutions that cannot usually be found by a gradient-based optimizer in the full design space.
?
Stress constraints for a partial domain of the structure are not allowed because they often create an ill-posed optimization problem since elimination of the partial domain would remove all stress constraints. Consequently, the stress constraint applies to the entire model when active, including both design and non-design regions, and stress constraint settings must be identical for all DSIZE and DTPL cards.
?
The capability has built-in intelligence to filter out artificial stress concentrations around point loads and point boundary conditions. Stress concentrations due to boundary geometry are also filtered to some extent as they can be improved more effectively with local shape optimization.
?
Due to the large number of elements with active stress constraints, no element stress report is given in the table of retained constraints in the .out file. The iterative history of the stress state of the model can be viewed in HyperView or HyperMesh.
?
Stress constraints do not apply to 1-D elements.
【23】Can I use buckling constraints on a topology or free-size optimization?
There are several barriers for buckling constraints in topology optimization:
1.
Buckling constraints are conditional, similar to stress constraints (see Can I use stress constraints with topology or free-size optimization? ). Structural instability does not exist when structural parts vanish. This results in the phenomenon of "singular topology," where sudden changes of the feasible design domain occur when the density of a design element approaches zero. Gradient based optimization algorithms cannot overcome this barrier. For example, structural stability might be most critical around an opening in a panel. Instead of removing material from the boundary to improve the shape of the opening, the optimization process usually tends to try to add material to the boundary to improve the stability. This prevents the finding of more meaningful topology and shape.
2.
Although low density material might have very little impact to structural stiffness, it can significantly impact the buckling load limits; often times a small amount of lateral support can significantly improve structural stability.
3.
Buckling modes in vanishing areas (low density zones) have no implication to the structural integrity. How to effectively filter out these buckling modes remains another challenging task for buckling constraints.
Because of the above reasons, for the time being, reasonable success can only be expected for one class of design problems -- shell structures with non-zero base thickness.
【24】Is there a way to find the rigid body modes in a model?
In order to find the rigid body modes, you can add a diagnostic command OSDIAG,46,1 to the I/O options or subcase information sections of the OptiStruct deck. The diagnostic command will output the dofs that are constrained and provide the rigid body mode results to the user.
【25】Can volume or mass be defined as a response for topography optimization?
The sensitivities of volume are so low for topography optimization that they do not make a significant contribution toward the optimization. It is recommended that using both volume and mass as responses be avoided.
【25】How can the same response from different loadsteps be added together?
This can be achieved through the use of DEQATN, DRESP2, and DRESP1L cards. A DEQATN is defined to sum a number or responses. This DEQATN is referenced on a DRESP2 definition, which uses the DRESP1L continuation to select the same DRESP1 response for a number of different subcases.
Within HyperMesh, this can be achieved by first defining a dequation. Then, in the response panel, you select function as the response type, select the already-defined dequation, click edit, select Responses_by_loadstep from the available options, and select the same response for a number of different loadsteps.
For example, consider a control arm with three loadsteps. The control arm consists of two components; one of which is designable. It is necessary to add the regional compliance of the designable component for three loadsteps together, and then minimize the resulting compliance. The constraint on the volume fraction is not to be more than 0.1. A section of the input file is shown below:
$
$ OBJECTIVES Data
$
$
$HMNAME OBJECTIVES 2objective
$
DESOBJ(MIN)=5
$
$
DESGLB 9
$
$
$HMNAME LOADSTEPS 1brake
$
SUBCASE 1
SPC = 1
LOAD = 2
$
$HMNAME LOADSTEPS 2corner
$
SUBCASE 2
SPC = 1
LOAD = 3
$
$HMNAME LOADSTEPS 3pothole
$
SUBCASE 3
SPC = 1
LOAD = 4
$
BEGIN BULK
$HMNAME DESVARS 1topo_arm
$TPL 1 0.0 0.0 1 1 14
$
$ OPTIRESPONSES Data
$
DRESP1 3 comp COMP PSOLID 14
DRESP2 5 wcomp 1
+ DRESP1L 3 1 3 2 3 3
DRESP1 9 vol VOLFRAC
$
$HMNAME DEQUATIONS 1eq1
$
DEQATN 1 f(a,b,c)=a+b+c
$
$
$ OPTICONSTRAINTS Data
$
$
$HMNAME OPTICONSTRAINTS 8vol
$
DCONSTR 8 9 0.1
DCONADD 9 8
7】volumefrac之间有什么反应和体积响应的差异？
Volumefrac反应是材料的可设计的材料体积分数。该卷的反应是总量，其中包括设计和非设计量。
【8】为最大限度地减少群众在OptiStruct相同体积最小？
只要这两个配方是相同的密度相同ρρ是在模型中的所有材料。当最小的体积，在材料卡密度值不必须给。
如果不同密度ρρ存在于设计和非设计空间，那么优化的结果可能是减少质量和体积最小化不同。
在这样的情况：设计质量和非设计质量几乎相同，但设计体积比非设计量（Vdesign <
方案
气瓶 现场处置方案 .pdf气瓶 现场处置方案 .doc见习基地管理方案.doc关于群访事件的化解方案建筑工地扬尘治理专项方案下载
。请参阅更多关于“联合履约指数”和利用价值的规范到用户的指南中的文档部分的响应页面。
【15】什么是一间指定的可设计的体积最小化设计性约束和体积的差异？
在第一种方法，你可以告诉OptiStruct使用的可设计一定的体积只有一小部分（即数量限制）。 OptiStruct将重新分配和重新调整设计领域内的材料的数量，同时优化的目标函数和满足任何
规定
关于下班后关闭电源的规定党章中关于入党时间的规定公务员考核规定下载规定办法文件下载宁波关于闷顶的规定
的其他限制。
在第二种方法中，你可以选择自己的目标，以减少音量。在这里，OptiStruct量将减少到一个最终的拓扑结构，满足其他方面的限制。
【16】使用之间有什么区别力和位移的规定？
为了增加刚度，减少应遵守部队使用，最大限度地遵守既定的位移。
合规的定义为：
?力?遵守位移
当使用规定的位移，反应力，必须增加，以增加硬度。这意味着要遵守最大化。
如果给出的力量，更硬的结构是指具有较低的位移。为了实现这一目标，必须遵守最小化。
【17】什么是物质的一小部分在优化运行（迭代0）开始的初始值？
如果设计问题的目的是降低音量反应或一呼百应，最初材料部分将被设定为0.9默认情况下。如果质量或体积的限制，是在设计中使用的问题，最初的材料比例将相应的值上的约束定义的值。在质量或体积的反应不是被用来定义目标或约束，材料部分将默认为0.6迭代0。
【18】我该如何分配到一小部分材料在迭代0？
初始体积分数可以分配到1.0（或任何其他值0.0和1.0）的定义上的DOPTPRM批量数据输入MATINIT参数。这可从HyperMesh界面改变的MATINIT参数值，并检查控制子面板的Opti中相应的复选框下的优化面板（在分析页面中）。
【19】我可以把（形状和/或地形大小）各种优化类型？
是的，任何类型的优化组合就可以执行OptiStruct。这是建议，但是，不同类型的优化进行单独第一。这将帮助你了解一个优化组合，再尝试了不同类型与结构性能的优化。
要建立一个优化问题，使用一个以上的优化类型，访问优化面板和类型的优化选择要执行的子面板（拓扑，地形，尺寸和/或形状）。如果有多个子面板面板是在优化选择，（包括拓扑结构和地形，例如）OptiStruct将自动执行组合的优化。
有关设置不同的优化类型的详情，请参阅本手册教程部分。
【20】在试图拓扑优化迭代0的结果是从一个不同的运行结果分析。什么是错的？
什么是错的。您已定义为您的拓扑结构优化的设计空间。在分析中仅运行，设计的空间密度设置为1.0。在第一次迭代拓扑优化，设计的空间密度小于1.0，除非你有明确规定的MATINIT值，定义在DOPTPRM批量数据录入，为1.0。因此，在第一次迭代，结构似乎并不如分析，只运行僵硬。
与群众的拓扑优化运行（卷）为目标，对MATINIT默认为0.9。对于约束质量（体积）运行时，将重置为默认值约束。如果质量（体积）不是目标函数和不限制，默认为0.6。
只执行设置为将要第一个优化迭代中使用的值的模态参数运行分析，不要使用分析命令，并设置MAXITER = 0。
【21】我怎样才能按照迭代历史，同时OptiStruct运行？
您可以打开迭代历史文件。hgdata使用牵牛星超图（或HyperView），而OptiStruct仍在运行，创造了对迭代目标，约束和设计变量的阴谋。使用'应用'在编辑曲线面板按钮，可以查看定期更新。
【22】我可以用拓扑或自由尺寸优化应力约束？
冯米塞斯应力约束可能被定义为拓扑和自由尺寸优化，通过重音在DTPL或DSIZE卡可选的续行。有一个与此约束限制：
?在应力约束的定义仅限于一个单一的冯米塞斯容许应力。拓扑结构的奇异现象是明显不同的许可时，强调存在于不同材料的结构。奇异的拓扑结构是指与应力约束条件的性质有关的问题，即元素的应力约束因素消失后消失。这将创建另外一个问题，就是一个庞大的数目减少的问题，不能与通常可以通过在整个设计空间梯度为基础的优化器找到解决方案存在。
一个局部的结构域?压力约束不允许的，因为他们往往因为创造了一个局部的区域消除病态的优化问题将消除所有的压力的限制。因此，应力约束适用于整个模型活动时，包括设计与非设计区，应力约束的设置必须为所有DSIZE和DTPL卡相同。
?该功能已内置的智能过滤掉点左右点载荷和边界条件的人工应力集中。由于应力集中的几何边界，也过滤了一些，因为他们可以改善，局部形状更有效地优化程度。
?由于配备有效应力约束大量元素，没有元素应力报告中给出了保留限制表中。出的文件。该模型的应力状态迭代的历史可以被视为在HyperView或Hypermesh。
?压力限制并不适用于一维元素。
【23】我可以用屈曲的拓扑结构或自由尺寸优化约束？
有屈曲约束拓扑优化中的几个障碍：
1。屈曲约束条件，类似应力约束（见我可以免费使用的拓扑结构或大小的优化应力约束？）。不存在结构性不稳定结构件时消失。在“奇异的拓扑结构，”那里的可行设计领域突然发生变化时，设计元素密度趋近于零的现象，这结果。基于梯度的优化算法无法克服这一障碍。例如，结构稳定性可能是最围绕在面板开放的关键。而不是清除从边界，以提高开放型材料，优化过程通常倾向于尝试添加材料的边界，以改善其稳定性。这可以防止更多的有意义的拓扑结构和形状的发现。
2。虽然低密度材料可能只有很少的影响，结构刚度，它可以显着影响的屈曲载荷的限制，往往次少量的横向支撑可显着提高结构稳定性。
3。在消失的地方屈曲模式（低密度区）没有意义的结构完整性。如何有效地过滤掉这些屈曲模态屈曲约束依然是富有挑战性的任务。
由于上述原因暂时，合理的预期的成功只能是一类问题的设计 - 与非零基厚壳结构。
【24】有没有办法找到一个模型刚体模式？
为了找到刚体模式，您可以添加一个诊断命令OSDIAG，46,1到I / O选项或OptiStruct甲板子用例的信息部分。该诊断命令将输出的是约束和刚体模式提供给用户的结果自由度。
【25】可体积或质量被定义为一个优化的地形反应？
销量的灵敏度是如此的地形优化，但他们没有一对优化重大贡献低。建议同时使用体积和质量作为反应是可以避免的。
【25】如何从不同的loadsteps同样的反应加在一起？
要做到这一点通过DEQATN，DRESP2和DRESP1L卡的使用。阿DEQATN被定义为一个数字的总和或响应。这DEQATN引用一个DRESP2定义，它使用DRESP1L继续选择相同的不同subcases数DRESP1反应。
在HyperMesh，能做到这一点，首先定义一个dequation。然后，在响应面板，您选择的响应类型的功能，选择已定义的dequation，单击编辑，然后从可用选项Responses_by_loadstep，并选择不同loadsteps数目相同的反应。
例如，考虑有三个loadsteps控制臂。控制臂由两部分组成，其中之一是可设计。要添加组件的可设计的区域遵守三个loadsteps在一起，然后最小化所产生的遵守情况。体积分数上的限制是不超过0.1。一个输入文件的部分如下所示：
三、Post-processing and Result Output
【1】In the analysis results output, what exactly is the shear angle?
The shear angle is the angle between the element’s horizontal axis and the major principle direction (in the principle co-ordinates as used for a Mohr circle). The shear angle is derived from the in-plane normal and shear stresses.
【2】How can SPC forces be output as a result?
Use the SPCFORCE command in the I/O options section of the input data.
With this command, loads are written to the .spcf file, an ASCII format results file. Loads are also written to the binary .res and .h3d files (if these formats are selected) and these result formats can be viewed graphically. Additionally, if the .spcf file is written, the reaction force summary, the load summary, and the strain energy residuals for each load case are written to the .out file.
For more information, refer to the SPCFORCE entry in the Reference Guide section of the documentation.
【3】Why doesn't the converged optimization result I obtain contain elements with high density values (0.7 ~ 1.0)?
Some of the most common causes of this result are:
1.
The optimization has not converged. The process has stopped because the optimization has reached the iteration limit. Please increase the iteration limit and restart the run.
2.
A huge design space has been given. This situation is normally found in the area of minimize mass or volume response.
3.
Not enough mass or volume has been given to the design problem. This situation is normally found in a design problem in which the mass or volume response is used as a constraint. Please increase the mass or volume fraction value in the constraint.
In addition, the DISCRETE parameter on the DOPTPRM bulk data entry, found in HyperMesh under opti control in the optimization panel, can be used to increase the penalization factor and force densities to go to either 0 or 1.
【4】Why do I still have a huge constraint violation percentage even if the output file indicates that the optimization has converged?
In general, optimization is only considered converged if the constraint violation percentage is zero (or at a very low value). Convergence at huge constraint violations occurs when the given constraints in the design problem are too tight or the design problem is so ill-defined that the design problem cannot be further improved. Thus, the change of design objective falls below the convergence criteria that the user has defined and the optimization process ends.
【5】Can I export the DVGRID information from a topography optimization?
Yes, add OSDIAG, 81, 5 to the top of your deck. This will export the DESVAR and DVGRID information generated from the DTPG cards to the .out file.
【5.5】Is it possible to reduce the file size of the iges surface generated by OSSmooth?
There are two ways to avoid having huge iges surface file sizes:
1.
Set the surface_reduction parameter to 1 in order to reduce the number of surfaces created.
2.
Use minimum member size control to obtain a more discrete structure. This way, you will get a smaller iges file when using the surface_reduction parameter.
【6】How do I obtain stress/force results for 1-D elements?
For CBAR/CBEAM elements, normal stress at the cross-section origin is output by default, and is controlled by the STRESS I/O option. If stress results are desired for other locations, the first continuation line for the PBAR/PBEAM definition is required. The maximum stress calculated at any of the four allowable stress recovery locations is then reported as the element's axial stress.
Sectional forces and moments for 1-D elements can be obtained through the FORCE I/O option. If FORCE=YES is added to the I/O options section of the input deck, the .force file is output containing force and moment results.
【7】Why are some parts of the model missing when OSSmooth is used to recover geometry?
This can be attributed to the presence of local coordinate systems. The following steps offer a solution:
1.
Import the model into HyperMesh.
2.
Click on Systems and reassign all elements to the global coordinate system.
3.
Delete the local coordinate systems.
4.
Export the file and save with a new file name.
5.
Rename the shape file created during the optimization with the same name used in the previous step.
6.
Run OSSmooth
三，后处理和结果输出
【1在分析结果输出】，究竟是什么剪角？
剪切角之间的元素的水平轴和主要原则方向角（在原则协调莫尔圆为一个使用）。剪切角是来自于平面和切应力。
【2】如何才能最高人民法院部队作为结果输出？
使用SPCFORCE在I / O选项，输入的数据部分命令。
使用此命令，加载被写入。spcf文件，以ASCII
格式
pdf格式笔记格式下载页码格式下载公文格式下载简报格式下载
的结果文件。负荷也将被写入二进制。水库和。话，H3D文件（如果这些格式被选中），这些结果的格式可以被视为图形。此外，如果。spcf文件写入，反应力总结，负载总结，并为每个负载情况下的应变能残差写入。出的文件。
欲了解更多信息，请参阅SPCFORCE在参考指南中的文档部分条目。
【3】为什么不融合的优化结果，我获得含有高密度值元素（0.7?1.0）？
对这个结果最常见的原因有：
1。该优化并没有收敛。这一进程已经停止，因为已经达到了优化迭代限制。请增加迭代限制，并重新启动运行。
2。一个巨大的设计空间已发出。这种情况通常是发现在质量或体积最小响应区域。
3。没有足够的质量或数量已经考虑到设计问题。这种情况通常是在设计中发现的问题，因为质量或体积响应作为约束使用。请增加质量或体积分数值约束。
此外，对DOPTPRM批量数据输入离散参数，在HyperMesh下找到在优化面板opti控制，可以用来增加密度惩罚因素和力量去为0或1。
【4】为什么我仍然有一个巨大的约束违规的百分比，即使输出文件表明，该优化已经收敛？
在一般情况下，优化融合，如果只考虑约束违规率是零（或在一个非常低的值）。在巨大的约束冲突发生时的收敛性问题在给定的设计约束太紧或设计问题是如此的不明确，设计问题不能得到进一步改善。因此，设计目标的变化属于该用户已定义和优化过程结束低于趋同标准。
【5】我可以从一个出口形貌优化DVGRID信息？
是，新增OSDIAG，81，5到你的甲板上。这将出口DESVAR和DVGRID信息从生成到DTPG卡。出的文件。
【5.5】是有可能减少IGES文件大小表面OSSmooth产生的？
有两种方法，以避免表面有巨大的IGES文件大小：
1。 surface_reduction参数设置，以1至减少创建面数。
2。使用最小成员的大小控制，使结构更加离散。这样，你会得到一个较小的IGES文件时使用surface_reduction参数。
【6】如何获得一维单元的应力/力的结果吗？
对于CBAR / CBEAM元素，在横截面正应力的起源是默认输出，是由I / O选项应力控制。如果强调结果对其他地方需要，为PBAR / PBEAM定义的第一续行是必需的。最大应力在四个容许应力恢复任何位置，然后计算出报告为元素的轴向压力。
分力量，为一维元素的时刻，可通过原力的I / O选项。如果力= yes是添加到I / O选项输入的甲板部分，。力量输出文件包含力和力矩的结果。
【7】为什么失踪人员时OSSmooth用于恢复几何模型的某些部分？
这可能是由于局部坐标系统的存在。下面的步骤提供了一个解决方案：
1。导入到HyperMesh模型。
2。点击系统和重新分配的所有元素，全球坐标系统。
3。删除本地坐标系统。
4。导出该文件并保存新的文件名。
5。重命名文件的过程中创建的形状与在上一步中使用的相同名称的优化。
6。运行OSSmooth
四、Error Messages
【1】What does ERROR #4720 "Invalid static SUBCASE that has no load or enforced displacement" mean?
It means that either a load or boundary constraint has not been defined in a subcase (loadstep) in the OptiStruct input deck.
In HyperMesh, the subcase can be defined using the subcase panel. While in the subcase panel, give a name to the subcase, choose the load collectors to be used for constraints, loads, method, etc., click on return, and then click on create.
【2】Why do I get the error message "out of environment space?"
The environment space required to run OptiStruct from within HyperMesh (both at the same time) is more than 8196 bytes. Increase the memory allocated to environment space to 16392 bytes by adding/modifying the following command in the config.sys:
SHELL= C:\COMMAND.COM /e:16392
For Windows 98, the above command should be change to:
SHELL= C:\COMMAND.COM /p /e:16392
The machine must be re-booted for any changes in the config.sys to take effect.
四，错误消息
【1】什么错误＃4720“无效的静态子用例是没有加载或被迫流离失所”是什么意思？
这意味着，无论是负载或边界的约束并没有被输入在OptiStruct甲板子用例（loadstep）来界定。
在HyperMesh，可以定义的子用例的子用例用面板。而在子用例面板，给人的子用例的名称，选择要加载收藏的约束，载荷，方法等，在返回点击使用，然后点击创建。
【2】为什么我得到错误信息“的环境空间不足？”
所需的空间环境内运行HyperMesh OptiStruct（都在同一时间）超过8196字节。通过增加对环境的空间分配到16392个字节的内存/修改在CONFIG.SYS以下命令：
壳= C的：\ COMMAND.COM / E的：16392
对于Windows 98，上面的命令应改为：
壳= C的：\ COMMAND.COM /的P / E：16392
本机必须重新启动在CONFIG.SYS中的任何更改生效。
RADIOSS (Block Format)
一、Running RADIOSS
【1】How to chain several runs one after each other, automatically?
You can chain several runs one after each other by creating a script file with all the commands to execute; when executing the script, these commands will execute one after each other.
In case of a UNIX or LINUX system, write on the first line of a file:
#! /bin/csh
This means that this script will be read by the csh interpreter. Then write the commands for running the computations.
Below is an example of a so-called “my_script” script file.
【2】How can I check the RADIOSS version which was used for a run?
Check the RADIOSS version used in the listing file (Runname_0000.out from v9 or higher; Runname_0000.lis in v5; RunnameL00 in v4) for RADIOSS Starter and in the listing file (Runname_nnnn.out from v9 or higher; Runname_nnnn.lis in v5; RunnameLnn in v4) for RADIOSS Engine.
In the header of these files, the RADIOSS version used, few key hints on hardware and the parallelism type are mentioned.
Example:
【3】How can I set the number of processors for a run?
For RADIOSS SPMD
The number of processors has to be defined in the RADIOSS Starter input (Runname_0000.rad or RunnameD00) with the option /SPMD. It is used by RADIOSS Starter for the "Domain Decomposition".
The same number of processors has to be input as a MPI parameter when you launch RADIOSS Engine.
For RADIOSS SMP
This is done by defining the environment variable OMP_NUM_THREADS.
The way to initialize this environment variable differs with shell interpreter:
In csh mode:
setenv ENVIRONMENT_VARIABLE [N]
In bash, ksh mode:
export ENVIRONMENT_VARIABLE=[N]
Refer to the HyperWorks Installation documentation for more explanation.
Another way (old one) is to add in the Engine input file the line /PROC/N.
If both the environment variable and /PROC/N are used, the value accounted for is the minimum one.
Check if the number of processor is correctly set by looking at the RADIOSS Engine display (standard output or listing file (Runname_0001.out, Runname_0001.lis or RunnameLnn):
【4】What should I do if the Starter stops with the following message: OUT OF SPACE IN DOMAIN DECOMPOSITION?
OUT OF SPACE IN DOMAIN DECOMPOSITION
(8) PLEASE INCREASE MEMORY FOR THE DOMAIN DECOMPOSITION
This message means that RADIOSS Starter is not able to process domain decomposition with the default amount of memory allocated (SPMD computation).
The needed memory is computed by RADIOSS Starter before the model decomposition. In most cases it is enough; but in the case of complex meshes and a lot of connectivity (for example: a model with a lot of solid elements), this memory allocation has to be increased.
This can be done by setting the Dkword value in the 4th field of the option /SPMD:
【5】What should I do if the Engine stops with the following message: ** ERROR IN OPENING INPUT FILE?
** ERROR IN OPENING INPUT FILE
This message appears if:
?
if RADIOSS Engine input file in version 44 (RunnameD01) contains the keyword /VERS/51
?
if RADIOSS Engine input file in version 51 (or higher) (Runname_run#.rad) contains the keyword /VERS/44.
【】How to set stacksize for running RADIOSS
Before running RADIOSS it is important to properly define the amount of stacksize memory.
Under Linux and Unix, stacksize must be defined as unlimited.
?
Using csh:
limit stacksize unlimited
?
Using sh:
ulimit –s unlimited
Additionally, in case of running RADIOSS SMP with more than one thread (OMP_NUM_THREADS greater than one), it is important to define an additional environment variable KMP_STACKSIZE, which defines the per thread stacksize.
Under Linux and Unix, the recommended value is 512 Mbytes.
?
Using csh:
setenv KMP_STACKSIZE 512m
?
Using sh:
export KMP_STACKSIZE=512m
Under Windows, the recommended value is 64 Mbytes.
1.
Click on start\Settings\Control_Panel\System\Advanced\Environment_Variables\ System_Variables\New.
2.
Define a new Variable KMP_STACKSIZE with Value 64m.
3.
Double-click the OK button to validate your modification.
Then, any new shell running RADIOSS will have the environment variable KMP_STACKSIZE defined to 64m.
Below is a summary of the recommended values automatically set by HyperWorks when running RADIOSS from a standard HyperWorks installation:
Variable
Stacksize
KMP_STACKSIZE
Windows
N/A
64m
Linux / Unix
unlimited
512m
一，运行RADIOSS
【1】如何链多次运行后对方一，自动？
您可以多次运行后，每个连锁通过创建一个有所有命令的脚本文件来执行其他一，当执行该脚本，将执行这些命令后，对方一。
在UNIX或Linux系统的情况下，写在一个文件的第一行：
＃！ /宾/ csh的
这意味着，这个脚本将被解释器读取的csh。然后写出计算运行的命令。
下面是一个所谓的“my_script”脚本文件的例子。
【2】我该如何检查RADIOSS版本是为运行使用？
检查（从v9或更高Runname_0000.out; Runname_0000.lis在V5; RunnameL00在v4）的版本的RADIOSS在列表文件中用于RADIOSS起动及在上市文件（Runname_nnnn.out从v9或更高; Runname_nnnn.lis在V5 ; RunnameLnn在4版）的RADIOSS引擎。
在这些文件头，RADIOSS版本中使用，对硬件和平行式几个关键提示提及。
例如：
【3】如何设置为运行的处理器数量？
对于RADIOSS半渗透膜采样
处理器的数量也将在RADIOSS起动输入与/半渗透膜采样选项（Runname_0000.rad或RunnameD00）来界定。这是首次使用RADIOSS为“区域分解”。
相同数量的处理器已经被视为一个MPI的参数，当您启动RADIOSS引擎输入。
对于RADIOSS的SMP
这是通过定义环境变量OMP_NUM_THREADS。
初始化的方法不同，这个环境变量与壳牌翻译：
在csh模式：
的setenv ENVIRONMENT_VARIABLE [N]的
在bash，ksh的模式：
出口ENVIRONMENT_VARIABLE = [N]的
请参考更多的解释HyperWorks的安装文档。
另一种方法（老一）是要增加引擎输入文件中的行/触发/全
如果这两个环境变量和/ proc / N的使用，货值占是最低之一。
检查是否正确的处理器数量由在RADIOSS引擎显示（标准输出或列表文件（Runname_0001.out，Runname_0001.lis或RunnameLnn）展望集：
【4】我应该怎么做，如果起动停止并显示以下消息：在太空中的区域分解？
出在空间域分解
（8）请为域分解增加记忆力
此消息意味着RADIOSS Starter是无法处理域与默认的内存分配（半渗透膜采样计算）金额分解。
计算所需的内存是由RADIOSS起动前的模型分解。在大多数情况下是足够的，但在情况复杂的网格和一个连接（例如：一个有坚实的很多因素模型）的东西，这种内存分配得增加。
这可以通过设置在选项/半渗透膜采样第四场Dkword值：
【5】我该怎么办，如果发动机停止并显示以下消息：**错误在开启输入文件？
**错误在开启输入文件
如果出现此消息：
?如果在版本44 RADIOSS引擎输入文件（RunnameD01）包含的关键字/ VERS/51
?如果RADIOSS引擎在版本51（或更高）（Runname_run＃。RAD）的输入文件包含的关键字/ VERS/44。
【】如何设置运行RADIOSS堆栈大小
运行前RADIOSS重要的是要正确定义堆栈大小的内存量。
在Linux和Unix下，堆栈大小必须定义为无限的。
?使用csh：
无限堆栈大小限制
?使用上海：
的ulimit - S的无限
此外，在运行多个线程（OMP_NUM_THREADS设置大于一）RADIOSS SMP的情况下，重要的是要定义一个额外的环境变量KMP_STACKSIZE，其中每个线程的堆栈大小定义。
在Linux和Unix中，推荐值是512兆字节。
?使用csh：
512M的的setenv KMP_STACKSIZE
?使用上海：
= 512M的出口KMP_STACKSIZE
在Windows下，推荐值是64兆字节。
1。点击开始\设置\的Control_Panel \系统\高级\ Environment_Variables \ System_Variables \新建。
2。定义一个新变量KMP_STACKSIZE价值6400万。
3。双击OK按钮来验证你的修改。
然后，任何新的shell中运行RADIOSS将有环境变量KMP_STACKSIZE定义为6400。
下面是HyperWorks的自动运行时设置HyperWorks的安装RADIOSS标准的推荐值的摘要：
变堆栈大小KMP_STACKSIZE
视窗? /阿6400
Linux / Unix的无限512M的
二、Parallelism
【1】What is the difference between RADIOSS SMP and RADIOSS SPMD?
SMP Version
SMP stands for Shared Memory Parallelism.
This version is based on shared memory architecture of computers.
For this kind of computer, all processors can access to a common memory space. Each process can access to all memory allocated by the program.
Shared memory architecture
Depending on the operating system, this version will be able to use up to 8, 12 or 16 processors with a reasonable efficiency. The efficiency can be considered as an acceptable one if it is greater than 50% (that is to say, the speedup is greater than half the number of processors).
SPMD Version
SPMD stands for “Single Program Multiple Data”.
RADIOSS Starter divides the model into several domains (equal to number of processors asked for).
Up to RADIOSS version 4:
The data is next sent to each process in RADIOSS Engine; this is the “Parallel Initialization”. The first process reads the complete RESTART file, sending the data to each other process.
Some additional memory is needed on first process for this operation in this version.
From RADIOSS version 5.1:
RADIOSS Starter writes as many RESTART files as the number of processes which will be used for the run. Each RESTART file is built from only the data that will be needed by the relative process, and is read directly by this process when running RADIOSS Engine. Additional memory is no longer needed for the “Parallel Initialization”.
Then each program executes on each domain. The management of computation at the frontiers of the domains remains and the necessity to communicate some information between the processes is implemented through the use of the MPI 'Message Passing Interface'.
This SPMD version is free from the computer architecture. It can run on distributed memory machines, shared memory machines, workstations cluster or high performance computation cluster.
With this version it is possible to use more processors than with the SMP version, with a better efficiency. It becomes possible to use more than 128 cores with a good speedup.
【2】What is the /PARITH/ON option?
The option “Parallel Arithmetic” is a strong point of RADIOSS. It is maintained for both RADIOSS SMP and SPMD versions.
It ensures the same results for a given RADIOSS release and architecture; regardless of the number of processors.
Indeed, differences in the order of treatments can result in some sensitivity of the results according to the number of processors used.
“Parallel Arithmetic” reduces sensitivity of Car Crash simulations, especially since these simulations naturally imply a lot of local buckling situations.
“Parallel Arithmetic” is not supported in case of “Incompatible Kinematic Conditions”.
二，平行
【1】之间有什么RADIOSS SMP和RADIOSS半渗透膜采样区别？
SMP版本
SMP的代表共享内存并行。
这个版本是基于计算机的共享内存架构。
对于这种类型的电脑，所有的处理器都可以访问公共的内存空间。每个进程可以进入该程序分配的所有内存。
共享内存架构
在不同的操作系统，这个版本将能够使用与合理的效率，8，12或16个处理器。效率可以被视为一个可以接受的一个，如果它大于50％（即，加速比大于一半的处理器数）。
半渗透膜采样版本
半渗透膜采样代表“单程序多数据。”
RADIOSS入门分成（等于处理器的数量要求）多个域模型。
截至RADIOSS版本4：
未来的数据发送到每个RADIOSS引擎进程，这是“并行初始化”。第一个进程读取完整的重新启动文件，发送数据到对方的过程。
需要一些额外的内存在第一次处理此在这个版本的操作。
从RADIOSS版本5.1：
RADIOSS首次写入尽可能多的重新启动，将在运行中使用的进程数量的文件。每次重新启动文件是建立只从将要由相对进程所需的数据，并读取该发动机运行时RADIOSS进程直接。额外的内存不再需要“并行初始化”。
然后每个程序执行的各个领域。的计算在该领域的前沿管理遗骸和沟通的必要性之间的一些进程的信息是通过的MPI，消息传递接口'加以实施。
这种半渗透膜采样版本是免费的计算机架构。它可以运行在分布式内存的机器，共享内存机，工作站或高性能集群计算集群。
有了这个版本，它可以使用比使用更多的处理器SMP版本具有更好的效率。就有可能使用了良好的加速超过128个核心。
【2】什么是/ PARITH / ON选项？
选项“并行算法”是一种RADIOSS的强项。这是保持两个RADIOSS SMP和半渗透膜采样版本。
它确保在给定RADIOSS释放和结构相同的结果，无论处理器的数量。
事实上，在处理顺序的差异可能会导致一些根据处理器的数量用于结果的敏感性。
“并行算法”减少汽车碰撞模拟的敏感性，特别是因为这些模拟自然意味着对局部屈曲的情况很多。
“并行算法”是不是在“不兼容的运动学条件”一案的支持。
三、RADIOSS Files
【1】What is the difference between the "Input format" and the RADIOSS version which is used?
The input format (41, 44, 51, 90, etc.) corresponds to the format of the RADIOSS input data file, whose name is RunnameD00 for input formats up to 44 or Runname_0000.rad for input formats coming from 51 or higher.
For input formats up to 44, the input format is declared at the first line of the Starter input file. This conforms to the version of the input manual.
For input formats from 51 onwards, the input format is declared in the keyword /BEGIN, which must be the first uncommented line after the line: “#RADIOSS Starter”.
For every new RADIOSS main release (41, 44, 51, 90, etc.), a new input manual is provided, which presents the characteristics of the new input format, and information on new keywords.
By ascending compatibility, a RunnamD00 or Runname_0000.rad file conforming to a given manual will be read normally by the next RADIOSS release (but not the opposite).
For instance, a file with format 41 will be read normally by version 44 of RADIOSS, while a file with format 42 can not be used with version 41. In this last case, an error message is given by RADIOSS Starter:
** ERROR IN INPUT FORMAT
INPUT VERSION 42 IS NOT SUPPORTED
三，RADIOSS文件
【1】什么是之间的“输入格式”和RADIOSS版本，这是用来区别？
输入格式（41，44，51，90，等）对应的RADIOSS输入数据文件，其名称RunnameD00输入格式高达44或Runname_0000.rad输入格式，从51或更高的未来格式。
对于高达44输入格式，输入格式是在宣布首次输入文件的第一行。这符合输入手动版本。
对于从51年起输入格式，输入格式是宣布在关键字/开始，这必须是第一个取消注释行之后行：“＃RADIOSS启动器”。
对于每一个新RADIOSS主要版本（41，44，51，90，等），提供新的输入手册，其中介绍了新的输入格式的特点，并在新的关键字信息。
通过提升兼容性，RunnamD00或Runname_0000.rad符合给定的文件将被读取手册通常由下RADIOSS版本（而不是相反）。
例如，一个格式41文件将被读取，通常由44个版本的RADIOSS，而有42文件格式不能与版本41中。在最后这种情况下，错误信息是给予RADIOSS入门：
**错误的输入格式
输入不支持42版
四、Restart
【1】I have a computation running; I would like to stop it after writing a RESTART file. Is this possible?
It is possible to do this by writing a control file in the same directory as the run data.
In case of a run number nnnn (/RUN/Runname/nnnn in the RADIOSS Engine input file), you have to creat a file called Runname_nnnn.ctl and write the following line in it:
/STOP
RADIOSS Engine ends and a RESTART file is written.
The others options available with control files are described in the Control File (C-File) section.
【2】What should I do if RADIOSS Engine does not start; it seems there is a problem with the RESTART file (Runname_0000_0000.rst)?
Check that the RESTART file Runname_0000_0000.rst (written by Starter) appears in the directory where RADIOSS Engine has been run.
If you receive the following type of message:
PGFIO-F-217/unformatted read/unit=21/attempt to read past end of file.
File name = CRA2_0000_0000.rst unformatted, sequential access record= 2
In source file /radiossb/v41/mot/For/comm/redsqi.F, at line number 51
In the RADIOSS Engine file (Runname_0001.rad), verify that the flag Iread in option /RFILE, which defines the reading format for file Runname_0000_0000.rst, correctly corresponds to the flag Irtyp of option /IOFLAG in Runname_0000.rad file; which defines the format of the Runname_0000_0000.rst file which was written by RADIOSS Starter.
/RFILE
NCYCLE IREAD IWRITE
/IOFLAG
IPRI
IRTYP IGTYP IOUTP
The different values correspond to:
0: default = 3
1: binary
2: ASCII 32 bits
3: IEEE
【3】Is it possible to write several RESTART files during the same run, without overwriting them each time?
You have to write the option /RFILE/n in the RADIOSS Engine input file Runname_run#.rad:
n refers to the number of different RESTART files that will be kept. The n RESTART files will get different names Runname_0001_0000_[C].rst1 with an extension using a letter: for e.g. the 1st RESTART file will be called Runname_0001_0000_I.rst; the 2nd RESTART file will be called Runname_0001_0000_J.rst and so on. The n+1th file will also be called Runname_0001_0000_I.rst and will overwrite the 1st file. This sequence is repeated.
It is possible to write up to 18 different RESTART files within the same run.
In order to restart from a file in the next run, you will have to specify in the Runname_run#.rad input file the next run, the letter defining the RESTART file into option /RUN.
For instance, for restarting with file Runname_0001_0000_J.rst:
/RUN/Runname/2/J
Reference
1
Let Runname_0001_cpu#_[C].rst for SPMD version, with cpu# varying from 1 to the number of processors which are used.
四，重新启动
【1】我有一个计算运行，我想停止后重新启动文件写它。这可能吗？
它可以通过编写的运行在相同的目录数据的控制文件中。
在运行数字nnnn（/运行/ Runname /在RADIOSS引擎输入文件分）的情况下，你必须创造一个文件名为Runname_nnnn.ctl写在它下面的行：
/停止
RADIOSS引擎结束，一重新启动文件被写入。
其他选项与控制文件中描述了可用的控制文件（C文件）部分。
【2】我应该怎么做，如果RADIOSS引擎无法启动，它似乎有一个重新启动文件（Runname_0000_0000.rst）问题？
检查重新启动文件Runname_0000_0000.rst（由起动书面）如RADIOSS发动机已经运行目录中。
如果您收到以下类型的消息：
PGFIO-F-217/unformatted读/单位= 21/attempt阅读文件的末端。
文件名= CRA2_0000_0000.rst格式化，顺序访问记录= 2
在源文件中的行号在第51 / radiossb/v41/mot/For/comm/redsqi.F，
在RADIOSS引擎文件（Runname_0001.rad），请确认在选项标志Iread /参考文件，它定义了文件Runname_0000_0000.rst阅读格式，正确对应于Runname_0000.rad文件选项/ IOFLAG旗Irtyp;定义该Runname_0000_0000.rst文件，该文件是由RADIOSS入门书写格式。
/参考文件
NCYCLE IREAD IWRITE
/ IOFLAG
IPRI IRTYP IGTYP IOUTP
不同的值对应于：
0：默认= 3
1：二进制
2：ASCII的32位
3：电机及电子学工程师联合会
【3】是有可能写在同一运行几个重启文件没有覆盖它们，每次？
你必须写在RADIOSS引擎输入文件Runname_run＃选项/参考文件/否拉德。：
N为不同的重启文件号码将被保留。的n重启文件将得到不同的名称Runname_0001_0000_ [中]与扩展rst1使用了一封信：。为了如第一重新启动文件将被称为Runname_0001_0000_I.rst;第二重新启动文件将被称为Runname_0001_0000_J.rst等。的n +1个文件也被称为Runname_0001_0000_I.rst，将覆盖一号文件。这个序列是重复的。
这是可能写出在同一运行18种不同重启文件。
为了重新启动从在下次运行文件时，您必须指定在Runname_run＃。拉德输入文件下运行，字母定义成选项重新启动文件/运行。
例如，对于文件Runname_0001_0000_J.rst重新启动：
/ RUN/Runname/2/J
参考
1设Runname_0001_cpu＃_研究[J]。为半渗透膜采样版本的RST，与CPU从1到不同处理器的数量是用＃。
五、Elements
【1】I used solid elements with ISMSTR=2 and /DT/BRICK/CST; but the run stopped with the message: "Zero or Negative Volume"; is this normal?
Ismstr =1, 2 and 3 are not available for the 8 integration points solids using formulations Isolid =12 and 112.
This means that these solids continue to use large strain formulation, and hence the following error message appears: "Zero or Negative Volume".
In order to use this small strain formulation with 8 integration points solid elements, use the HA8 solid formulation which is available as of RADIOSS version 44.
When using this formulation, set Isolid =14 with Inpts =222 (corresponding to Isolid =222 in input format 44). Also set Icpre =1 for elastic or visco-elastic material law, and Icpre =2 for elasto-plastic laws.
【2】I used solid elements and several integration points, and the Starter gives the following error message while the element seems to be well-defined: ** ERROR: ZERO OR NEGATIVE 3D SOLID VOLUME, is this normal?
【3】How many integration points should I use in the thickness of shell elements?
If only 1 integration point is used, a membrane only behavior will be obtained (except with law 1, up to version 44). Some materials, such as fabric, can justify such a choice (no bending strength).
In case of an elastic behavior, one gets the exact solution from 3 integration points – that is to say that the bending moments are exactly integrated through the thickness of the shell – and it is not necessary to use more integration points.
In case of a plastic behavior, the bending moments are not integrated exactly. Using more integration points, the solution becomes more accurate; so it is recommended to use 5 integration points.
【4】I am using material law 1, with 1 integration point through the thickness and still get bending moments; why?
Up to version 44, Material Law 1 for shells does not use integration points but switches to the global formulation (corresponding to N=0); whatever the number of integration points N is asked for.
So up to version 44, there is no way to use this material law with only 1 integration point and membrane only behavior.
workaround: use Material Law 2 with integration point and a huge value for the yield stress.
As of version 51, Material Law 1 for shells uses global formulation, except if one integration point is asked for in the property, then a membrane only behavior occurs. Note that this can explain some differences in the results between versions up to 44 and version 51.
【5】With shell elements using the same material law, but different types of properties (while keeping the same number of integration points), I do not get the same results; why?
The integration scheme which is used for property types 1 and 9 (relative to isotropic shells through the thickness) sets the integration points and weights in order to integrate exactly the bending moments in the elastic case (from 3 integration points since for 1 integration point, no bending moments are computed).
The integration scheme which is used for property types 10 and 11 is a step-by-step integration scheme and uses integration points at the center of each layer, and weights which correspond to the relative thickness of each layer. So the integration scheme is not the same one.
An error relatively important can occur in the elastic field, when there are a few layers or large differences on the thicknesses of the layers. One way to work around this problem is to subdivide the thicker layers. But it is generally not well-suited in case of modeling the failure of the layers.
【6】When is it better to use QEPH shells, instead of Belytschko shells?
QEPH shells are more accurate for elastic or elasto-plastic loads, whatever the loading type - quasi-static or dynamic; but they are not compatible with anisotropic and orthotropic material laws.
QEPH shells will give better results if the mesh is fine enough. In case of a coarse mesh, this formulation will be too stiff and some local buckling phenomena could be missed. In case of a coarse mesh, the Belytschko shells often give better results.
【7】I used solid elements and the run stopped before the end time, with the message: "Zero or Negative Volume". How do I solve this problem?
This happens when solid elements are very deformed and their characteristic length goes to 0. You may notice in the output file that before getting this error message, the time step of the element written into the message drops down.
In case of large strain formulation, the time step of an element goes to 0 when the element is compressed. In a mathematical way, the element can not reverse its orientation since its stiffness increases to an infinite value; but due to numerical accuracy, the element may go to reverse its orientation
五，元素
【1】我所用ISMSTR = 2和/药物疗法/砖/科委固体元素，但停止运行的消息：“零或负体积”，这是正常的吗？
Ismstr = 1，2和3不适用于8个积分点可使用固体制剂Isolid = 12和112。
这意味着这些固体继续使用大应变制定，因此，出现以下错误信息：“零或负体积。”
为了使用8积分点这个小应变实体单元的制定，使用HA8固体制剂可以被用来作为RADIOSS 44版本可用。
当使用这一提法，设置Inpts = 222 Isolid = 14（对应Isolid = 222输入格式44）。同时设置Icpre = 1弹性或粘弹性材料的法律，Icpre = 2弹塑性法律。
【2】我使用的固体元素和多种集成点，并首次提供了以下错误信息，而该元素似乎是明确的：**错误：零或负三维固体体积，这是正常的吗？
【3】有多少积分点，我应该用在壳单元的厚度？
如果只有1的结合点，是使用一种膜只行为将得到（除非法第1到版本44）。有些材料，如面料，可以证明这样的选择（无弯曲强度）。
在弹性行为的情况下，一会从3集成点的精确解 - 这是说，弯曲力矩是完全集成通过壳厚度 - 这是没有必要使用更多的集成点。
在一个塑料行为的情况下，弯矩不统一准确。使用更多的集成点，该解决方案更加准确，因此，建议用5集成点。
【4】我使用的材料法1，1通过结合点的厚度，仍然可以得到弯矩，为什么？
截至到版本44，物权法1弹不使用集成点，但切换到全球配方（对应到N = 0）;无论整合点数N是提出的要求。
因此，注册到版本44，有没有办法用只有1只的结合点和膜这种材料的法律行为。
解决方法：使用材料与集成法第2点和巨大的屈服应力值。
从版本51，物权法一贝壳了，除非使用一个结合点，是在全球制定的物业问，那么一种膜只的行为发生。请注意，这可以解释高达44和51版本中的一些版本之间的结果差异。
【5】与外壳使用相同的实体法内容，但不同种类物业（保持相同数量的积分点），我没有得到相同的结果，为什么？
的整合计划，为物业类型1和9（相对于通过壳的厚度各向同性），用于设置集成点和权重，以整合正是在弹性情况下，从3弯矩积分点（自1的结合点，没有弯矩计算）。
的整合计划，为物业类型使用的是10和11一步一步的集成方案，并使用在每一层的中央集成点，和重量分别对应于每个层的相对厚度。因此，集成方案是不一样的。
比较重要的一个错误可能发生在弹性方面，当有一个或数层的层厚度较大的差别。一种方法来解决此问题是厚层细分。但人们普遍尚未在建模的故障的情况下的层适合。
【6】什么时候最好使用QEPH炮弹，炮弹，而不是Belytschko？
QEPH炮弹是更多的弹性和弹塑性负载，准确的装载任何类型 - 准静态或动态的，但他们不与各向异性，正交异性材料的法律兼容。
QEPH炮弹将得到更好的结果，如果是足够细的网格。在一个粗网的情况下，这一提法会过于僵硬，一些局部屈曲现象可能被错过。在一个粗网的情况下，Belytschko炮弹经常得到更好的结果。
【7】我使用的固体元素和结束时间之前停止运行，与消息：“零或负体积。”我该如何解决这个问题？
这发生在固体元素非常变形，其特征长度变为0。您可能会注意到在输出文件之前收到此错误消息，到消息的元素的时间步长的书面滴下来。
在制定大应变的情况下，一个元素的时间步长变为0时，该元素被压缩。在数学方法，元素不能扭转其方向，因为它的硬度提高到一个无限的价值，但由于计算精度，该元素可能会扭转其方向
六、Materials/Rupture
【1】Which curve should I input in material law 36 in order to characterize a material?
【2】I use solid elements and εpmax in the corresponding material. After the criteria εpmax is reached, elements are not deleted; why?
Depending on the material law, the solid elements are not deleted after the criteria
pmax is reached (they do not appear as “deleted elements” in post-processors).
For Material Laws 2, 4 and 22, only the deviatoric part of the stress tensor is set to zero, the internal pressure of the solid is still computed.
On the other hand, for Material Laws 3, 23, 28 and 36 the solid elements are deleted when
pmax is reached.
六，材料/破裂
【1】我应该在哪个曲线资料法36条输入，以描述一个材料吗？
【2】我使用在相应的固体物质要素和εpmax。 εpmax后达到的标准，内容不会被删除，为什么？
实体法上的不同，固体元素是不会被删除后达到的标准Pmax的（他们不显示为“删除的元素”后处理器）。
对于材料法例第2，第4和22只偏应力张量的部分设置为零，固体内部的压力仍然计算。
另一方面，对于材料法规3，23，28和36条的固体元素被删除时，Pmax的就达到了。
七、Post-processing
【1】Using shell elements, I asked for strain Time History output (RunnameT01) and Animation files, but the values remain equal to zero; why?
The strain tensor is not computed by default; it must be asked for in the RADIOSS input file (Runname_0000.rad) by setting flag Istrain (flag to compute strains for post-processing) to 1 in option /DEF_SHELL or in the shell property set.
On the contrary, the strain tensor is always computed and available for Law 25 and Law 27.
【2】/ANIM/ELEM, BRICK or SHELL/EPSD & Variable EPSD for a group of shells or 3-node shells for Time History: I asked for strain rate output but the values remain equal to zero in post-processors; why?
Strain rate filtering needs to be activated, but it is not available for all material laws. This option has been introduced in RADIOSS version 42 for Material Laws 2, 36 and 44 and has been extended to some other laws in RADIOSS version 44.
It is not possible to get these outputs if the material law does not allow filtering (or “smooth”) the strain rate. On the contrary, using Fsmooth =1 and Fcut =1.E+30 will allow for all these laws to get these outputs without filtering the strain rate (indeed, filtering is activated but the cut-off frequency is so high that no filtering happens at all).
In certain cases, the outputs are also available even if strain rate filtering had not been asked for (Fsmooth =0).
This variable EPSD is available for both Animations and Time History in case of shell elements; it is only available for Animations in case of solid elements.
【3】What are the stresses SIGX, SIGY, and VONM in Animation files if I use integration points for the shells?
The stresses SIGX, SIGY… in Animation files represent the mean stresses through the thickness of the shell element. The VONM stress represents the Mises criteria applied to these mean stresses SIGX, SIGY… In the same way, the stresses F1, F2, F12, Q1 and Q2 given in Time History correspond to these mean stresses.
These mean stresses are computed by summation of the stresses at each integration point, averaged by the integration weights (refer to integration weights table in the RADIOSS Theory Manual). They are used for the internal forces calculation.
【4】Where is the plastic strain value computed if I ask for /ANIM/ELEM/EPSP for shell elements?
This value corresponds to the plastic strain value on the neutral fibre.
【5】What is the output to Animation files with /ANIM/ ... /ENER?
The specific energy per mass unit.
【6】What is the output to Animation files with /ANIM/ ... /HOUR?
The Hourglass energy per mass unit.
【7】Using shell elements with QEPH formulation (Ishell=24), the hourglass energy of the part and the subset are not equal to zero in Time History; why?
When looking to the SUBSET or the PART in Time History, the hourglass energy is not zero, since the energy absorbed due to the numerical damping is output there (it is related to coefficient dn of the shell property).
The energy corresponding to the physical stabilization of hourglass is counted as internal energy for this formulation.
【8】Using /ANIM/GZIP the Animation files are not readable; why?
This option uses the Gnu tool: GZIP which is normally available on all systems UNIX and LINUX. Please check that it is installed correctly on the machine RADIOSS is running on.
Note:
This option is not available on Windows platforms.
【9】What is the difference between /ANIM and /OUTP for EPSP output?
Runname_nnnn.sty files contain both membrane and max (over the integration points through the thickness) values; whereas Annn files contain only membrane value.
【10】Is it possible to get more (or less) Animation files while a computation is running?
Yes it is possible to write an Animation file by writing a control file in the data directory.
For the run number nn (/RUN/Runname/nn in the RADIOSS Engine input file), you have to write the file Runname_nn_0000_[C].rst with the process /ANIM in it.
RADIOSS Engine writes an Animation file at this time.
The other options available with control files are described in the Control File (C-File) file.
In order to change the Animation files writing frequency, you have to stop your RADIOSS computation while writing a RESTART file, by using a control file (option /STOP). Then you can chain a second run with a different frequency for the Animation files writing.
七，后处理
【1】采用壳单元，我问的应变时程输出（RunnameT01）及动画文件，但其值仍为零，为什么？
应变张量不计算在默认情况下，它必须先通过设置标志Istrain在RADIOSS输入文件（Runname_0000.rad）（旗来计算后处理株）在选项/ DEF_SHELL或在shell属性设置为1 。
相反，应变张量总是计算和法法第25和27可用。
【2】/阿尼姆/伊莱姆，砖或壳/ EPSD及变EPSD时程为一组的炮弹或3个节点的炮弹：我问的应变速率输出，但值保持在后处理器等于零，为什么？
应变率滤波需求被激活，但它并非适用于所有材料的法律提供。此选项已被引入RADIOSS版本42材料法例第2，第36和44，并已扩大到44 RADIOSS版本的一些其他法律。
这是不可能取得这些成果如果材料法律不允许过滤（或“顺利”）的应变速率。相反，使用Fsmooth = 1和Fcut = 1.E +30将所有这些法律没有得到允许过滤这些输出应变率（事实上，过滤被激活，但截止频率是如此之高，没有发生过滤在所有）。
在某些情况下，产出也可过滤即使应变率没有要求（Fsmooth = 0）。
这个变量EPSD都可以使用动画和时间史壳单元的情况，它仅适用于固体元素的情况下动画可用。
【3】什么是应力动画文件SIGX，SIGY和VONM如果我使用的炮弹结合点？
该讲SIGX，SIGY ...在动画文件代表的平均通过壳单元厚度的压力。该VONM应力代表米塞斯准则适用于这些平均应力SIGX，SIGY ...在同样的方式，讲的F1，F2，F12键，第一季度和第二季度的历史某一特定时间对应于这些平均应力。
这些平均应力是由在每个积分点强调的总和计算，平均由积分重量（指重量在RADIOSS一体化理论手册表）。它们用于计算内力。
【4】哪里是塑性应变值计算，如果我/阿尼姆/伊莱姆/壳单元EPSP的要求？
此值对应于中性纤维塑性应变值。
【5】什么是与/阿尼姆/输出动画文件... / ENER？
每单位质量比能量。
【6】什么是与/阿尼姆/输出动画文件... /小时？
沙漏每单位质量的能量。
【7】配方中使用QEPH壳元素（Ishell = 24），该子集的一部分，沙漏能不能及时历史等于零，为什么？
当寻找到子集或部分在时间历程，沙漏能量不为零，因为吸收的能量，由于数值阻尼输出有（这是有关财产的外壳系数的DN）。
能源相对应的沙漏稳定算作物理内能为这个提法。
【8】使用/阿尼姆/ GZIP的动画文件无法读取，为什么？
该选项使用GNU工具：GZIP的通常是在所有的UNIX和Linux系统。请检查它是安装在机器上运行RADIOSS正确。
注：此选项不支持Windows平台。
【9】之间是什么/阿尼姆和/ OUTP的EPSP的输出之差？
Runname_nnnn.sty文件包含的膜和MAX（多年来通过的集成点的厚度）值而Annn文件只包含膜的价值。
【10】是有可能得到更多（或更少）动画文件，而一个计算运行？
是的，它可以写入数据目录中写入一个控制文件的动画文件。
为运行数字nn（/运行/ Runname /在RADIOSS引擎输入文件神经网络），你必须写过程/阿尼姆在它的文件Runname_nn_0000_研究[J]。零售税。
RADIOSS发动机在这个时候写的动画文件。
与对照文件提供的其他选项说明在控制文件（C文件）文件。
为了改变动画文件写作频率，你必须停止你RADIOSS计算，同时撰写重新启动文件通过使用一个控制文件（选项/停止），。然后你可以用一链为动画文件写作不同频率第二轮。
八、Results Checking
【1】How is the Energy Error in the listing file (Runname_0001.out) computed?
Ek
Translational kinetic energy at courant time
Ekr
Rotational kinetic energy at courant time
Ei
Internal energy
Ewk
Work of external forces (energy brought to the system)
E,1
Energy at beginning of the RUN (not at time t=0)
The Hourglass energy is not counted in this energy balance, so that a negative energy error generally occurs (except if using QEPH or BATOZ shells, and fully integrated solids, for which there is no Hourglass).
It is bounded to ±99%.
The energy error is reset after each RESTART.
It is possible to stop a job and rerun it by using a control file containing /CHKPT. In this case, error and energy values will restart from their last value.
【2】How to appreciate the Energy Error, and which values are reasonable values?
The Energy Error computed by RADIOSS is a percentage.
If the error is negative, it means that some energy has been dissipated.
In case of under integrated elements (Belytschko shells, solids with 1 integration point), the Hourglass energy can also explain a negative Energy Error since it is not counted in the energy balance. The normal amount of Hourglass energy is about 10 to 15%.
If the error is positive, there is an energy creation.
In case of using QEPH shell formulation or fully integrated elements, the Energy Error can be slightly positive since there is no Hourglass energy and the computation is much more accurate. An error of 1 or 2% will be acceptable.
In case of a more important positive energy, the source of this energy has to be identified. Incompatible kinematic conditions can lead to such a situation.
If the error reaches ±99%, the computation has diverged; except in the first cycle of a run for which the initial energy of the system was null, so that a relatively false energy balance often introduces large relative error.
【3】Is it necessary to take into account the added mass and how to check if the results are not modified too much?
The added mass can be due to Interface Type 2, Spotflag =1. In this case, the added mass is totally made at time t=0. It can also be due to options for constant time step (/DT/NODA/CST or /DT/INTER/CST).
In case of added mass in the model, it is necessary to check if it is not too important with respect to the total mass of the model (see the DM/M value in the last column in the RADIOSS Engine listing file (Runname_nnnn.out)).
It is also important to post-process this added mass in order to check that it is not too large locally, since this could mean false results (for checking this, the Animations written with /ANIM/NODA/DMAS have to be visualized).
浙公网安备 33021202002483