OpenFoam logfile compression tip
Hi all!
Making simulations in OpenFoam sometimes I get really huge log files. In some cases it can result in hard drive freespace running out! But all information can be useful afterwards and I cannot just redirect output to /dev/null. So it is necessary to compress output on the fly. One solution in Linux OS is piping it to gzip/bzip2: openfoamSolver 2>&1 | gzip > log.gz But worst thing is that gzip blocks log.gz pipe for reading during simulation and one cannot get access to log data until task is finished! The solution is to use "compress" package. To obtain it in Ubuntu use sudo apt-get install ncompress Then it is possible openfoamSolver 2>&1 | compress > log.Z or make run script, containing Code:
#!/bin/sh |
Continue with logfile
Hi! great post tip, btw..
My problem is a bit different though: I would like to know how it is possible to continue a logfile of a simulation that was interrupted and I wish to resume with the same logfile, without erasing the previous timesteps. Thx Jose |
Quote:
Code:
foamProgram >> logFile |
Great! many Thx
Regards |
Compress VTK files
Thanks for the compress tip!
In line with compression of data files, another question. I commonly create output sample planes using the function object libfieldFunctionObjects.so. The problems is that the planes are only written in uncompressed ascii, so a lot of data is generated (especially for isocontour). An example Code:
PlanesVTK Thanks! Regards, Eelc |
Hello,
have you had any luck exporting slices in vtk binary format?Thanks, matteo |
Hello,
this is very interesting and may be of great helpt to me. The problem is I don't really understand how you proceed with this compressed file. I mean normally one wants to extract data from this file during runtime (e.g. for plotting residuals). For doing this I need to extract the file and I am as far as before. What am I missing here? Best regards, Kate Quote:
|
Edited the log file on a server
Hello,
By mistake I have edited the solver.log output file in the running case. Now the case is running for 65 hours and it is scheduled to run for 300 hours more. The issue is solver.log file is not getting updated anymore. Although I am monitoring the residuals through residuals function object, but I want to see the number of PIMPLE iterations being used so that I can update my Courant Number. Can anyone suggest the way to restart the output log file? |
Quote:
|
All times are GMT -4. The time now is 15:33. |