[MikeHersee]

Hi, I've just (eventually) successfully installed OpenFOAM having never used it or any other CFD software previously, or even Linux to anything other than a trivial extent before. (But why not start on a new operating system with the most complex application possible, eh? What could possibly go wrong?) Anyway, I'm following the first OpenFOAM tutorial at http://openfoam.org/docs/user/cavity.php#x5-40002.1 .

I've worked my way round the fact that the 'Display' tab doesn't exist anymore in Paraview and has been absorbed into the 'properties' tab, and I believe I've successfully updated the thing that gets updated when you click on 'Accept', whatever it is. But when I go back to the terminal window and type icoFoam, it just sits there until I exit from paraview. ie, it appears that there is a record or file lock preventing IcoFoam from running. This isn't apparently what is supposed to happen, as according to the tutorial, icoFoam is supposed to run and update the data that Paraview is looking at, if I've understood it correctly.

When I exit paraview, icofoam suddenly takes off and spews a load of data at the terminal window that looks like a successful run. But when I go back into paraview, I can't seem to work out how to get at the data it has apparently produced.

I'm running a fresh installation of Linux Mint 17.1, which is based on Ubuntu 14.04, and OpenFOAM 2.3.1 with Paraview 4.1, all installed according to the instructions. Any help very much appreciated.

[alexeym]

Hi,

Your confusion comes from the fact that terminal will echo what you're typing while paraview is running but won't execute what you've typed until you exit paraview.

So to resolve this "issue", you can a) send running paraview in background (using Ctrl-Z shortcut and bg command), or b) run paraFoam using

$ paraFoam &

this will send paraview in background from the very beginning, or c) execute paraFoam in separate terminal.

[MikeHersee]

Thanks Alexey, that has worked. Still can't get the data to be displayed, but that's a different issue now, apparently due to differences in version of paraview, that the instructions don't answer....