|
[Sponsors] |
![]() |
![]() |
#1 |
Guest
Posts: n/a
|
Hi Everybody,
I'd like to run StarCd in a batch mode. Which means assuming that the mesh is ok, I can, by using a Script, - change some boundary conditions, - start StarCd - get some results. Is that available with Star? Thanks for your help. Bab |
|
![]() |
![]() |
![]() |
#2 |
Guest
Posts: n/a
|
Hi, save your .prob files with different filenames - for example case01.prob, case02.prob and so on. write a script that renames those files according to your mdl file, runs star and copies the .pst file according to your .prob prefix:
assuming your star executable is named star and your case name is case, something like this will do: mv -f case01.prob case.prob star case cp case.pst case01.pst mv -f case02.prob case.prob star case cp case.pst case02.pst you should also save other files you need later on to check convergence etc. |
|
![]() |
![]() |
![]() |
#3 |
Guest
Posts: n/a
|
use ''prostar -b''
|
|
![]() |
![]() |
![]() |
#4 |
Guest
Posts: n/a
|
Thanks for your answer. I was thinking that an easier way was available.
For example, by using Fortran subroutines which calls data files for the boundary conditions. Use readbc.f which calls bc.dat. In the script, out of star, U changes bc.dat at every step of the loop. The idea is to make all the changed things out of star. Is that not ok? Do we have to compile star every step again? Compiling can also be done by the batch controler. Thanks for your answer. Bab |
|
![]() |
![]() |
|
|
![]() |
||||
Thread | Thread Starter | Forum | Replies | Last Post |
Batch Run | Akin | CFX | 11 | June 24, 2013 20:07 |
batch bug? | Prad | CFX | 0 | October 27, 2008 09:54 |
Batch | Kim Skatun | CFX | 5 | June 19, 2008 11:05 |
batch run | N.R. | CFX | 1 | June 17, 2007 22:44 |
Batch Run | Ogbeni | CFX | 4 | October 15, 2003 12:33 |