This section is empty. This is just a suggestion on how to structure it. Please feel free to add questions and answers here!
Using multiple POSDAT.F - simple trick
There may be instances when the simulation may require multiple versions of POSDAT.F to be used. For example, one POSDAT.F may be used to calcualte and another used to print. Everytime copy pasting the code or renaming the files as POSDAT.F may be a little boring / inefficient. In stead the following procedure can be adopted:
Suppose you have posdat1.f and posdat2.f for 2 different purposes. Rename them as POSDAT1.TXT and POSDAT2.TXT. Ensure that these files contain only the code that you write. The star generated code must not find a place here. and keep them int he ufile folder. In the original 'empty' POSDAT.F generated by STAR, use the follwoing line:
if you need to run the first job. this command automatically transfers the control to the POSDAT1.TXT. Mind that though they are named .txt they still need to be in proper fortran format. else, this will result in compilation error.
Also they cannot have the extension '.f' because star tries to compile them as separate files and ends up giving an error.
Using scene files to produce 3D images
A little known but very useful tool is Starview and the scene file. Starview is a small, free piece of software that runs on windows and reads the native scene file format (*.scn), the scene file is a 3D image file that you can create in either pro-VIS or pro-STAR and allows the starview user to navigate around a set of post processed results.
When you have set up your post-processing as you would like to display it (section plots, streamlines etc) then you save the scene file (pro-STAR: in glm mode, utilities -> write STAR-CD scene file, pro-VIS: window -> write STAR scene file) and then drag and drop it on the starview executable. You can then navigate around the results you have set up allowing you to zoom, pan and rotate around the scene and look at parts of the model you are interested in. Starview is small (approx 2mb) as are the scn files and so can be easily e-mailed to clients/colleagues who may not have a STAR-CD license.
Using PRODEFS, PROINIT and .Prostar.Defaults to customise pro-STAR
Setup a directory and point the STARUSR environmental variable at it
This file can be used to create customised commands that perform one or more operations (obviously the commands cannot conflict with currently defined pro-STAR commands).
E.G. You can get the word "pall" to issue cset,news,fluid zoom,off cplot if you so wish. All you need to do is in the directory specified, create a file called PRODEFS and put in the entry: pall=cset,news,fluid $zoom,off $cplot. From now on when you open a new Pro-STAR session, whenever you type pall, that string of commands is issued.
This file controls what happens during the startup of pro-STAR, the file is read and any commands in it issued.
E.G. If you wish to open pro-STAR with the graphics window having a reverse background just open a file in your STARUSR directory called PROINIT and put the command clrm reve in it. From now on, as pro-STAR opens, this file will be read and the background with be reversed. If you haven't already specified a STARUSR directory then you will notice that in your working directory a PROINIT file is created, this is useful as a "roadmap" for you own customised PROINIT
This file can be used to control the action of your function keys. Again all that needs to be done is the creation of a file called .Prostar.Defaults in your STARUSR directory.
E.G. If you want the F1 key to always perform a cplot just edit the .Prostar.Defaults file and at the top put $FUNCTION_KEYS_DEFINITION then underneath put cplot. You can then continue down for each of the definitions you require, after the last definition you need to put $END
How can I try STAR-CCM+?
You can download a free version of STAR-CCM+ from the CD-adapco website http://www.cd-adapco.com/products/STAR-CCM_plus/STAR-CCM_trial.html
This version is limited to 16,000 cells per CPU across a maximum of 2 CPU's and allows full usage up to this limit.
You can import ngeom and ccm files (native CDA formats) as well as grd, cas and msh grids.
Stand-alone CAD integrated package with solid modeller, automatic mesher and solver. There are two versions, one using STAR-CD as a solver and able to create tetrahedral and hybrid meshes, the other using STAR-CCM+ and able to create tetrahedral, polyhedral and hybrid (tet or poly) meshes.
Catia 5 plugin
Unigraphics NX plugin