Jump to content

Search the Community

Showing results for tags 'restart'.

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 14 results

  1. Hello I am using RADIOSS to simulate a crash test which I have previously done. The trajectory of the impactor before impact is complex and requires several linkages and mechanisms to set up. The area of interest is the post-impact behaviour (stress/strain) on the target component, as well as the trajectory of the impactor. When I run the impactor by itself, to see the launch trajectory, I get a reasonable run time of about an hour. When I run the impactor with a simplified initial velocity + the target with all the contact and failure cards defined, I get a reasonable run of about 3 hours. When I run the full model: impactor with the initial trajectory + the target with all the contact and failure cards defined, I get a run around 12 hours to reach the impact, and another 12-24 hours to get results from post impact trajectory. I believe this is partly due the finer mesh required for the target model. I was hoping there is a way I can split the analysis in two, using the results from a the first as an initial condition for the second. Consider the following scenario: Model A: Simple model with only what is required to set off the trajectory of the impactor. The target is not modeled. Run from T=0 to T=T_impact. The run is stopped at the moment where the impact would have occurred. Model B: The target, with finer mesh and contact and fail definition is introduced, and the analysis is "RESTART" picking up from where Model A left off. In other words the target (with finer mesh) only appears just before impact onwards. This should theoretically cut down the majority of the analysis time. Is there a way to set up a RESTART file with introduction of new elements / properties / fail cards, and linking it to a "Stopped" run? I hope the diagrams attached illustrates what I'd like to do. Please let me know if there is a way to do this. Thank you. Best Regards, MN
  2. Hi rahul, i need your help. You can see a below picture for example i am showing. Same as like one tube both ends are fixed and need to pass the stress requirement with reducing the diameter of the tube. So my aim to reduce the diameter of the tube. Is it possible in optimization. i have searched all the tutorials but i didn't find anything.If you have any example files please share me
  3. Hello, We have been running a quit heavy optimisation with hyperstudy using the GRSM algorithm. After about 37 runs, the computer stopped or we had a power cut or something, so we had an abnormal termination of the optimisation. Is there a way to restart the optimisation from where it stopped instead of running the whole thing again? It is a very heavy opt, so it took us a day and a half to run up to iteration 37, and it would be very important for us to just restart from where left. Many thanks in advance.
  4. how to restart a run when it is stopped before completion?
  5. Hi @all First, i hope this is the right forum for this topic. If it isn't, please switch. I've to simulate an multiphysics coupled heat transfer + fluid cooling process (like cooling fins or spines). For that case i've to define an heat flux into the base of the solid structure. The heat is flowing through the structure and left the structure on the "water" cooled contact surface. This cause an increase of the fluid temperatur deltaT (T_in-T_out) on the outflow against to teh inflow temperature. The fluid flow is perpendicular to the heat conduction in the solid. Points I've finished: Import complex geometry into ACUCONSOLE (+meshing) Define the global problem description Define the inflow, outflow, heat source (basic BC's) Simulation of the fluid flow through the structure still open Points: Simulation of the heat conduction Define the result of the Simulation (heat cond.) as boundary for the flow simulation As i wrote in the title, at the moment I work with the ACUCONSOLE. Is Hypermesh (with the ACUsolve deck) better for multiphysics like this? How can I define old results as boundary conditions in new simulations? (current temperature/heat flux as input value for the fluid wall) Is it possible to import more than one geometry into acuconsole? (The software always want to delete the previous part when i import a second one) I hope you can help me to solve this problem. best regards Alex
  6. Hi Procedure to Restart First, while submitting the files for restart, please create a new engine file (may be copy - paste original file) and edit the extension from *_0001.rad to *_0002.rad Next, in the newly created Engine file, you have to edit the number in /RUN, ex. /RUN/Drop_test/1/ will become /RUN/Drop_test/2/ Finally, while submitting the run call new Engine file(*_0002.rad) which you have created use same number of cores what you have used for the first run. Note: During restart you can also change many parameters (If needed) in the engine file like Termination time, Animation Frequency, Time History Frequency, Apply BCs, Apply Loads, Delete Interface/Part/Element etc Regards Prashanth A.R
  7. Hi all, How to stop a job and continue calculation from the end point with HyperWorks Solver Run Manager (Suppose a job is stopped and continue calculation with more cpus)? In addition, what's the effect of selections in the HyperWorks Solver View window? Any resources or videos will be appreciated. Best Wishes Roy
  8. Hi everyone, I'm doing a nonlinear quasi-static analysis (NLSTAT) composed of two loadstep. Usually I make modification on BC applied to the 2nd loadstep. It is possible to restart this analysis from the second loadstep instaed of restarting the complete analysis? thanks, Luke31
  9. i am trying to run a job via a restart file generated when i solved the job using (-nt 15 and -np 15) 225 processes. i am inputting same command line to use 0002.rad files but the job isn't running. there are 15 files present for restart - 0001_0001.rst to 0001_0015.rst but i am unable to run the job . it is giving me following error i am attaching 0001.out and 0002.out files oct_trial2_0001.out oct_trial2_0002.out
  10. Hello all, Is there any way to resume interrupted jobs because of unintentional reasons (PC failure, electricity loss, license server loss etc) in Opstistruct? Especially for NLSTAT analyses. Thanks in advance. Regards, Yetkin Hamurisci
  11. Submitted by Enric on Thu, 06/02/2011 - 11:18 I have a model I need to run multiple (n=25) times, each time with different "start" values. For every model, the COST function is used to optimise the model such that the model ends when the global optimisation is complete. At the moment, I have the start values in a .csv file in 25 columns which I can access via the Import block. However, as Vissim stops after each model is optimised, to run the multiple models I need to manually tell it which of the models it is to run which involves telling the import function which column to access. Please could you let me know if there is a way of doing two things: 1. Running all 25 models in sequence so I don't need to keep restarting the model myself manually. 2. Exporting data in such a way that at the end of each of the 25 models it saves the data in a separate data file (ie. so I end up with 25 data files). As far as I can see, using the Export block there is no way of setting the data filename automatically. Any guidance would be appreciated. Many thanks
  12. Hi, I need a little guidance on how to use the 'Restart' option in Acusolve. I have a setup running with constant density air model (temperaure equation disabled) on a cluster server, and I want to use this solution to start a run with the air model switched to ideal gas and temperature equation enabled. Thanks in advance for any help. Prashant
  13. To perform a restart in AcuSolve, there are two conditions that must be satisfied: 1.) The RESTART_OUTPUT command must be included in the simulation that you want to restart from. This command writes all data necessary to restart a simulation to disk at the specified intervals. 2.) The RESTART command must be included in the input file of the run that you are restarting. The only changes that are made to the simulation once the restart is performed are the commands that appear after the RESTART{} commmand in the input file. In the attached example, the flow was first solved using a steady state simulation. To restart the simulation, and solve only for turbulence (i.e. using the previous flow solution), simply execute acuRun. The input file contains all of the commands necessary to restart the run. Please see the AcuSolve Commands Reference Manual for more information about the RESTART and RESTART_OUTPUT commands. AcuSolve’s reference manuals can now be accessed through AcuConsole’s Help menu, To see the available manuals, select Help–>AcuSolve Help Home. This will bring up the searchable html version of the manuals.
  14. If I want to use the solution from a previous run as my initial condition for a restart, do I need to remove the NODAL_INITIAL_CONDITION command from my input file when restarting? The RESTART command simply reads the input data from a previous run (the last run by default unless a different run is specified). Any command appearing after the RESTART command will be processed and overwrite the settings from the previous run. NODAL_INITIAL_CONDITION, however, does have special behavior....when the RESTART command is processed, it automatically uses the data from the previous run. So, here are some scenarios to illustrate RESTART and NODAL_INITIAL_CONDITION. Consider the following input files for the restart run: This will pull the previous run's data for the initial conditions: RESTART {} RUN{} This will also pull the previous run's data for the initial conditions because the RESTART comes after the NODAL_INITIAL_CONDITION command (i.e. the restart data overwrites the NODAL_INITIAL_CONDITION data): NODAL_INITIAL_CONDITION(velocity){ variable = velocity values = {1,0,0} } RESTART {} RUN{} This will OVERWRITE the previous run's data for the initial conditions with 1,0,0 because NODAL_INITIAL_CONDITION comes after RESTART: RESTART{} NODAL_INITIAL_CONDITION(velocity){ variable = velocity values = {1,0,0} } RUN{}
  • Create New...