Hi Zach, Freddie, Peter, Thanks a lot for your reply! In particular to Zach, it did help a lot your reply to start the code running. I have some other technical questions:
- "order 1" corresponds to p=1 or p=0 (scheme order 1)? - Is it possible to monitor residuals? I see it's required to input dt... Isn't there a Global or Local time stepping scheme available? - How to specify the maximum time steps to run / convergence criteria? - If trying to run in parallel... Is it required to partition the .gmsh in as many blocks as procs to be used? - If I want a specific output (let's say the L2 norm of entropy error on Euler cases). Is it possible to input in the .ini file? If not, Where in the code should I implement this output? The first attempts to run this case with pyFR do not look like making any evolution of the solution in time. Perhaps I'm not setting correcltly the time integration scheme/ BCs... Could you please have a look and tell me whether it's OK? Thanks a lot for your help. On the other hand, if I want to set periodic boundary conditions (not for this case though...) How should I specify the Boundaries in the .ini and .gmsh files? I see in the "euler_vortex" case uploaded in the website that no "bcs" tags are specified. Is it on the other hand necessary to name the boundaries in any way inside the .gmsh file? Thanks once more! Best regards, Antonio On Thursday, March 12, 2015 at 11:12:35 AM UTC+1, Vincent, Peter E wrote: > > Zach, Freddie - thanks for the input! > > Antonio - please let us know if it helps. > > Cheers > > Peter > > Dr Peter Vincent MSci ARCS DIC PhD > Senior Lecturer and EPSRC Early Career Fellow > Department of Aeronautics > Imperial College London > South Kensington > London > SW7 2AZ > UK > > web: www.imperial.ac.uk/aeronautics/research/vincentlab > twitter: @Vincent_Lab > > > > > > On 11 Mar 2015, at 20:24, Freddie Witherden <[email protected] > <javascript:>> wrote: > > > Hi Antonio, > > > > On 11/03/15 17:34, Antonio Garcia-Uceda wrote: > >> - When runninf the .ini file attached, an error pops-up with the > >> following: "ValueError: Invalid characters in expression". What is > wrong > >> with it? > > > > Underscores are not supported as variable names inside the .ini file. > > When these are used inside of the initial condition expressions they > > give rise to the invalid characters in expression error. > > > > For those that are interested: we disallow underscores as it greatly > > simplifies the logic required to ensure that initial condition > > expressions are valid. If we did allow underscores then more work would > > be required to ensure that the expression does not contain something > > naughty in an attempt to execute arbitrary code: > > > > <http://nedbatchelder.com/blog/201206/eval_really_is_dangerous.html> > > > > Disallowing underscores and other 'fun' characters permits us to safely > > use eval(). This is an order of magnitude simpler than pulling in a > > proper expression evaluation library (or, worse still, rolling our own > > with a custom parser/syntax tree). > > > > 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 an email to [email protected] > <javascript:>. > > Visit this group at http://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 http://groups.google.com/group/pyfrmailinglist. For more options, visit https://groups.google.com/d/optout.
sphere_lev2o1_o1.ini
Description: Binary data
