What about the continuous tavg plug-in after restart?

Cases
1

Hello, everyone, I have a question about tavg plug-in and restart functions.
I used the tavg plug-in for a long simulation, and the mode used was continuous, but unfortunately, for some reason, the calculation was interrupted.
Because my calculation is not over yet, and starting from scratch will bring a lot of extra calculation burden, I thought of the restart function.
I successfully restarted the calculation using the last pyfrs before the transient non-average interruption.
Unfortunately, after the restart calculation, the continuous function of the tavg plug-in seems to restart the calculation, which means that the first tavg after restart is very different from the last tavg before restart.
I don’t know if there is a better way to solve my problem with the restart function.
For example, use the last pyfrs of tavg before the interruption to restart the calculation? Will this make the continuous function continue to count, and in that case, can’t my transient non-average results be obtained?
As I am not familiar with the restart function, I may need help.
Thank everyone in the community for your hard work.
Best regards.

2

Please allow me to add that I just tried to use the pyfrs of the last tavg before the interruption for restart calculation, and the result failed.
Invalid solution for system is displayed, which means that only transient non-average pyfrs can be used for restart calculation. In this case, will the result of my continuous tavg start averaging again, or what? Is there any way to avoid this？
I really appreciate your help.
Regards.

3

There is functionality in the current develop version of PyFR that will enable you to merge separate time average files together.

Regards, Freddie.

4

I tried the merge functionality of the current develop version using files created with the 1.12.2 version and end up with the error
‘No option cfg-section in section: tavg’ .

The metadata was prepared slightly different in that older version. There are the options ‘tstart’ and ‘tend’ in the section ‘tavg’ instead of ‘cfg-section’ and ‘range’ in the newer version. It also has no std deviation mode.

Could you guide me in modifying the TavgCLIPlugin so that the metadata are set properly, provided that the version differences are not too distinct?

Best regards.

5

I do not recall all of the differences in the metadata but if you compare a new and old file you should be able to identify them easily enough. The metadata itself is generated here:

Regards, Freddie.