https://www.cfd-online.com/W/index.php?title=Special:Contributions/Aread14&feed=atom&limit=50&target=Aread14&year=&month=CFD-Wiki - User contributions [en]2024-03-29T13:33:11ZFrom CFD-WikiMediaWiki 1.16.5https://www.cfd-online.com/Wiki/STAR-CCMSTAR-CCM2007-06-15T15:06:18Z<p>Aread14: /* Links */</p>
<hr />
<div>=== STAR-CCM+ ===<br />
<br />
Produced by [[CD-adapco]], STAR-CCM+ was first released in May 2004.<br />
<br />
<br />
<br />
== Links ==<br />
[[http://www.cd-adapco.com] CD-adapco Homepage]<br />
<br />
[[http://www.cd-adapco.com/products/STAR-CCM_plus/index.html] STAR-CCM+ Product Page]</div>Aread14https://www.cfd-online.com/Wiki/STAR-CCMSTAR-CCM2007-06-15T15:06:06Z<p>Aread14: /* Links */</p>
<hr />
<div>=== STAR-CCM+ ===<br />
<br />
Produced by [[CD-adapco]], STAR-CCM+ was first released in May 2004.<br />
<br />
<br />
<br />
== Links ==<br />
[[http://www.cd-adapco.com] CD-adapco Homepage]<br />
[[http://www.cd-adapco.com/products/STAR-CCM_plus/index.html] STAR-CCM+ Product Page]</div>Aread14https://www.cfd-online.com/Wiki/STAR-CCMSTAR-CCM2007-06-15T15:04:53Z<p>Aread14: /* Links */</p>
<hr />
<div>=== STAR-CCM+ ===<br />
<br />
Produced by [[CD-adapco]], STAR-CCM+ was first released in May 2004.<br />
<br />
<br />
<br />
== Links ==<br />
[[http://www.cd-adapco.com] CD-adapco Homepage]</div>Aread14https://www.cfd-online.com/Wiki/STAR-CCMSTAR-CCM2007-06-15T15:03:35Z<p>Aread14: /* Links */</p>
<hr />
<div>=== STAR-CCM+ ===<br />
<br />
Produced by [[CD-adapco]], STAR-CCM+ was first released in May 2004.<br />
<br />
<br />
<br />
== Links ==<br />
[www.cd-adapco.com] CD-adapco Homepage</div>Aread14https://www.cfd-online.com/Wiki/STAR-CCMSTAR-CCM2007-06-15T15:02:50Z<p>Aread14: /* STAR-CCM+ */</p>
<hr />
<div>=== STAR-CCM+ ===<br />
<br />
Produced by [[CD-adapco]], STAR-CCM+ was first released in May 2004.<br />
<br />
<br />
<br />
== Links ==<br />
[[CD-adapco Home Page][www.cd-adapco.com]]</div>Aread14https://www.cfd-online.com/Wiki/STAR-CCMSTAR-CCM2007-06-15T15:01:36Z<p>Aread14: New page: === STAR-CCM+ ===</p>
<hr />
<div>=== STAR-CCM+ ===</div>Aread14https://www.cfd-online.com/Wiki/STAR-CCM%2BSTAR-CCM+2007-06-15T15:01:10Z<p>Aread14: New page: === STAR-CCM+ ===</p>
<hr />
<div>=== STAR-CCM+ ===</div>Aread14https://www.cfd-online.com/Wiki/CodesCodes2007-06-15T15:00:39Z<p>Aread14: /* Solvers */</p>
<hr />
<div>An overview of both free and commercial CFD software. Here you will find short descriptions of codes along with links to resources.<br />
<br />
'''Note to contributers:''' Please try to keep descriptions short and to the point (approximately 200 words) and avoid long lists of features or capabilities. Also keep in mind that all contributions are considered to be released under the GNU Free Documentation License 1.2 (see [[Project:Copyrights]] for details). Also note that all information should be verifiable and objective truths that also competitors to the code in question will agree upon. This is especially important if you are an employee of the company selling the code. See the [[CFD-Wiki:Policy]] for further information.<br />
<br />
== Free codes ==<br />
<br />
This section lists codes that are in the public domain, and codes that are available under GPL, BSD or similar licenses.<br />
<br />
=== Solvers ===<br />
<br />
* ADFC -- [http://adfc.sourceforge.net/index.html ADFC homepage]<br />
* Diagonalized Upwind Navier Stokes -- [http://duns.sourceforge.net DUNS homepage]<br />
* Dolfyn -- [http://www.dolfyn.net/dolfyn/index_en.html dolfyn homepage]<br />
*[[Edge]] -- [http://www.edge.foi.se/ Edge homepage]<br />
*[[ELMER]] -- [http://www.csc.fi/elmer/ ELMER homepage]<br />
* Featflow -- [http://www.featflow.de Featflow homepage]<br />
* Femwater -- [http://www.cee.odu.edu/model/femwater.php Femwater code]<br />
* FreeFEM -- [http://www.freefem.org FreeFEM homepage]<br />
*[[Gerris Flow Solver]] -- [http://gfs.sourceforge.net/ Gerris Flow Solver homepage]<br />
* IMTEK Mathematica Supplement (IMS) -- [http://www.imtek.uni-freiburg.de/simulation/mathematica/IMSweb/ IMTEK Mathematica Supplement (IMS) homepage]<br />
* iNavier -- [http://inavier.sourceforge.net/ iNavier Solver Home Page]<br />
* MFIX -- [http://www.mfix.org Computational multiphase flow homepage]<br />
*[[NaSt2D-2.0]] -- [http://home.arcor.de/drklaus.bauerfeind/nast/eNaSt2D.html NaSt2D-2.0 homepage]<br />
*[[NSC2KE]] -- [http://www-rocq1.inria.fr/gamma/cdrom/www/nsc2ke/eng.htm NSC2KE homepage]<br />
*[[OpenFlower]] -- [http://sourceforge.net/projects/openflower/ OpenFlower homepage]<br />
*[[OpenFOAM]] -- [http://www.openfoam.org/ OpenFOAM homepage]<br />
* OpenFVM -- [http://openfvm.sourceforge.net/ OpenFVM homepage]<br />
* PETSc-FEM -- [http://www.cimec.org.ar/petscfem PETSc-FEM homepage]<br />
* PP3D -- [http://www.featflow.de/ parpp3d++ homepage]<br />
* SLFCFD -- [http://slfcfd.sourceforge.net SLFCFD homepage]<br />
*[[SSIIM]] -- [http://folk.ntnu.no/nilsol/cfd/ CFD at NTNU]<br />
*[[Tochnog]] -- [http://tochnog.sourceforge.net Tochnog homepage]<br />
* Typhon solver -- [http://typhon.sf.net Typhon solver homepage]<br />
<br />
=== Grid generation ===<br />
<br />
*[[Delaundo]] -- [http://www.cerfacs.fr/~muller/delaundo.html Delaundo homepage]<br />
* GMSH -- [http://www.geuz.org/gmsh/ GMSH hompage]<br />
* NETGEN -- [http://www.hpfem.jku.at/netgen/ NETGEN homepage]<br />
* SALOME -- [http://www.salome-platform.org SALOME homepage]<br />
* TETGEN -- [http://tetgen.berlios.de/ TETGEN hompage]<br />
*[[Triangle]] -- [http://www.cs.cmu.edu/~quake/triangle.html Triangle homepage]<br />
<br />
=== Visualization ===<br />
*[[DISLIN]] -- [http://www.mps.mpg.de/dislin/server.html DISLIN homepage]<br />
* GMV -- [http://www-xdiv.lanl.gov/XCM/gmv/ GMV homepage]<br />
*[[Gnuplot]] -- [http://www.gnuplot.info/ gnuplot homepage]<br />
* GRI -- [http://gri.sourceforge.net/ GRI homepage]<br />
*[[Mayavi]] -- [http://mayavi.sourceforge.net/ MayaVi homepage]<br />
*[[OpenDX]] -- [http://www.opendx.org OpenDX homepage]<br />
*[[ParaView]] -- [http://www.paraview.org/HTML/Index.html ParaView homepage]<br />
*[[Tioga]] -- [http://www.kitp.ucsb.edu/~paxton/tioga.html Tioga homepage]<br />
*[[Vigie]] -- [http://www-sop.inria.fr/sinus/Softs/vigie.html Vigie homepage]<br />
*[[Visit]] -- [http://www.llnl.gov/visit Visit homepage]<br />
*[[vtk]] -- [http://www.vtk.org vtk homepage]<br />
*[[vtk.Net]] -- [http://vtkdotnet.sourceforge.net/ vtk.Net homepage]<br />
<br />
=== Miscellaneous ===<br />
<br />
*[[Engauge Digitizer]] -- [http://digitizer.sourceforge.net Engauge Digitizer homepage]<br />
*[[Ftnchek]] -- [http://www.dsm.fordham.edu/~ftnchek/ ftnchek homepage]<br />
*[[g3data]] -- [http://www.frantz.fi/software/g3data.php g3data homepage]<br />
* GIFMerge -- [http://www.the-labs.com/GIFMerge/ GIFMerge homepage]<br />
*[[Gifsicle]] -- [http://www.lcdf.org/~eddietwo/gifsicle/ Gifsicle homepage]<br />
*[[ImageMagick]] -- [http://www.imagemagick.org ImageMagick homepage]<br />
<br />
== Commercial codes ==<br />
<br />
=== Solvers ===<br />
<br />
* AcuSolve -- [http://www.acusim.com/ ACUSIM Software's homepage]<br />
* ADINA-F -- [http://www.adina.com/index.html ADINA's homepage]<br />
* ADINA-FSI -- [http://www.adina.com/index.html ADINA's homepage]<br />
* ANSWER -- [http://www.acricfd.com/ ACRi's homepage]<br />
*[http://www.cfd-online.com/W/index.php?title=CFD%2B%2B CFD++] -- [http://www.metacomptech.com Metacomp Techonlogies' homepage]<br />
* CFD2000 -- [http://www.adaptive-research.com/ Adaptive Research's homepage]<br />
*[[CFD-FASTRAN]] -- [http://www.esi-group.com/SimulationSoftware/advanced.html ESI Group's homepage]<br />
* CFD-ACE -- [http://www.esi-group.com/SimulationSoftware/advanced.html ESI Group's homepage]<br />
* CFdesign -- [http://www.cfdesign.com CFdesign's homepage]<br />
* CFX -- [http://www.ansys.com/ Ansys' homepage]<br />
* EFD -- [http://www.nika.biz/ Flomerics/NIKA homepage]<br />
*[[FENSAP-ICE]] -- [http://www.newmerical.com/ NTI' homepage]<br />
* FINE -- [http://www.numeca.be/ Numeca's homepage]<br />
* FIRE -- [http://www.avl.com/ AVL's homepage]<br />
*[[FLACS]] -- [http://www.gexcon.com/index.php?src=flacs/overview.html GexCon's homepage]<br />
* FLOW-3D -- [http://www.flow3d.com/ Flow Science's homepage]<br />
* FLOTHERM-- [http://www.flomerics.com Flomerics' homepage]<br />
* FLOVENT-- [http://www.flomerics.com Flomerics' homepage]<br />
* FLOWVISION -- [http://www.fv-tech.com FlowVision's homepage]<br />
*[[FLUENT]] -- [http://www.fluent.com Fluent's homepage]<br />
* FluSol -- [http://www.cfd-rocket.com FluSol's hompage]<br />
* Flowz--[http://www.zeusnumerix.com Zeus Numerix's homepage ]<br />
*[[J-FLO]] -- [http://www.newmerical.com NTI's homepage]<br />
* KINetics Reactive Flows -- [http://www.ReactionDesign.com Reaction Design's homepage]<br />
* KIVA--[http://www.lanl.gov/orgs/t/t3/codes/kiva.shtml Los Alamos homepage]<br />
*[[NOGRID FPM]] -- [http://www.no-grid.com NOGRIDS's homepage]<br />
*[[PHOENICS]] -- [http://www.cham.co.uk CHAM's homepage]<br />
*[[SPLASH]] -- [http://www.panix.com/~brosen SPLASH's homepage]<br />
*[[STAR-CD]] -- [http://www.cd-adapco.com CD-adapco's homepage]<br />
* [[STAR-CCM+]] -- [http://www.cd-adapco.com CD-adapco's homepage]<br />
* Turb'Flow -- [http://www.fluorem.com Fluorem's hompage]<br />
<br />
=== Grid generation ===<br />
<br />
* ADINA-AUI -- [http://www.adina.com/index.html ADINA's homepage]<br />
*[[CFD-GEOM]] -- [http://www.esi-group.com/ ESI's homepage]<br />
*[[CFD-VISCART]] -- [http://www.esi-group.com/ ESI's homepage]<br />
* CFDExpert-GridZ --[http://www.zeusnumerix.com/ Zeus Numerix's homepage]<br />
*[[Gridgen]] -- [http://www.pointwise.com/ Pointwise's homepage]<br />
* GridPro -- [http://www.gridpro.com/ PDC's homepage]<br />
* Harpoon -- [http://www.ensight.com/ CEI's homepage]<br />
* ICEM CFD -- [http://www.ansys.com/ ANSYS' homepage]<br />
<br />
=== Visualization ===<br />
<br />
* ADINA-AUI -- [http://www.adina.com/index.html ADINA's homepage]<br />
*[[CFD-VIEW]] -- [http://www.esi-group.com/ ESI's homepage]<br />
* CFX-Post -- [http://www.ansys.com/ ANSYS' homepage]<br />
* COVISE -- [http://www.visenso.de/ Visenso's homepage]<br />
* EnSight -- [http://www.ensight.com/ CEI's homepage]<br />
* Fieldview -- [http://www.ilight.com/ Intelligent Light's homepage]<br />
*[[Tecplot]] -- [http://www.tecplot.com/ Tecplot's homepage]<br />
*ViewZ -- [http://www.zeusnumerix.com/ Zeus Numerix's homepage]<br />
<br />
=== Systems ===<br />
<br />
* ADINA -- [http://www.adina.com/index.html ADINA's homepage]<br />
* Flownex -- [http://www.flownex.com/ Flownex's homepage]<br />
<br />
== Online tools and services ==<br />
<br />
*[[CFDNet]] -- [http://www.cfdnet.com/ CFDNet homepage]</div>Aread14https://www.cfd-online.com/Wiki/AutomotiveAutomotive2007-06-15T14:58:01Z<p>Aread14: </p>
<hr />
<div>CFD related to automotive applications like external car aerodynamics, climate control, engine cooling, combustion engines, ...<br />
<br />
FEM or FDM technique can be used to find out the response of a temperature sensor mounted on exhaust gas manifold.<br />
<br />
FEM techniques are widely used to check whether a sensor mounted would withstand the engine vibration and its life<br />
{{stub}}<br />
<br />
=== Links ===<br />
<br />
Autosim - http://www.autosim.org - a collaborative project, sponsored by NAFEMS, to look at the use of simulation in the automotive industry, including CFD.</div>Aread14https://www.cfd-online.com/Wiki/Aero-acoustics_and_noiseAero-acoustics and noise2007-06-15T14:54:15Z<p>Aread14: /* Introduction */</p>
<hr />
<div>== Introduction ==<br />
Sound can be understood as the pressure fluctuation in a medium. Acoustics is the study of sound propagation in a medium; AeroAcoustics deals with the study of noise generated by air. Examples include the flow around the landing gear of an aircraft, or the buffeting noise caused when driving along with the window/sunroof open. As a result of the stringent conditions imposed on the Aircraft industries to limit noise pollution, focus is now shifting towards predicting the noise generated by a given aerodynamic flow. Similarly, in the automotive industry, passenger comfort is of great importance, so OEMs are keen to minimise unnecessary noise sources.<br />
<br />
AeroAcoustics is an advanced field of fluid dynamics in which the flow scale is removed to the acoustic levels. The first advance in the field of AeroAcoustics was made by Sir James Lighthill when he presented an &quot;Acoustic Analogy&quot;. With proper manipulation of the Euler equations, he derived a wave equation based on pressure as the fluctuating variable, and the flow variables contributing to the source of fluctuation. The resulting wave equation can then be integrated with the help of Green's Function, or can be integrated numerically. Thus, this equation can represent the sound propagation from a source in an ambient condition. With the success of the acoustic analogy, many improvements were made on the derivation of the wave equation. Two common form of the equation used in the acoustic analogy are the Ffowcs Williams - Hawkins equation and the Kirchoff's Equation. <br />
<br />
Although the Acoustic Analogy solves the problem of noise prediction to a great extent, focus is now shifting towards direct computation, in which noise is computed directly by the flow solver. Of course the acoustic analogy is still applied in far field propagation, but near field sound generation is resolved to a large extent. Large Eddy Simulation is widely used for these studies. DNS is still unuseable for problems of practical dimensions; industries require a code that can provide them results in a day, not a month. Hence, RANS based models (like JET3D by NASA) are widely used in industry.<br />
<br />
One of the main difficulties in Computational AeroAcoustics is the scale of the problem. Acoustic waves have a high velocity relative to the flow structures and, at the same time, are nearly 10 orders of magnitude smaller. Also, due to the propagation to long distances, the numerical scheme should be less dissipative and less dispersive. The CFD solvers have inherent dissipation to ensure stability. This makes most robust CFD solvers incapable of simulating acoustic flows. Advanced schemes such as Dispersion Relation Preserving (DRP) schemes, compact schemes etc., aim at a less dispersive solution. Still, given the limits of current computational capability, acoustic computation for a problem of practical interest is still out of reach.<br />
<br />
The solution adopted by the main code vendors (STAR-CD, Fluent, CFX) is to de-couple the problem: solve for the acoustic sources in the CFD code, then couple to an acoustic propagation code (SYSNoise, Actran) to discover noise levels some distance from the source.<br />
<br />
== Different Methods ==<br />
=== DNS === <br />
=== Green's Function ===<br />
=== incompressible/acoustic splitting === <br />
==Higher Order Schemes for Aero-acoustics==<br />
=== Finite Difference ===<br />
=== Finite Volume ===<br />
<br />
==Boundary Conditions ==<br />
== Reference ==<br />
<br />
{{stub}}</div>Aread14https://www.cfd-online.com/Wiki/Siemens_FAQSiemens FAQ2007-05-08T12:57:35Z<p>Aread14: /* es-tools */</p>
<hr />
<div>This section is empty. This is just a suggestion on how to structure it. Please feel free to add questions and answers here!<br />
<br />
== STAR-CD ==<br />
<br />
=== Using multiple POSDAT.F - simple trick ===<br />
<br />
Answer:<br />
<br />
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:<br />
<br />
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:<br />
<br />
INCLUDE 'POSDAT1.TXT'<br />
<br />
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. <br />
<br />
Also they cannot have the extension '.f' because star tries to compile them as separate files and ends up giving an error.<br />
<br />
=== Using scene files to produce 3D images ===<br />
<br />
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.<br />
<br />
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.<br />
<br />
=== Using PRODEFS, PROINIT and .Prostar.Defaults to customise pro-STAR ===<br />
<br />
Setup a directory and point the STARUSR environmental variable at it<br />
<br />
==== PRODEFS ====<br />
<br />
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). <br />
<br />
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.<br />
<br />
==== PROINIT ====<br />
<br />
This file controls what happens during the startup of pro-STAR, the file is read and any commands in it issued. <br />
<br />
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<br />
<br />
==== .Prostar.Defaults ====<br />
<br />
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.<br />
<br />
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<br />
<br />
== STAR-CCM+ ==<br />
<br />
=== What is STAR-CCM+? ===<br />
<br />
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 at (in May 2007) is V2.06. <br />
<br />
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.<br />
<br />
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.<br />
<br />
=== How can I try STAR-CCM+? ===<br />
<br />
Please contact your nearest CD-adapco office or agent (full list at [[http://www.cd-adapco.com]]) or e-mail CD-adapco at<br />
<br />
[[info@us.cd-adapco.com]] or<br />
<br />
[[info@uk.cd-adapco.com]]<br />
<br />
to request a trial license of STAR-CCM+<br />
<br />
You can now also download 20 example cases, with instructions on how to set-up and run and post-process the calculations.<br />
<br />
=== How do I produce an animation in STAR-CCM+ ===<br />
<br />
Animations can be produced for either a transient of steady-state calculation. <br />
<br />
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.<br />
<br />
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.<br />
<br />
// STAR-CCM+ macro: AnimatePlaneSection.java<br />
package macro;<br />
<br />
import java.util.*;<br />
<br />
import star.common.*;<br />
import star.base.neo.*;<br />
import star.vis.*;<br />
<br />
<br />
public class AnimatePlaneSection extends StarMacro {<br />
<br />
public void execute() {<br />
double xCoord ;<br />
int FileName ;<br />
String path = "/INSERT_PATH/" ;<br />
StringBuffer path2 = new StringBuffer("") ;<br />
xCoord = -1.0 ;<br />
FileName = 0 ;<br />
<br />
Simulation simulation_0 = <br />
getActiveSimulation();<br />
<br />
// select plane section<br />
PlaneSection planeSection_0 = <br />
((PlaneSection) simulation_0.getPartManager().getObject("plane section 2"));<br />
// select scene<br />
Scene scene_0 = <br />
simulation_0.getSceneManager().getScene("Geometry Scene 1");<br />
<br />
// define number of loops<br />
int counter = 150; <br />
<br />
for (int i=0; i<counter;i++) <br />
{<br />
// set and increment the X coordinate of the plane section<br />
xCoord = xCoord + 0.1;<br />
<br />
// increment the file name so that it doesn't overwrite the last one<br />
FileName = FileName + 1 ;<br />
<br />
// create the file name <br />
path2.append("PlaneSection").append(i).append(".png") ;<br />
<br />
// change the X coordinate of the plane section, leaving the others fixed.<br />
planeSection_0.setOrigin(new DoubleVector(new double[] {xCoord, -11.0, 10.98441335}));<br />
<br />
// write image file giving the name (path + path2.toString()) and the screen resolution (1068, 605)<br />
scene_0.printAndWait(resolvePath(path + path2.toString()), 1, 1068, 605);<br />
<br />
// clear path2 which contains the file name<br />
path2.delete(0,path2.length());<br />
}<br />
}<br />
}<br />
<br />
== STAR-CAD Series ==<br />
<br />
=== STAR-Design ===<br />
<br />
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. <br />
<br />
=== STAR-Cat5 ===<br />
<br />
Catia 5 plugin <br />
<br />
=== STAR-NX ===<br />
<br />
Unigraphics NX plugin<br />
<br />
=== STAR-Works ===<br />
<br />
SolidWorks plugin<br />
<br />
=== STAR-Pro/E ===<br />
<br />
Pro-Engineer plugin<br />
<br />
== es-soltiuons ==<br />
<br />
[[Category: FAQ's]]<br />
<br />
{{stub}}</div>Aread14https://www.cfd-online.com/Wiki/Siemens_FAQSiemens FAQ2007-05-08T10:03:43Z<p>Aread14: /* STAR-CCM+ */</p>
<hr />
<div>This section is empty. This is just a suggestion on how to structure it. Please feel free to add questions and answers here!<br />
<br />
== STAR-CD ==<br />
<br />
=== Using multiple POSDAT.F - simple trick ===<br />
<br />
Answer:<br />
<br />
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:<br />
<br />
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:<br />
<br />
INCLUDE 'POSDAT1.TXT'<br />
<br />
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. <br />
<br />
Also they cannot have the extension '.f' because star tries to compile them as separate files and ends up giving an error.<br />
<br />
=== Using scene files to produce 3D images ===<br />
<br />
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.<br />
<br />
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.<br />
<br />
=== Using PRODEFS, PROINIT and .Prostar.Defaults to customise pro-STAR ===<br />
<br />
Setup a directory and point the STARUSR environmental variable at it<br />
<br />
==== PRODEFS ====<br />
<br />
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). <br />
<br />
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.<br />
<br />
==== PROINIT ====<br />
<br />
This file controls what happens during the startup of pro-STAR, the file is read and any commands in it issued. <br />
<br />
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<br />
<br />
==== .Prostar.Defaults ====<br />
<br />
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.<br />
<br />
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<br />
<br />
== STAR-CCM+ ==<br />
<br />
=== What is STAR-CCM+? ===<br />
<br />
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 at (in May 2007) is V2.06. <br />
<br />
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.<br />
<br />
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.<br />
<br />
=== How can I try STAR-CCM+? ===<br />
<br />
Please contact your nearest CD-adapco office or agent (full list at [[http://www.cd-adapco.com]]) or e-mail CD-adapco at<br />
<br />
[[info@us.cd-adapco.com]] or<br />
<br />
[[info@uk.cd-adapco.com]]<br />
<br />
to request a trial license of STAR-CCM+<br />
<br />
You can now also download 20 example cases, with instructions on how to set-up and run and post-process the calculations.<br />
<br />
=== How do I produce an animation in STAR-CCM+ ===<br />
<br />
Animations can be produced for either a transient of steady-state calculation. <br />
<br />
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.<br />
<br />
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.<br />
<br />
// STAR-CCM+ macro: AnimatePlaneSection.java<br />
package macro;<br />
<br />
import java.util.*;<br />
<br />
import star.common.*;<br />
import star.base.neo.*;<br />
import star.vis.*;<br />
<br />
<br />
public class AnimatePlaneSection extends StarMacro {<br />
<br />
public void execute() {<br />
double xCoord ;<br />
int FileName ;<br />
String path = "/INSERT_PATH/" ;<br />
StringBuffer path2 = new StringBuffer("") ;<br />
xCoord = -1.0 ;<br />
FileName = 0 ;<br />
<br />
Simulation simulation_0 = <br />
getActiveSimulation();<br />
<br />
// select plane section<br />
PlaneSection planeSection_0 = <br />
((PlaneSection) simulation_0.getPartManager().getObject("plane section 2"));<br />
// select scene<br />
Scene scene_0 = <br />
simulation_0.getSceneManager().getScene("Geometry Scene 1");<br />
<br />
// define number of loops<br />
int counter = 150; <br />
<br />
for (int i=0; i<counter;i++) <br />
{<br />
// set and increment the X coordinate of the plane section<br />
xCoord = xCoord + 0.1;<br />
<br />
// increment the file name so that it doesn't overwrite the last one<br />
FileName = FileName + 1 ;<br />
<br />
// create the file name <br />
path2.append("PlaneSection").append(i).append(".png") ;<br />
<br />
// change the X coordinate of the plane section, leaving the others fixed.<br />
planeSection_0.setOrigin(new DoubleVector(new double[] {xCoord, -11.0, 10.98441335}));<br />
<br />
// write image file giving the name (path + path2.toString()) and the screen resolution (1068, 605)<br />
scene_0.printAndWait(resolvePath(path + path2.toString()), 1, 1068, 605);<br />
<br />
// clear path2 which contains the file name<br />
path2.delete(0,path2.length());<br />
}<br />
}<br />
}<br />
<br />
== STAR-CAD Series ==<br />
<br />
=== STAR-Design ===<br />
<br />
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. <br />
<br />
=== STAR-Cat5 ===<br />
<br />
Catia 5 plugin <br />
<br />
=== STAR-NX ===<br />
<br />
Unigraphics NX plugin<br />
<br />
=== STAR-Works ===<br />
<br />
SolidWorks plugin<br />
<br />
=== STAR-Pro/E ===<br />
<br />
Pro-Engineer plugin<br />
<br />
== es-tools ==<br />
<br />
[[Category: FAQ's]]<br />
<br />
{{stub}}</div>Aread14https://www.cfd-online.com/Wiki/Siemens_FAQSiemens FAQ2007-05-08T09:47:36Z<p>Aread14: /* What is STAR-CCM+? */</p>
<hr />
<div>This section is empty. This is just a suggestion on how to structure it. Please feel free to add questions and answers here!<br />
<br />
== STAR-CD ==<br />
<br />
=== Using multiple POSDAT.F - simple trick ===<br />
<br />
Answer:<br />
<br />
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:<br />
<br />
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:<br />
<br />
INCLUDE 'POSDAT1.TXT'<br />
<br />
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. <br />
<br />
Also they cannot have the extension '.f' because star tries to compile them as separate files and ends up giving an error.<br />
<br />
=== Using scene files to produce 3D images ===<br />
<br />
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.<br />
<br />
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.<br />
<br />
=== Using PRODEFS, PROINIT and .Prostar.Defaults to customise pro-STAR ===<br />
<br />
Setup a directory and point the STARUSR environmental variable at it<br />
<br />
==== PRODEFS ====<br />
<br />
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). <br />
<br />
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.<br />
<br />
==== PROINIT ====<br />
<br />
This file controls what happens during the startup of pro-STAR, the file is read and any commands in it issued. <br />
<br />
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<br />
<br />
==== .Prostar.Defaults ====<br />
<br />
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.<br />
<br />
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<br />
<br />
== STAR-CCM+ ==<br />
<br />
=== What is STAR-CCM+? ===<br />
<br />
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 at (in May 2007) is V2.06. <br />
<br />
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.<br />
<br />
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.<br />
<br />
=== How can I try STAR-CCM+? ===<br />
<br />
Please contact your nearest CD-adapco office or agent (full list at [[http://www.cd-adapco.com]]) or e-mail CD-adapco at<br />
<br />
[[info@us.cd-adapco.com]] or<br />
<br />
[[info@uk.cd-adapco.com]]<br />
<br />
to request a trial license of STAR-CCM+<br />
<br />
You can now also download 20 example cases, with instructions on how to set-up and run and post-process the calculations.<br />
<br />
== STAR-CAD Series ==<br />
<br />
=== STAR-Design ===<br />
<br />
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. <br />
<br />
=== STAR-Cat5 ===<br />
<br />
Catia 5 plugin <br />
<br />
=== STAR-NX ===<br />
<br />
Unigraphics NX plugin<br />
<br />
=== STAR-Works ===<br />
<br />
SolidWorks plugin<br />
<br />
=== STAR-Pro/E ===<br />
<br />
Pro-Engineer plugin<br />
<br />
== es-tools ==<br />
<br />
[[Category: FAQ's]]<br />
<br />
{{stub}}</div>Aread14https://www.cfd-online.com/Wiki/Siemens_FAQSiemens FAQ2007-05-08T09:44:16Z<p>Aread14: /* STAR-CCM+ */</p>
<hr />
<div>This section is empty. This is just a suggestion on how to structure it. Please feel free to add questions and answers here!<br />
<br />
== STAR-CD ==<br />
<br />
=== Using multiple POSDAT.F - simple trick ===<br />
<br />
Answer:<br />
<br />
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:<br />
<br />
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:<br />
<br />
INCLUDE 'POSDAT1.TXT'<br />
<br />
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. <br />
<br />
Also they cannot have the extension '.f' because star tries to compile them as separate files and ends up giving an error.<br />
<br />
=== Using scene files to produce 3D images ===<br />
<br />
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.<br />
<br />
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.<br />
<br />
=== Using PRODEFS, PROINIT and .Prostar.Defaults to customise pro-STAR ===<br />
<br />
Setup a directory and point the STARUSR environmental variable at it<br />
<br />
==== PRODEFS ====<br />
<br />
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). <br />
<br />
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.<br />
<br />
==== PROINIT ====<br />
<br />
This file controls what happens during the startup of pro-STAR, the file is read and any commands in it issued. <br />
<br />
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<br />
<br />
==== .Prostar.Defaults ====<br />
<br />
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.<br />
<br />
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<br />
<br />
== STAR-CCM+ ==<br />
<br />
=== What is STAR-CCM+? ===<br />
<br />
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 at (in May 2007) is V2.06. <br />
<br />
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.<br />
<br />
=== How can I try STAR-CCM+? ===<br />
<br />
Please contact your nearest CD-adapco office or agent (full list at [[http://www.cd-adapco.com]]) or e-mail CD-adapco at<br />
<br />
[[info@us.cd-adapco.com]] or<br />
<br />
[[info@uk.cd-adapco.com]]<br />
<br />
to request a trial license of STAR-CCM+<br />
<br />
You can now also download 20 example cases, with instructions on how to set-up and run and post-process the calculations.<br />
<br />
== STAR-CAD Series ==<br />
<br />
=== STAR-Design ===<br />
<br />
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. <br />
<br />
=== STAR-Cat5 ===<br />
<br />
Catia 5 plugin <br />
<br />
=== STAR-NX ===<br />
<br />
Unigraphics NX plugin<br />
<br />
=== STAR-Works ===<br />
<br />
SolidWorks plugin<br />
<br />
=== STAR-Pro/E ===<br />
<br />
Pro-Engineer plugin<br />
<br />
== es-tools ==<br />
<br />
[[Category: FAQ's]]<br />
<br />
{{stub}}</div>Aread14