Siemens FAQ
From CFD-Wiki
(→What is STAR-CCM+?) |
|||
(31 intermediate revisions not shown) | |||
Line 3: | Line 3: | ||
== STAR-CD == | == STAR-CD == | ||
- | === | + | === Using multiple POSDAT.F - simple trick === |
- | Answer | + | Answer: |
- | + | 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: | |
+ | |||
+ | INCLUDE 'POSDAT1.TXT' | ||
+ | |||
+ | 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 | ||
+ | |||
+ | ==== PRODEFS ==== | ||
+ | |||
+ | 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. | ||
+ | |||
+ | ==== PROINIT ==== | ||
+ | |||
+ | 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 | ||
+ | |||
+ | ==== .Prostar.Defaults ==== | ||
+ | |||
+ | 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 | ||
== STAR-CCM+ == | == STAR-CCM+ == | ||
- | == STAR- | + | === What is STAR-CCM+? === |
- | + | Back around the turn of the 00s, CD-adapco decided to develop a new CFD code, called STAR-CCM+. Its aim was to take advantage of the latest advances in CFD and computing to produce a code that is easy-to-use but without compromising on accuracy or capability. They got together a team, headed by Wayne Smith (one of the key developers of Fluent) to do the task. The first release was in 2004. The latest release (October 2024) is Release 2410 (V19.10). | |
+ | STAR-CCM+ is a face-based code, which means that it can mesh and solve on arbitrary polyhedral cells. It uses object-oriented (OO) programming and has a client-server architecture. The server is written in C++ and the client in Java. | ||
+ | |||
+ | One of its key features is its simulation process. The user is able to go from CAD geometry to post-processing entirely within the STAR-CCM+ environment. | ||
+ | |||
+ | There is a STAR-CCM+ lite version available with more limited functionality and CD-adapco's own 3D CAD tool ( 3D-CAD ) has been integrated into the STAR-CCM+ client. | ||
+ | |||
+ | === How can I try STAR-CCM+? === | ||
+ | |||
+ | Please contact your nearest CD-adapco office or agent (full list at [[http://www.cd-adapco.com]]) or e-mail CD-adapco at | ||
+ | |||
+ | [[info@us.cd-adapco.com]] or | ||
+ | |||
+ | [[info@uk.cd-adapco.com]] | ||
+ | |||
+ | to request a trial license of STAR-CCM+ | ||
+ | |||
+ | You can now also download 20 example cases, with instructions on how to set-up and run and post-process the calculations. | ||
+ | |||
+ | === How do I produce an animation in STAR-CCM+ === | ||
+ | |||
+ | Animations can be produced for either a transient of steady-state calculation. | ||
+ | |||
+ | Transient: When running a transient calculation, you can set Scenes to write an image file (eg a PNG) at set intervals (every 1 or 2 timesteps or iterations). To do this, go to Attributes > Update. In this panel you can specify the update frequency of the scene, whether to write this to a file, the file format, resolution and location. | ||
+ | |||
+ | Steady: You can generate an animation for a steady result using a Java macro, varying the position of a plane section, length of a streamline etc, and writing an image file. Example macro is below. | ||
+ | |||
+ | // STAR-CCM+ macro: AnimatePlaneSection.java | ||
+ | package macro; | ||
+ | |||
+ | import java.util.*; | ||
+ | |||
+ | import star.common.*; | ||
+ | import star.base.neo.*; | ||
+ | import star.vis.*; | ||
+ | |||
+ | |||
+ | public class AnimatePlaneSection extends StarMacro { | ||
+ | |||
+ | public void execute() { | ||
+ | double xCoord ; | ||
+ | int FileName ; | ||
+ | String path = "/INSERT_PATH/" ; | ||
+ | StringBuffer path2 = new StringBuffer("") ; | ||
+ | xCoord = -1.0 ; | ||
+ | FileName = 0 ; | ||
+ | |||
+ | Simulation simulation_0 = | ||
+ | getActiveSimulation(); | ||
+ | |||
+ | // select plane section | ||
+ | PlaneSection planeSection_0 = | ||
+ | ((PlaneSection) simulation_0.getPartManager().getObject("plane section 2")); | ||
+ | // select scene | ||
+ | Scene scene_0 = | ||
+ | simulation_0.getSceneManager().getScene("Geometry Scene 1"); | ||
+ | |||
+ | // define number of loops | ||
+ | int counter = 150; | ||
+ | |||
+ | for (int i=0; i<counter;i++) | ||
+ | { | ||
+ | // set and increment the X coordinate of the plane section | ||
+ | xCoord = xCoord + 0.1; | ||
+ | |||
+ | // increment the file name so that it doesn't overwrite the last one | ||
+ | FileName = FileName + 1 ; | ||
+ | |||
+ | // create the file name | ||
+ | path2.append("PlaneSection").append(i).append(".png") ; | ||
+ | |||
+ | // change the X coordinate of the plane section, leaving the others fixed. | ||
+ | planeSection_0.setOrigin(new DoubleVector(new double[] {xCoord, -11.0, 10.98441335})); | ||
+ | |||
+ | // write image file giving the name (path + path2.toString()) and the screen resolution (1068, 605) | ||
+ | scene_0.printAndWait(resolvePath(path + path2.toString()), 1, 1068, 605); | ||
+ | |||
+ | // clear path2 which contains the file name | ||
+ | path2.delete(0,path2.length()); | ||
+ | } | ||
+ | } | ||
+ | } | ||
+ | |||
+ | == STAR-CAD Series == | ||
+ | |||
+ | === STAR-Design === | ||
+ | |||
+ | 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. | ||
+ | |||
+ | === STAR-Cat5 === | ||
+ | |||
+ | Catia 5 plugin | ||
+ | |||
+ | === STAR-NX === | ||
+ | |||
+ | Unigraphics NX plugin | ||
+ | |||
+ | === STAR-Works === | ||
+ | |||
+ | SolidWorks plugin | ||
+ | |||
+ | === STAR-Pro/E === | ||
+ | |||
+ | Pro-Engineer plugin | ||
+ | |||
+ | == es-soltiuons == | ||
+ | * [http://www.weprintdiscs.com/ CD Printing] | ||
[[Category: FAQ's]] | [[Category: FAQ's]] | ||
+ | |||
+ | {{stub}} |
Latest revision as of 07:37, 16 December 2024
This section is empty. This is just a suggestion on how to structure it. Please feel free to add questions and answers here!
Contents |
STAR-CD
Using multiple POSDAT.F - simple trick
Answer:
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:
INCLUDE 'POSDAT1.TXT'
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
PRODEFS
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.
PROINIT
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
.Prostar.Defaults
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
STAR-CCM+
What is STAR-CCM+?
Back around the turn of the 00s, CD-adapco decided to develop a new CFD code, called STAR-CCM+. Its aim was to take advantage of the latest advances in CFD and computing to produce a code that is easy-to-use but without compromising on accuracy or capability. They got together a team, headed by Wayne Smith (one of the key developers of Fluent) to do the task. The first release was in 2004. The latest release (October 2024) is Release 2410 (V19.10).
STAR-CCM+ is a face-based code, which means that it can mesh and solve on arbitrary polyhedral cells. It uses object-oriented (OO) programming and has a client-server architecture. The server is written in C++ and the client in Java.
One of its key features is its simulation process. The user is able to go from CAD geometry to post-processing entirely within the STAR-CCM+ environment.
There is a STAR-CCM+ lite version available with more limited functionality and CD-adapco's own 3D CAD tool ( 3D-CAD ) has been integrated into the STAR-CCM+ client.
How can I try STAR-CCM+?
Please contact your nearest CD-adapco office or agent (full list at [[1]]) or e-mail CD-adapco at
to request a trial license of STAR-CCM+
You can now also download 20 example cases, with instructions on how to set-up and run and post-process the calculations.
How do I produce an animation in STAR-CCM+
Animations can be produced for either a transient of steady-state calculation.
Transient: When running a transient calculation, you can set Scenes to write an image file (eg a PNG) at set intervals (every 1 or 2 timesteps or iterations). To do this, go to Attributes > Update. In this panel you can specify the update frequency of the scene, whether to write this to a file, the file format, resolution and location.
Steady: You can generate an animation for a steady result using a Java macro, varying the position of a plane section, length of a streamline etc, and writing an image file. Example macro is below.
// STAR-CCM+ macro: AnimatePlaneSection.java package macro;
import java.util.*;
import star.common.*; import star.base.neo.*; import star.vis.*;
public class AnimatePlaneSection extends StarMacro {
public void execute() {
double xCoord ; int FileName ; String path = "/INSERT_PATH/" ; StringBuffer path2 = new StringBuffer("") ; xCoord = -1.0 ; FileName = 0 ;
Simulation simulation_0 = getActiveSimulation();
// select plane section
PlaneSection planeSection_0 = ((PlaneSection) simulation_0.getPartManager().getObject("plane section 2"));
// select scene
Scene scene_0 = simulation_0.getSceneManager().getScene("Geometry Scene 1");
// define number of loops
int counter = 150; for (int i=0; i<counter;i++) {
// set and increment the X coordinate of the plane section
xCoord = xCoord + 0.1;
// increment the file name so that it doesn't overwrite the last one
FileName = FileName + 1 ;
// create the file name
path2.append("PlaneSection").append(i).append(".png") ;
// change the X coordinate of the plane section, leaving the others fixed.
planeSection_0.setOrigin(new DoubleVector(new double[] {xCoord, -11.0, 10.98441335}));
// write image file giving the name (path + path2.toString()) and the screen resolution (1068, 605)
scene_0.printAndWait(resolvePath(path + path2.toString()), 1, 1068, 605);
// clear path2 which contains the file name
path2.delete(0,path2.length());
}
}
}
STAR-CAD Series
STAR-Design
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.
STAR-Cat5
Catia 5 plugin
STAR-NX
Unigraphics NX plugin
STAR-Works
SolidWorks plugin
STAR-Pro/E
Pro-Engineer plugin
es-soltiuons