Control model verbosity when there are many wall patches
timofeymukha opened this issue · 2 comments
Hey Timofey,
I just came across the following issue (not sure if it is one). Checking the log-data we get the Wall modelling time consumption (I guess for each patch?). However, which time is it? Actually, one time-step is around 2s. However, comparing the modelling time consumptionis around 50 s? So I am not sure to which time this refers to (without checking the code in more detail).
Furthermore, wouldn´t it make sense to put such information more into a postProcessing folder or give the possibility to activate/deactivate it.
And finally, why are there only a few patches at which the SampledVelocityField::sample is executed?
@shor-ty Tobias, I am moving everything to Github, including issues. Tagging you here.
Verbosity can now be controlled with the silent parameter. Messaging about sampling are only in the log if the debug switches for the classes are on. Saving the wall model execution time to a file is planned for development. Closing for now.