Prevent removal of .foam cases with cleanCase function

Right now, when executing any of the ./Allclean sripts, a cleanCase function is called deleting also any files with extension .foam. These files are used for ParaView to read OpenFOAM cases, and is quite handy to keep them when debugging OpenFOAM runs. Is it possible to prevent the deletion of these files? I understand ParaFoam creates files .OpenFOAM, but we are talking about .foam files.

The idea of the Allclean (or foamCleanTutorials) is to cleanup the case. If you've run the Allclean, there probably isn't really anything left to look at or debug.

assigned to @mark

When testing complete processes (i.e. Allrun) or for debugging (need to remove old results/mesh data). It is faster to run Allclean than to remove all results and mesh data, potentially distributed in processor folders. Also, one case may have run for longer than a previous case, hence re-using the old rm command may not get rid of all results data.

I also vote for providing some means to avoid deleting .foam file

Perhaps something like cleanCase0, some version to clearAll, default call in foamCleanTutorial being minimal cleanup ?

I still think it is easier to recreate the .foam if required rather than adding in more logic and exceptions to foamCleanTutorials. Recreating the file requires more typing, but at least the logic is entirely with the user.

• touch case.foam
• paraFoam -touch -vtk

Although I usually use touch log.foam if I need some arbitrary name. This has the benefit of being automatically cleaned up by foamCleanTutorials :)

Thanks To @mark

I could clear this issue by adding alias to my csh.

alias paraview550 'touch case.foam;/hosts/punwor073/home/pss/OpenFOAM/ParaView/ParaView-5.5.0-Qt5-MPI-Linux-64bit/bin/paraview'
alias paraFoam550 'touch case.foam;/hosts/punwor073/home/pss/OpenFOAM/ParaView/ParaView-5.5.0-Qt5-MPI-Linux-64bit/bin/paraview case.foam'

The paraview550 = just creates a case.foam and I can load in paraview if needed, or it could be used to load any other formats.

Second option paraFoam550 would create case.foam and launch paraview with this case.

Note that, path to these binaries need to be included in $PATH

@Roger - are you OK with the various alternatives listed? Can we close?

closed