Jump to content
  • Announcements

    • Rahul Ponginan

      Please click here for a short but important announcement   03/26/17

      Dear Users Our Commercial and Academic users around the world can use these same forums here as before i.e. the Altair Support Forum , Commercial users from India with solver queries can go to the Solver Forum for India Commercial Users , Academic Users from India and AOC India Participants are requested to go to the Forum for India Academic Users and AOC India Participants , We will be tending to all queries in all the forums promptly as before, thank you for your understanding. 

Search the Community

Showing results for tags 'paraview'.

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 (Preprocessing)
    • Analysis (Solvers)
    • Optimization and Design Exploration
    • Visualization (Postprocessing)
    • Model Based Development
    • Conceptual design and Industrial design
    • 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
  • Forum for India Academic Users and AOC India Participants
    • India EDU Installation FAQ
    • India EDU Modeling and Visualisation
    • India EDU Linear, Non-Linear Solver ( Implicit/Explicit)
    • India EDU Multi-Body Dynamics
    • India EDU CFD
    • India EDU Optimisation
    • India EDU Report Generation
  • Solver Forum for India Commercial Users
    • IND - OptiStruct for Linear & Non-Linear Implicit
    • IND - OptiStruct & HyperStudy for Optimisation
    • IND - RADIOSS for Impact Safety & Non-Linear Explicit Applications
    • IND - MotionSolve for Multi-Body Dynamics
    • IND - HyperWorks CFD forum
    • IND - FEKO, Winprop & Flux
  • Forum for our Australia and New Zealand Based Users
    • ANZ - HyperWorks
    • ANZ - Electromagnetics
    • ANZ - HPC (PBS)
  • Japanユーザーフォーラム
    • ユーザーフォーラムへようこそ
    • インストールとライセンス
    • モデリング(プリプロセッシング)
    • シミュレーション技術(ソルバー)
    • データ可視化(ポストプロセッシング)
    • モデルベース開発
    • コンセプト設計と工業デザイン
    • 製造シミュレーション
    • CAE プロセスの自動化


There are no results to display.

Found 3 results

  1. Postprocessing in Paraview

    How do i open the results from acusolve simulation in paraview.
  2. TIME_AVERAGE_OUTPUT This type of output is a simple average. The value that is printed in the output file is computed as follows:UTimeAve = sum( U_n )/n, where n = the step number. The reset_frequency tells AcuSolve to start the time averaging procedure over by deleting the previous time averaged field, setting n=0, then starting the process out with a fresh set of values. Note that these values are not carried forward across restarts. So, every time you restart AcuSolve, the time average output is reinitialized. RUNNING_AVERAGE_OUTPUT This type of output uses a weighted average to compute the output value. This is useful for cases where you may want to weight the initial time steps less as the flow field is developing. The value that is printed in the output file is computed as follows: URunAve = 1/N*U_n + (1-1/N)*URunAve_n-1. Where N = min(step,N_max), step= the current time step number, and N_max=running_average_steps. The running_average_steps parameter is set in the EQUATION command. So, setting the running_average_steps essentially defines an averaging "window" over which to compute the output. This value is carried forward across restarts, and may also be initialized using the NODAL_INITIAL_CONDITION command. Note that TIME_AVERAGE_OUTPUT is simply an output quantity, whereas the RUNNING_AVERAGE_OUTPUT field is used in other areas internal to AcuSolve such as the non-reflecting boundary conditions, and running_average_wall_function. Both types of output can be visualized using Fieldview, Ensight, and Paraview. They are included in the extended output variables when using acuTrans to convert nodal output. Here is an example: acuTrans -out -to fieldview -extout If either TIME_AVERAGE_OUTPUT or RUNNING_AVERAGE_OUTPUT are defined, their variables will be written into the output file.
  3. The Lighthill stress tensor is constructed by taking derivatives of the velocity field. It is possible to build all terms of the Lighthill stress tensor within a post processing package (Fieldview, Ensight, or Paraview) by using the function calculator. To make this calculation efficient, it is suggested that the -extout flag is used on acuTrans when converting the solution to the post-processor format. This writes the velocity gradients to the file. The velocity gradients can then be assembled appropriately in the post processing package to form the Lighthill stress tensor without havin to compute each derivative in the post processor. The divergence of the Lighthill stress tensor is typically used for visualizing the acoustic source strength. Creating and animating isosurfaces of divT can provide insight into the acoustic source characteristics.