fieldAverage fails to continue averaging the fields
2 Attachment(s)
Hi there dear Foamers,
I am currently running some simple LES cases and I wish to, during runTime, average some fields of interest. For instance I'm using fieldAverage in my controlDict in the following way Code:
funtions Could any expert or someone who has already experienced a similar situation advise me? Thanks in advance and best regards, F. Soares. |
Quick answer: I vaguely remember there was a bug related to this in one of OpenFOAM's older versions. I've found the bug report for it: http://www.openfoam.org/mantisbt/view.php?id=898
Which version of OpenFOAM are you using? |
Sorry, I should have attached the other threads I was reading about this issue. I currently use OpenFOAM 2.4.x.
|
A few quick questions:
|
According to 'blockMesh -help' I am currently
Code:
Using: OpenFOAM-2.4.x (see www.OpenFOAM.org) Code:
/*--------------------------------*- C++ -*----------------------------------*\ Once again thank you for your time and patience Mr. Santos, F. Soares. |
I forgot to address a similar tutorial in my last reply. In $FOAM_TUTORIALS/incompressible/pisoFoam/les/pitzDaily there is a similar structure to the case I am trying to run here. However modifying the controlFidct file
Code:
/*--------------------------------*- C++ -*----------------------------------*\ Code:
Starting time loop |
Hi F. Soares,
This is starting to look like it's a somewhat severe bug. The case you prepared with the tutorial has the function objects prepared differently and that could be enough for the first one to not conflict with the second one, given that you gave two different start times and different averaging mechanisms. And I went looking for bug reports about "fieldAverage" and found the following issue still open: http://www.openfoam.org/mantisbt/view.php?id=1336 - it seems to be related to your issue. I'm adding this to my to-do list for the upcoming weekend. If you can figure out a way to reproduce this issue with the tutorial case, it would help a lot in isolating the origin of the problem and to fix it. The other possibility for the origin of this bug is if you are running in parallel at the University, which could potentially also bring up other problems. Best regards, Bruno |
All times are GMT -4. The time now is 20:26. |