Jump to content

Search the Community

Showing results for tags 'memory'.

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 , Licensing and Altair One
    • Modeling & Visualisation
    • Solvers & Optimization
    • Multi Body Simulation
    • 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
    • APA - Optical Design
  • Japanユーザーフォーラム
    • ユーザーフォーラムへようこそ
    • Altair製品の意外な活用例
    • インストール / ライセンス / Altair One / その他
    • モデリング(プリプロセッシング)
    • シミュレーション技術(ソルバー)
    • データ可視化(ポストプロセッシング)
    • モデルベース開発
    • コンセプト設計と工業デザイン
    • 製造シミュレーション
    • CAE プロセスの自動化
    • エンタープライズソリューション
    • データアナリティクス
    • 学生向け無償版(Altair 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 6 results

  1. Hello, I'm running a Non_Linear Static simulation on one of the Door_panel_frames. Established the Bonding/Separating connections on the potential connection regions. Also, BC and material established. But I get the error, " Not Enough memory for equation system. Number of Equations 205" Max number of cores is default 8 What are the steps to correct this? Regards, KP
  2. HI there, Is it possible with Evolve 2016 to fix the camera of perspective viewport? I know it is possible to lock it using the icon on the top right of the view. But apart from just lock it, I would need to SAVE the view so a can use it again with the same model in the future even when I want to work with it unlocked. thanx Pil
  3. Dear all, We are trying to run a very heavy model, non-linear analysis (slide contact + pretension) and quite a lot of elements. It keeps giving us an error of not enough memory for the mumps solver. We are running on a machine with 4 cores and 64 Gb Ram. We tried all the options, (core in, core out, fixlen, len, etc..) but same error! Is there a way to tell optistruct to use all the available ram and then use the hard drive for the rest? Or do you now of a better way to avoid this error message, and let the simulation run, even if it is going to do few days to run? Many thanks in advance for any response and for your help and valuable time.
  4. Hello everyone, I've encounter an error while using the optistruct solver. It says: Errors reported during program execution Error output from the solver: ============================== *** WARNING: The amount of allocated memory exceeds available RAM - this may cause significant slowing down of solution progress due to the swapping out memory to the swap file. It is recommended to use out-of-core solution to reduce memory requirements. hwsolver.mesg output from the solver: ============================== *** FATAL ERROR # 9171 *** 32-bit overflow in memory allocation for "lgnnl". It's very strange that the system didn't report "not enough memory". Rather, from the task manager memory window, I observed a steep increase in memory usage up to my max memory (32GB) and then the solver instantly failed.The fem file is quite large, about 3.7GB. I also forced out of core solution. The free disk space is about 600GB. It's a RAID 0 ssd setup btw. Can anyone plz help me on this issue? Cheers, Edward
  5. 最小および、推奨システム要件は以下の通りです。 Processor: Intel or AMD 64 bits multi-core Graphic card : OPENGL V2.0 互換 NVIDIA チップセット 最小システム要件 推奨システム要件 詳細については、 <インストールディレクトリ>\2019\flux\Flux\DocExamples\InstallationGuide\00_Installation_guide_en.pdf をご覧ください。
  6. Error 37389: DGFM is only supported when solving the linear equation system in main memory I keep getting this error when trying to use DGFM to solve a Vivaldi array. The array has only 2 elements but it seems as thought it is very resource intensive. What exactly does this error mean? What can I do to fix it? Does it have anything to do with the other problem of trying to use DGFM in conjunction with SEP for dielectric regions or is it a separate problem altogether? Is there a better way to simulate a finite array?
  • Create New...