Automate execution of command line
 

Hi,

I would like to automate execution of command line with a script (On Ubuntu). Moreover, I want that the second line begin when the first line is finished.

For exemple :

* cd User/Cas1
* blockMesh
* snappyHexMesh
* sudo cp Cas1/0 Cas1/3 // copy of the boundary conditions
* decomposePar
* foamJob -parallel -screen simpleFoam
* reconstructPar
* cd User/Cas2
* blockMesh
* snappyHexMesh
* sudo cp Cas1/0 Cas1/3 // copy of the boundary conditions
* decomposePar
* foamJob -parallel -screen simpleFoam
* reconstructPar
* cd User/Cas2
* etc ...

Thanks all for your help

That's the default behaviour. Just put all the commands from above in a file that starts with the line "#!/bin/bash", and then run "chmod +x [scriptname]" to make the file executable. That's it.

Ok.

The file is a text file (.txt) ?

The file is plain text, but the extension is not important. I usually end them in .sh, but if you prefer you can use .txt, or no extension at all.

Ok, thanks.

Edit : It works :)

Is it possible to use the script to modify the parameters of velocity inlet in the text file ?

Yes. Learn how to use sed or awk to manipulate text files.

That is a possibilty. Although these straight replacements always have to make an assumption about what they have to replace ("look for value 42 and replace it with the inlet velocity"). I personally find a solution similar to http://openfoamwiki.net/index.php/Co...ions_for_walls much easier to maintain (but of course I'm not objective)

But of course sed has the advantage to be installed everywhere

What did you think about gnu m4 ? (
http://www.somogyibence.hu/documents...ckMesh_m4.html)

Sincerely hate it since I had to configure a sendmail-server. But I'm a man of many prejudices, so don't take my word.

Seriously: I think the main purpose of M4 is generating text files, not analyzing them. So it might be just the opposite of what you're looking for

Ok, thanks for your response.

Have you an example of BlockMesh script ? (Example of your script wrote with PyFoam)

Have a look at slide 42ff of http://web.student.chalmers.se/group...amAdvanced.pdf

I'm planing to add a more sophisticated templating-mechanism to later versions of PyFoam

Dear All,

pardon the question, but I think that this does not work.

In fact I have my launch.sh file which is the following:

The problem is that the reconstructPar starts before the foamJob -p buoyantPimpleFoam is ended.

Any idea about that?

Thanks a lot,
Samuele

Hi

foamJob sends the solving process to the background and redirects its output to a log file, hence your following commands get to start as soon as the case starts.

Dear Pablo,

thanks for answering.

I know that it is as you say, i.e. that foamJob solves in BG.. What I would like to know is if it is possible to launch all the commands that I give in BG on a server, executing them one after the other.

Thanks a lot,
Samuele

Hi

it is very easy:

where you just have to change the number of processors.

Regards

If I give the command you suggested (i.e. mpirun -np 8 buoyantPimpleFoam -parallel > log), I'll launch the program in foreground and when I close the terminal where I am running it, the execution stops.

Let me try to explain what I wanna do: maybe you can help me.

I am performing some simulations on a server. I connect via ssh, from my laptop.

The point is that if I am working in serial, I can give and then and then .

With mpirun, this syntax doesn't work, hence I user foamJob.

What should I do, to you?

Thanks a lot,
Samuele

Use the nohup command before mpirun. This makes it ignore the "death" of the shell

If I understood well, I can write a launch.sh file like this:

Is that correct?

Thanks a lot,
Samuele

Greetings to all!

@samiam1000: The first line shouldn't have quotes:
There is a major flaw in your current script: "foamJob -p" will launch and run in the background automatically, leading the rest of the script to executed immediately after foamJob is executed. A quick fix would be to run with "foamJob -s -p".

By what I can understand, it's not foamJob that needs nohup, it's the call to this script that needs this! For example, if you call this script "runcase.sh", you'll need to:

1. The script should be something like this:
   
   Code:

   ---

   #!/bin/bash

foamJob -s -p buoyantPimpleFoam

reconstructPar

cd ../1DegNew/

mapFields -consistent ../1DegStartNew -sourceTime 100

decomposePar

buoyantPimpleDyMFoam_MS

sed -i 's/1/2/' system/controlDict

buoyantPimpleDyMFoam_MS

sed -i 's/2/3/' system/controlDict

buoyantPimpleDyMFoam_MS

sed -i 's/3/4/' system/controlDict

buoyantPimpleDyMFoam_MS

sed -i 's/4/5/' system/controlDict

buoyantPimpleDyMFoam_MS

sed -i 's/5/6/' system/controlDict

   ---

2. After you edit and save the script for the first time, make sure it is an executable script:
   Code:

   ---

   chmod a+x runcase.sh

   ---

3. Then for running the script:
   Code:

   ---

   nohup ./runcase.sh

   ---

Last but not least, why aren't you following the examples shown in the tutorials? For example, see "incompressible/simpleFoam/turbineSiting/Allrun". The downside of this example is that it will only run in the machine where it is launched...


Best regards,
Bruno

No. I was answering the mpirun-issue. I don't use foamJob so I can't comment on your script