Hi Nolan, Thanks for your interest in PyFR.
I’m not sure I follow. Paraview can’t, at the moment, read in native .pyfrm/s files - you have to convert them to .vtu files using pyfr export (which involves linear sub-sampling of the fundamentally polynomial solutions) - so it’s not just a case of changing output naming conventions (which I think we can control anyway?) Sorry if I missed your point! Cheers Peter On 17 Jul 2017, at 15:48, Nolan Dyck <[email protected]<mailto:[email protected]>> wrote: So it seems like the default output behaviour of PyFR should remain as-is for the reasons mentioned above, but I'm wondering if an extra option could be added to the ini file to adjust the naming conventions of the output files so that Paraview can load it as a time series? I'd be happy to handle this change. Nolan On Thursday, December 15, 2016 at 2:55:00 AM UTC-5, Vincent, Peter E wrote: Hi Jonny, Regarding: Interesting! When you say PyFR isn't really used for simulations of sufficient scale, I think you mis-read Freddie’s message, which said: In general, the kinds of simulations that PyFR is used for are of sufficient scale that it is simply not practical to work with more than a single solution file at a time. Typical simulations are of such scale that lumping a time series into a single file is not practical/sensible. Typically what we do is script paraview to process a series of individual files and produce an animation. And more recently we have been working to add in-situ vis capabilities such that PyFR can generate images, to make an animation, on-the-fly as the simulation proceeds. They latter approach significantly reduces the amount of data written to disk. Peter Dr Peter Vincent MSci ARCS DIC PhD Reader in Aeronautics and EPSRC Fellow Department of Aeronautics Imperial College London South Kensington London SW7 2AZ UK web: www.imperial.ac.uk/aeronautics/research/vincentlab<http://www.imperial.ac.uk/aeronautics/research/vincentlab> twitter: @Vincent_Lab<https://twitter.com/Vincent_Lab> On 14 Dec 2016, at 16:00, Jonny Hyman <[email protected]<javascript:>> wrote: Interesting! When you say PyFR isn't really used for simulations of sufficient scale, do you mean computationally, spatially, or based on complexity? It seems to me that the flux reconstruction approach should be scalable to many different flows, so I'm a bit confused as to what you mean. :) Thanks so much for your helpful information! You guys are the best! On Tuesday, December 13, 2016 at 10:04:35 PM UTC-8, Freddie Witherden wrote: On 13/12/2016 21:02, Jonny Hyman wrote: > I'm doing some simple tests to get acquainted with PyFR. > > I would like to have a *time playback *in Paraview? I can get the single > solutions from the .pyfrs files and the export functionality to .vtu, > but I'm not super clear on how to make a 4-dimensional simulation - > effectively mashing all of the pyfrs solutions into one file or set of > arrays which can be played back over time. > > Does anyone have tips? I may just write a Python script to merge all of > the data in the .pyfrs files into a time dependent vtu but I don't want > to go through the trouble if there's some simpler solution. You should be able to open up all of the .vtu files at once in ParaView and then step through them using the built in UI. In general, the kinds of simulations that PyFR is used for are of sufficient scale that it is simply not practical to work with more than a single solution file at a time. As such there has been no work around merging multiple files together. Regards, Freddie. -- You received this message because you are subscribed to the Google Groups "PyFR Mailing List" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]<javascript:>. To post to this group, send email to [email protected]<javascript:>. Visit this group at https://groups.google.com/group/pyfrmailinglist. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "PyFR Mailing List" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]<mailto:[email protected]>. To post to this group, send email to [email protected]<mailto:[email protected]>. Visit this group at https://groups.google.com/group/pyfrmailinglist. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "PyFR Mailing List" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send an email to [email protected]. Visit this group at https://groups.google.com/group/pyfrmailinglist. For more options, visit https://groups.google.com/d/optout.
