Hi Nolan,
On 17/07/2017 14:23, Nolan Dyck wrote:
> If I wanted to export all the timesteps (i.e. 0-40), then I would
> need to manually export each one, or write a script to do so.
>
> Instead of this, can we just add a command line option for the
> export argument to process all output files matching the given base
> file name? So something similar to the following command would export
> all the timesteps
Currently, the recommended way of exporting a bunch of .pyfrs files is
to use GNU parallel as:
parallel pyfr export -d5 mesh.pyfrm {} {.}.vtu ::: *.pyfrs
which is a one-liner that will export everything in parallel. Thus,
there is no means in PyFR for directly exporting a batch of files. Now,
it is true that we could improve the performance if it were all done in
PyFR for we could reuse some of the interpolation matrices. However,
even for moderately sized simulations it is simply not possible to open
up a large number of .vtu files; thus we have never investigated further.
Regards, Freddie.