Jump to content

Search the Community

Showing results for tags 'warning'.

More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • Altair Support Forum
    • Welcome to Altair Support Forum
    • Installation and Licensing
    • Modeling & Visualisation
    • Solvers & Optimization
    • Conceptual design and Industrial design
    • Model-Based Development
    • Manufacturing Simulation
    • CAE Process Automation
  • Academic Partner Alliance Forum
    • APA - Composites
    • APA - CFD & Thermal
    • APA - Vehicle Dynamics
    • APA - Manufacturing
    • APA - Crash and Safety
    • APA - Noise, Vibration and Harshness
    • APA - System Level Design
    • APA - Structural and Fatigue
    • APA - Marine
  • Japanユーザーフォーラム
    • ユーザーフォーラムへようこそ
    • インストールとライセンス
    • モデリング(プリプロセッシング)
    • シミュレーション技術(ソルバー)
    • データ可視化(ポストプロセッシング)
    • モデルベース開発
    • コンセプト設計と工業デザイン
    • 製造シミュレーション
    • CAE プロセスの自動化
    • Student Edition(学生用無償版)


There are no results to display.

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start





Website URL







Found 10 results

  1. Hi, I am using Incremental Radioss. There are few default material available in the database. When running the simulation with those default material, the simulation runs successfully (though it has 0 errors and 2 warnings. The warning is related to the material property). But I am using a different material which I add it in the database manually. When running the simulation with the manually added material, I get the error in simulation running or the simulation gets stopped in the middle while it is running few animation files. In the summary page, I get 0 errors and 2 warnings, the same one which I got while running with the default materials. The difference is that, the simulation gets over when running with the default material but it isn't getting completed with the manually added materials. The material I am adding is DP1200 steel. Have attached with the screenshot of the error. Error : 2 warning id :1084 Warning in material law1 When referring to material law1, it says it is related to the elasticity of the material. But I have given the input values properly. Kindly help me as soon as possible and thanks in advance.
  2. George P Johnson

    Warnings while importing the files

    Hello When importing a nastran file into HyperMesh I find warnings as shown in the image Can you explain to me where these warnings come from? and how to correct these errors? Thank you
  3. Hello guys, first of all, I'd like to thank you for your great support. I'm quite new to FE analysis and now i'm facing my first problems. To get known to HyperWorks, I started to mesh an imported CAD file with Hypermesh and defined materials and properties. Before applying Boundary Conditions and forces I wanted to check the model for errors and started the anaylisis ( Solver: Radioss (Block 140)) That's where I encountered some error messages. With the help of this forum I was able to fix some problems. For these messages I wasn't able to find any solution: According to that warning, i found a thread here ( http://forum.altairhyperworks.com/index.php?/topic/19028-warnings/#comment-39612 ) Unfortunately I couldn't help myself to fix that issue. For which criteria I have to check the surfaces? What's to do to fix that error in element group? Regards
  4. gbd


    WARNING 510: Imaginary part of the impedance is large thus the real part will be inaccurate WARNING 4722: It is highly recommended to use double precision accuracy (solution settings) WARNING 509: Reactive power large thus real power is inaccurate WARNING 2340: No further output of warnings and hints Hı, I have these problems and I don't know how I solve these. Please help me
  5. ZDecker3

    Zero composite thickness

    Hi All, I'm currently attempting to run an analysis on a carbon fiber/honeycomb structure. The composites is set up off of a meshed 2D surface by creating plys to determine the direction, thickness, material, and selecting the designated elements. They were than organized by creating a symmetric laminate and than a PCOMPP property is assigned to the same 2D elements as the plys. When I put the 3D element representation on and turn on the composite layers, everything looks exactly how it should, but I am receiving the warning below warning when I run a check in Optistruct. *** WARNING # 1569 for property id = 19. Thickness is zero for this composite. This will produce meaningless stress results and may cause singularity of the global stiffness matrix. Property 19 is the property where it assigns the PCOMPP property. The analysis does run up until it hits error #153 which seems to be caused by the above warning. *** ERROR # 153 *** Exactly zero pivoting encountered during Numerical Factorization; the model may have rigid body mode. Solver error no. = -503 spc set id = 2 index = 1 Possible reasons are: 1) insufficiently constrained model, 2) having rigid body mechanisms within the model, 3) extremely ill-conditioned rigid element sets, 4) extremely thin shells (as used for "skinning") that have MID2/MID3, 5) gap elements with extremely high stiffness (KA, especially KT or MU). Check the model and rerun the problem. (MECHCHECK may be used to find the rigid body modes. To do so, change the input to be an eigenvalue analysis and add MECHCHECK.) (WARNING: results obtained with MECHCHECK cannot be used because the model is changed internally.) This error was detected in subroutine bcsmtxfct. Does anyone know what might be causing the initial warning in this model? It seems weird to me that it says that it has zero thickness but when it's in 3D element representation it shows the thickness of the carbon layers and the honeycomb core.
  6. For a given element (except for the fifth node of a pyramid) each node is connected to three other nodes via three connected edges. Assume R1, R2, and R3 are the vectors for the three connected edges. For a positive Jacobian: ( R1 × R2 ) · R3 > 0 This test is done for every node of every element - so a mesh with 10K tetrahedral elements would yield 40K Jacobian tests.
  7. During the processing stage, acuPrep determines whether or not 'surfaces' from Simple BC or Element BC commands are boundaries or internal to the parent element set. If a surface element (tri or quad) has a volume element on only one side - or volume elements from different sets on both sides - it is considered to be a boundary. If a surface element has a volume element on both sides, and those volume elements are in the same element set - it is considered to be internal. If there are surfaces in the geometry between volumes in the same element set, these surfaces should not have Boundary Conditions defined. If there truly is an internal 'wall' (such as a baffle) within a given volume, the mesh surfaces should be split to yield two sets of nodes and two sets of surface elements.
  8. If User's are unable to open a database or if it gives an error like "Unable to create path Marker" then we can say that the database is corrupted. In such cases the data from this corrupted database can be extracted by following the below steps, Install HDFview on the machine (http://www.hdfgroup.org/hdf-java-html/hdfview/) Open HDFview GUI Load the database by clicking on File > Open in the menu bar and navigating to the database location. Select the database and click Open All the data in the database will be displayed in hierarchical format Click on first item in the tree, press Shift and select the last item. All the items in the tree will be selected Right click and select Copy Click on File > New > HDF5 Provide a filename (eg: test.acs) and save the database Scroll down to the bottom to see the new database created (test.acs.h5) Right-click on the new database and select Paste. Click Yes to copy the selected objects You can see all the objects under the new database Save the database. File > Save, then close the HDFview GUI by clicking on File > Exit Rename the new database (eg: test.acs.h5 to test.acs) Load the new database into AcuConsole
  9. python: error while loading shared libraries: libstdc++.so.5: cannot open shared object file: No such file or directory AcuConsole requires the standard C++ libraries, version 5 to be installed on the system. These libraries can be downloaded from the various rpm repositories on the web.
  10. Whenever AcuPrep sees the same command listed twice in a single input file, it will issue the following warning: *** WARNING: Multiple command issue In many cases, this warning is due to a setting associated with the AUTO_SOLUTION_STRATEGY command. For example, the following input file commands will cause the warning that is shown below: From the input file: ... AUTO_SOLUTION_STRATEGY { max_time_steps = 100 initial_time_increment = 10000000000.0 # sec convergence_tolerance = 0.0001 num_krylov_vectors = 10 relaxation_factor = 0.25 flow = on } STAGGER( "flow" ) { max_linear_solver_iterations = 10000 } .... From the log file: ... acuPrep: Reading AUTO_SOLUTION_STRATEGY acuPrep: Processing AUTO_SOLUTION_STRATEGY acuPrep: AUTO_SOLUTION_STRATEGY: creating and including "fixedMassFlow.ss.inc" ... acuPrep: Reading TIME_SEQUENCE acuPrep: Reading STAGGER( "flow" ) acuPrep: Reading STAGGER( "eddy_frequency" ) acuPrep: Reading STAGGER( "kinetic_energy" ) acuPrep: Reading TIME_INCREMENT acuPrep: Reading TIME_INTEGRATION acuPrep: Reading LINEAR_SOLVER_PARAMETERS acuPrep: Reading CONVERGENCE_CHECK_PARAMETERS acuPrep: Reading ALGEBRAIC_MULTIGRID_PARAMETERS acuPrep: Reading STAGGER( "flow" ) acuPrep: *** WARNING: Multiple command issue ... The reason for this is that the AUTO_SOLUTION_STRATEGY command itself generates a STAGGER( "flow"){} command when it is executed. This can be seen by the fact that AcuPrep displays a message that it is reading STAGGER( "flow" ) after processing the AUTO_SOLUTION_STRATEGY command. So, the fact that I manually added this command to the input file as well leads to the warning. In this case, the command duplication is deliberate because I increased the max_linear_solver_iterations to 10000 for the flow stagger. Note that when modifying the "Advanced Solution Strategy" settings in AcuConsole, these warnings will appear for any of the settings that are modified. The following image shows an example of modifying the settings in a similar fashion as what was described above: Note that if you are receiving these warnings and you are not sure why, it is best to review the input file and the log file to understand what is causing them. Most times, this warning is expected as a result of changes to the solution strategy. However, if it is appearing for other commands, it is important to review your settings to understand why the warning appears.