Writing report files and creating report definitions.

cfd_worker99 · March 13, 2019, 16:20

Hi,
I am solving a transient heat transfer case in fluent and ran into a small but extremely annoying impediment with regard to Post processing in Fluent.
I have setup a number of planes (300 in total). I calculate the area-weighted average temperature on each of the planes. As setting up individual monitors at each of these planes will be cumbersome, I use report definitions and then have these compiled in report files which are then generated as .OUT file.
It was all working perfectly, but for some reason, after the 1423 timesteps, the file stopped recording. The solution files still went On and the data files were saved but not the .OUT files.
I am now trying to fix this but so far nothing is working. I am able to create individual monitors and store them but the reports file just do not get recorded. Can you please help. :-(

AlexanderZ · March 13, 2019, 20:33

you may try to change .out to .dat =)))

it is possible to write scheme code to write data in file

best regards

MKuhn · March 14, 2019, 10:00

That is strange. Try to find out if it is a size problem. Split it in two files or write the data only every second time step. I record data over 5000 time steps (but not 300 planes) in *.txt instead of *.out and it works. But I think it has nothing to do with the file extension.

kjoshi2 · June 12, 2020, 12:55

Hello,
I am having same issue while fluent writes .out report files.
@ cfd_worker99 - were you able to solve it? was it some size issue?

March 13, 2019, 16:20	Writing report files and creating report definitions.	#1
cfd_worker99 New Member Lisa Join Date: Apr 2017 Location: USA Posts: 19 Rep Power: 9	Hi, I am solving a transient heat transfer case in fluent and ran into a small but extremely annoying impediment with regard to Post processing in Fluent. I have setup a number of planes (300 in total). I calculate the area-weighted average temperature on each of the planes. As setting up individual monitors at each of these planes will be cumbersome, I use report definitions and then have these compiled in report files which are then generated as .OUT file. It was all working perfectly, but for some reason, after the 1423 timesteps, the file stopped recording. The solution files still went On and the data files were saved but not the .OUT files. I am now trying to fix this but so far nothing is working. I am able to create individual monitors and store them but the reports file just do not get recorded. Can you please help. :-(

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
[mesh manipulation] How to write cellSet for different regions in constant/polyMesh/sets	Struggle_Achieve	OpenFOAM Meshing & Mesh Conversion	3	June 17, 2019 09:29
[snappyHexMesh] Creating multiple multiple cell zones with snappyHexMesh - a newbie in deep water!	divergence	OpenFOAM Meshing & Mesh Conversion	0	January 23, 2019 04:17
[mesh manipulation] Importing Multiple Meshes	thomasnwalshiii	OpenFOAM Meshing & Mesh Conversion	18	December 19, 2015 18:57
Possible Bug in pimpleFoam (or createPatch) (or fluent3DMeshToFoam)	cfdonline2mohsen	OpenFOAM	3	October 21, 2013 09:28
UDF issue	MASOUD	Fluent UDF and Scheme Programming	14	December 6, 2012 13:39

March 13, 2019, 20:33		#2
AlexanderZ Senior Member Alexander Join Date: Apr 2013 Posts: 2,363 Rep Power: 34	you may try to change .out to .dat =))) it is possible to write scheme code to write data in file best regards

March 14, 2019, 10:00		#3
MKuhn Senior Member Moritz Kuhn Join Date: Apr 2010 Location: Germany, Dresden Posts: 207 Rep Power: 17	That is strange. Try to find out if it is a size problem. Split it in two files or write the data only every second time step. I record data over 5000 time steps (but not 300 planes) in .txt instead of .out and it works. But I think it has nothing to do with the file extension.

June 12, 2020, 12:55		#4
kjoshi2 New Member Ketaki Join Date: Apr 2018 Posts: 1 Rep Power: 0	Hello, I am having same issue while fluent writes .out report files. @ cfd_worker99 - were you able to solve it? was it some size issue?