Jump to content

Search the Community

Showing results for tags 'fluid-structure interaction'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Altair Support Forum
    • Welcome to Altair Support Forum
    • Installation and Licensing
    • 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製品の意外な活用例
    • インストール / ライセンス / その他
    • モデリング(プリプロセッシング)
    • シミュレーション技術(ソルバー)
    • データ可視化(ポストプロセッシング)
    • モデルベース開発
    • コンセプト設計と工業デザイン
    • 製造シミュレーション
    • CAE プロセスの自動化
    • エンタープライズソリューション
    • データアナリティクス
    • 学生向け無償版(Altair Student Edition)

Categories

There are no results to display.


Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Interests


Organization

Found 2 results

  1. By default, the nodes and element connectivity are absent from the OP2 file. This is done by design. FEMAP writes a parameter "PARAM OGEOM NO". This means do not write geometry to the op2 file. This is done because the pre-processor already has the geometry loaded and hence it needs only the results from the file. Workaround: Simply disable this parameter using the deck editor in FEMAP or remove this parameter by editing the deck outside of FEMAP
  2. Yes, AcuConsole does support a generic format for importing modal results. It is called AcuSolve Modal Response (AMR) format. Here is how it works: 1.) A single XML file contains the eigen values and references to other files containing the nodal coordinates, element connectivity, and eigenvectors for each mode. 2.) This XML file is what is read by AcuConsole. To accomplish this, go to the eigenMode Manager, select Open, then choose ACUSIM Modal Response from the File type filter drop down menu. You can now read in the XML file (with a .amr extension). Attached is an example showing the AMR format. Start by looking at the file named modalResponse.amr. This is the XML file. The format of that should be pretty obvious, but here is an explanation of it: coordinates Tag: Reads a file containing the coordinates of the structural model. This file contains nodeId xCrd yCrd zCrd element_set Tag: Reads the element connectivity of the structural model and specifies whether it is a 2-d or 3-d mesh. The format of the file is as follows: elementId node1 node2 node3 node4 ....... mode Tag: Specifies the eigenvalue for each mode, the mode index, and references the file containing the eigenvector. The format of the eigenvector files is: nodeId xEigenVector yEigenVector zEigenVector. Make sure that the eigenvalues are mass normalized when you import them into AcuConsole.
×
×
  • Create New...