[Reynolds]

Hello,

A quick introduction: I am a finalist aeronautical engineering student just beginning to get stuck into my final year project. I am aiming to validate STAR CCM+ aeroacoustic abilities and then predict noise from some 'real world' cases (landing gear/road vehicle wing mirrors). I am just carrying out some preliminary runs for the moment and would appreciate a point in the right direction.

I have run a tansient case up to t=0.12s using the Proudman acoustic model. Now that it is finished I can only see the result at t=0.12. I want to see the contours at intervals of t up to 0.12, and run an animation of the delta t.

Should I have turned on some switch to record specific parameters every time step? I did think about switching on 'autosave' to an interval, but thought that all the transient data would be saved in the original .sim file anyway and did not want to have 10-20 large .sim files as I am limited on hard drive space by the university.

Any help would be great!

Thanks,
Matt

[Pauli]

You did not miss anything. This is a significant limitation when using StarCCM+.

You have two options. The first is the autosave option you described. But as you've recognized, the autosave option can create an enormous amount of data.

The second option is to do all your post processing as the run progresses. The upside is the solver handles all the heavy calculations. The downside is that post processing on the fly requires significant clairvoyance.

Personally I find neither is an attractive option. Your best bet is to make a small model so you can run it repeatedly until you sort out all the post processing requirements & associated setups (derived parts, reports, monitors, scenes, etc.).

[Reynolds]

Thanks Pauli,

I think I may be able to find a suitable directory to save the time steps whilst it is running. I have heard that there is a 'screen grab' function within STAR. If so I could be able to write a java script to autosave each screen grab and then not require gigabytes of storage of all the timesteps.

Thanks for your speedy response,
Matt

[abdul099]

You don't need a java macro to save a scene. In the scene, you can go to the update folder and tick "save to file" and the update frequency. Way more easier when the scene is not changing view points etc...

[Reynolds]

Abdul,

that is very useful. Thankyou! The solution to these problems always tends to be right under your nose doesn't it!

Matt