OpenFOAM-plus issueshttps://develop.openfoam.com/Development/OpenFOAM-plus/-/issues2018-12-19T11:30:09Zhttps://develop.openfoam.com/Development/OpenFOAM-plus/-/issues/1129paraFoam displays 'internalMesh' after any patch groups in the 'Mesh Parts' s...2018-12-19T11:30:09ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comparaFoam displays 'internalMesh' after any patch groups in the 'Mesh Parts' selectioninternalMesh used to be first. Is this wanted?internalMesh used to be first. Is this wanted?v1906Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/OpenFOAM-plus/-/issues/1103Misleading Log Info: fieldAverage timeStart Option2018-12-01T15:33:04ZKutalmış BerçinMisleading Log Info: fieldAverage timeStart Option### Summary
When **fieldAverage** functionObject's *timeStart* is *on*, the solver misleadingly informs the user as if the averaging is started:
For example:
```
functions
{
fieldAverage1
{
type fieldAver...### Summary
When **fieldAverage** functionObject's *timeStart* is *on*, the solver misleadingly informs the user as if the averaging is started:
For example:
```
functions
{
fieldAverage1
{
type fieldAverage;
libs ("libfieldFunctionObjects.so");
writeControl writeTime;
timeStart 60;
...
```
The solver informs the user at 0 time-step with the following:
```
fieldAverage fieldAverage1:
Restarting averaging for fields:
U: starting averaging at time 0
p: starting averaging at time 0
yPlus: starting averaging at time 0
wallShearStress: starting averaging at time 0
```
### Steps to reproduce
Please run `tutorials/incompressible/pimpleFoam/LES/channel395DFSEM` case.
### What is the expected *correct* behavior?
The solver should inform the user that the averaging will start at time **timeStart** of **fieldAverage**.