Site will likely be offline for maintenance 27/28 March - more details soon
Lots of updates migrated from internal development line
Old code maintained a list of file pointers, and provided a clunky interface to output to file. Although OK for function objects that only created a single file, those that created multiple files were required to refer to each by an index and making it very easy to introduce errors. The new code simplifies the functionObjectFile class so that it provides helper functions to create and write to files, and no longer maintains a list of file pointers. Instead, each function object must create and take responsibility for all of the file streams that it requires. Changes propagated across dependencies:
Previously, if function objects required to store data on disk to enable smooth restarts, e.g. fieldAverage, the object would need to provide the mechanism for reading/writing state information itself. This class abstracts out the reading/writing of state information in a straightforward manner, whereby an object can retrieve its own data, or retrieve e.g. the latest available data from another object (e.g. see fieldValueDelta).
New function object to generate images at run-time, or in 'post-processing' mode via the execFlowFunctionObjects utility