[leroyv]

Dear PyFoam users,

Some of my solvers generate big amounts of logs. When using a BasicRunner object, the script prints, on job termination, things like

Unused output: UTildeStarAverage = 3.72048262e-09
Unused output:
Unused output: Time = 82.48
Unused output:
Unused output: DILUPBiCG:  Solving for UTildeStary, Initial residual = 5.624271647e-09, Final residual = 5.624271647e-09, No Iterations 0 Unused output: DICPCG:  Solving for pTildeStar, Initial residual = 4.043827184e-07, Final residual = 4.043827184e-07, No Iterations 0

and so on. However, this data seems to be properly output to the log file. So I'm guessing it's not too serious, this is only a problem when the output vitally needs to be processed while running; am I mistaken?

[gschaider]

Originally Posted by leroyv

Dear PyFoam users,

Some of my solvers generate big amounts of logs. When using a BasicRunner object, the script prints, on job termination, things like

Unused output: UTildeStarAverage = 3.72048262e-09
Unused output:
Unused output: Time = 82.48
Unused output:
Unused output: DILUPBiCG:  Solving for UTildeStary, Initial residual = 5.624271647e-09, Final residual = 5.624271647e-09, No Iterations 0 Unused output: DICPCG:  Solving for pTildeStar, Initial residual = 4.043827184e-07, Final residual = 4.043827184e-07, No Iterations 0

and so on. However, this data seems to be properly output to the log file. So I'm guessing it's not too serious, this is only a problem when the output vitally needs to be processed while running; am I mistaken?

Yep. This means "I've seen the output but I no longer analyze it for residuals etc ... Just passing it along"

[leroyv]

Originally Posted by gschaider

Yep. This means "I've seen the output but I no longer analyze it for residuals etc ... Just passing it along"

Thank you for your answer. Would it make any sense to hide this unused output? (I saw that there is no switch to enable or disable this in the FoamThread class)

[gschaider]

Originally Posted by leroyv

Thank you for your answer. Would it make any sense to hide this unused output? (I saw that there is no switch to enable or disable this in the FoamThread class)

This output is usually generated if there is a problem (program aborted etc). I put it there to help diagnosing problems and am VERY reluctant to do any attempts to hide it. Do you get it during "regular" operations or just when aborting the program?

[leroyv]

Originally Posted by gschaider

This output is usually generated if there is a problem (program aborted etc). I put it there to help diagnosing problems and am VERY reluctant to do any attempts to hide it. Do you get it during "regular" operations or just when aborting the program?

I agree with you, my problem is very specific and suppressing this output would probably not be a good idea.

I get it during regular use, when processing a small case which requires lots of time steps. The solver generates tons of output and my guess would be that the solver is "too quick" for the output to be processed on-time. I finally wrote a very basic runner class, which doesn't monitor the running thread with another one and silently launches the binary using the subprocess.call() function and redirects the output to a log file. This is okay for the case I am running.