Create Animation File in Radioss

Ovunc2

Hello, 

I' m working on impact analysis in Radioss. 

As you know, we can create animation files at regular intervals with the ENG/ANIM/DT card.

But, I want to see the moment of impact in more detail. So can I create animation files at different intervals in certain time intervals and at different intervals in other time intervals?

Thank you. 

Best Regards, 

Ovunc

PaulAltair

Hi, to do exactly as you ask, the only solution currently is to break your model up into multiple engine files (i.e. using 'restarts', though the restarts may be set in advance)

so, for example, if you know impact is occurring at approx 0.1s

you could have your _0001.rad with an /ANIM/DT of 0.01 with a termination time in /RUN of 0.09s

Then you have a _0002.rad as a copy of your _0001.rad but with /ANIM/DT of 0.001 and termination time in /RUN of 0.11s

(you can then have _0003.rad, _0004.rad etc. etc.)

if you submit the Starter (_0000.rad) from a folder containing both the _0001.rad and _0002.rad then the default behaviour is to run both of those before the job exits and the animation frequency will be higher for the end of the run.

An alternative that may also be of interest is the option /ANIM/SENSOR, this allows you to write additional /ANIM files at a frequency defined on that card once a sensor has been triggered, this could allow you to start writing extra animation file output only once a condition has been met (e.g. based on a contact or displacement criterion) these animation files are written in addition to those already being written at /ANIM/DT frequency

Another similar option /ANIM/LSENSOR allows a single extra animation file to be written as each of a series of sensors is triggered

Finally, you can manually trigger a single extra animation file in real time at any point in the run by issuing the command /ANIM into the .ctl file (this can be done from the compute console if you are using that)

Hope this helps, the syntax for the /ANIM/SENSOR options is available in the help documentation

Paul

Ovunc2

Paul Sharp_21301 said:

Hi, to do exactly as you ask, the only solution currently is to break your model up into multiple engine files (i.e. using 'restarts', though the restarts may be set in advance)

so, for example, if you know impact is occurring at approx 0.1s

you could have your _0001.rad with an /ANIM/DT of 0.01 with a termination time in /RUN of 0.09s

Then you have a _0002.rad as a copy of your _0001.rad but with /ANIM/DT of 0.001 and termination time in /RUN of 0.11s

(you can then have _0003.rad, _0004.rad etc. etc.)

if you submit the Starter (_0000.rad) from a folder containing both the _0001.rad and _0002.rad then the default behaviour is to run both of those before the job exits and the animation frequency will be higher for the end of the run.

An alternative that may also be of interest is the option /ANIM/SENSOR, this allows you to write additional /ANIM files at a frequency defined on that card once a sensor has been triggered, this could allow you to start writing extra animation file output only once a condition has been met (e.g. based on a contact or displacement criterion) these animation files are written in addition to those already being written at /ANIM/DT frequency

Another similar option /ANIM/LSENSOR allows a single extra animation file to be written as each of a series of sensors is triggered

Finally, you can manually trigger a single extra animation file in real time at any point in the run by issuing the command /ANIM into the .ctl file (this can be done from the compute console if you are using that)

Hope this helps, the syntax for the /ANIM/SENSOR options is available in the help documentation

Paul

Hi Paul @Paul Sharp , 

Thanks for your reply. It was very useful for me.

Best Regards, 

Ovunc