[grnahas]

I am trying to do the temporal mean with TempMean for the wall shear stress in my geometry. The problem is that Ensights gives that the wall shear stress and the average over time are the same which I know it cannot be true as the wall shear stress definitely varies over time.

Anyone has an idea what my be the problem or what I might be doing wrong? I think that Ensight is not actually doing the integration over time and is only considering one time step.

For information, when I try showing my solution in different time steps I get this error:

Error> {s1:1} readensight_fvar_sect_ptrs() in resu.c:10690 of EnSight Server 9.2.2(f):
Error referencing invalid condition.
Not EOF, expecting part id in variable file.
Possible extra white space appended to record data file<truePressure.****.scl>, at EnSight (0-bias)

[kevincolburn]

It sounds like your variable from exported from Fluent has been corrupted/incorrectly written. To check into this further, as it is EnSight format files, you can use the utility 'ens_checker92' and provide the .encas file that you have. This utility will check the file for format integrity, and report back any errors. From here, we can determine which variable, which timestep, and what might be the issue and potential resolution options.

It does sound like there is a corrupt/invalid file, and therefore the TempMean aborted (resulting in not completing the routine for temporal mean). Feel free to reach out to your local EnSight support agent, or the main support (support@ensight.com).

-Kevin

[grnahas]

Kevin,

Thank you so much for your reply. I will try checking if files are corrupted, but I do not think so. I am using an in housing software and I have rerun simulations to make sure that the files are not corrupted, but I am still getting the same error.

"Error referecing invalid solution"

[kevincolburn]

Okay. Couple of things to check:
a. have you run the "ens_checker92" utility on this dataset? This will check for issues with the files themselves. 99% of the time, this points to where the issue is.
b. Is your model changing variables only, or it is also changing connectivity? (checking the geometry line in your case file will indicate this). TempMean cannot work with a model which is indicated to be changing connectivity.

-kevin

[grnahas]

a) Yes, I checked. No problem with the files.
b) I have a fixed geometry and a fixed mesh so TempMean should work.

[kevincolburn]

Hmm. Not sure what else I can suggest on your end to do. EnSight 9.2 is going back a ways, and not sure if there were any issues with the TempMean routine. If you are able, you might want to try updating to a recent release of EnSight. Are you able to share the data files us here at CEI? I am sure that we can find the reason for the problem if we were able to dive into the dataset itself.

-Kevin