libFieldFunctionObjects writeInterval

In the v1712 release the following libFieldFunctionObjects

dummy
{
    type    wallShearStress;

    libs ("libfieldFunctionObjects.so")

    writeControl    timeStep;
    writeInterval   1e+06;
    writeFields no;

    patches ("board.*");
    log     no;
}

writes the wallShearStress field in the case directory every time step. The same controlDict sintax worked fine for the same case with the 2.4.0 version, with the field object written every specified write interval (using outputInterval in the old version).

changed the description

By Riccardo Rossi on 2018-05-27T22:20:54 (imported from GitLab project)

1712 works as expected, no? IMHO, with writeControl writeTime;, the field can be written at the write intervals. @Ricky-11

I've tried with "writeControl writeTime" and the wallShearStress field is still written every time step. In the 2.4.0, using "writeControl timeStep" the field is written every integer specified by "writeInterval". @kutalmisbercin

By Riccardo Rossi on 2018-05-28T14:44:53 (imported from GitLab project)

Ah, a semicolon was missed at the end of this: libs ("libfieldFunctionObjects.so")

It should be libs ("libfieldFunctionObjects.so");

Tested with tutorials/incompressible/simpleFoam/T3A, now works:

dummy { type wallShearStress; libs ("libfieldFunctionObjects.so"); writeControl writeTime; log no; }

Hope this helps :) @Ricky-11

Yet I would expect, a missing semicolon would raise error? I also removed semicolons of each entry of dummy in turn: writeControl writeTime and log no resulted no IO error, but type wallShearStress did. Might be useful to be considered by the OpenFOAM developer team.

It helped indeed @kutalmisbercin . Sorry for missing the semicolon. Now is working fine but yes, I would expect an error for this scenario so definitely worth taking a look by the devel team.

By Riccardo Rossi on 2018-05-28T23:21:42 (imported from GitLab project)

• Cross-reference to issue #762 (closed) about some of the difficulties. It would indeed be really nice to solve.

closed

Closed as being related to input error, not wallShearStress itself.

mentioned in commit 2549500d090d30d972ba193af6db9a1a32d3e7ee