|December 11, 2015, 06:59||
Error writing monitor points to file
I am performing LES of T-junction mixing flows and have placed around 300 monitor points within my computational domain. Time step used in LES is 0.2 ms and the physical time presently simulated is around 37 seconds (approx. 183000 iterations).
Over the past week I noticed that the monitor points are not written to the results file due to their size exceeding 2 GB of memory. I have attached a pdf of the error and a clip of contenets inside the .dir folder created during LES the run along with this thread. I am currently using around 240 processors to perform the LES and the computational grid has close to 7 million nodes.
I would welcome your suggestions as to how to fix this issue? Should I use more processors or is there any alternate way to fix this problem. Thanks for you help in advance.
Last edited by selvam2487; December 11, 2015 at 07:19. Reason: Additional info.
|December 11, 2015, 07:53||
Join Date: Mar 2009
Location: Sydney, Australia
Posts: 13,321Rep Power: 103
Are you using 64 bit CFX on a 64 bit OS?
Other than that I cannot suggest much except to use less monitor points, or to output less data at the monitor points. All the nodes save the monitor point data in the single file so more partitions will not help. Also you could remove some values that can be calculated as post-processing, eg if you output both pressure and absolute pressure, you could reduce that to just pressure and calculate absolute pressure as post processing.
Oh yes, and if you are confident about your convergence you could remove the convergence monitors from the file, imbalances, boundary integrals and all the other things in there by default which you might not need.
|monitor points, t junction, writing error|
|Thread||Thread Starter||Forum||Replies||Last Post|
|Problem installing swak_2.x for OpenFoam-2.4.0||towanda||OpenFOAM Installation||6||September 5, 2015 21:03|
|centOS 5.6 : paraFoam not working||yossi||OpenFOAM Installation||2||October 9, 2013 01:41|
|Annoying issue of automatic "Rescale to Data Range " with paraFoam/paraview 3.12||keepfit||OpenFOAM Paraview & paraFoam||60||September 18, 2013 03:23|
|"parabolicVelocity" in OpenFoam 2.1.0 ?||sawyer86||OpenFOAM Running, Solving & CFD||21||February 7, 2012 12:44|
|ParaView Compilation||jakaranda||OpenFOAM Installation||3||October 27, 2008 12:46|