Hi Antonio, I’ve looked over both your PyFR configuration file and your mesh. With regards to your boundary conditions you have specified a supersonic inflow farfield boundary condition, a subsonic inflow characteristic boundary condition, and a slip wall boundary condition for your mesh. Note you have specified the type (with underscores instead of hyphens) instead of the actual name of the boundary. With PyFR you need to provide the boundary names as given in the mesh file. Then the boundary condition type is specified separately. As an example for a no-slip adiabatic surface using the name you have given your surface, “Slip_Wall”, an appropriate boundary condition setting might be:
[soln-bcs-Slip_Wall]
type = no-slp-adia-wall
I’m not sure whether a more appropriate slp-adia-wall or symmetry boundary
condition has been implemented in PyFR for your specific situation yet. There
is the char-riem-inv boundary option, but I believe that is intended for use at
freestream outer boundaries. If there is a more suitable inviscid wall
boundary, then I’m not sure it has reached the documentation. Give the types of
flows PyFR is aimed at solving, it wouldn’t surprise me if this isn’t an
option. I’m also not sure whether the boundary condition names can include
underscores or recognize lower and upper case characters. Something that might
be worthwhile stating explicitly somewhere in the documentation. I tend to
stick with lower case names.
It appears you’re using SI units wherein u_inf has been set to 100 m/s, p_inf =
101325.0 Pa, and rho_inf = 1.2 kg/m3. This gives a Mach number ~ 0.3 which
really isn’t supersonic flow, so you are much better off creating separate
subsonic inflow and subsonic outflow boundaries in your model. In Gmsh, if you
labeled the inflow boundary inflow, then an example for specifying this
boundary in PyFR’s configuration file would be:
[soln-bcs-inflow]
type = sub-in-frv
rho = 1.0
u = 0.355
v = 0.0
w = 0.0
Here I’ve normalized/non-dimensionalized rho, u, v, and w by some reference
values (e.g. u = 100m/s/[mach*sqrt(gam)]).
I also noticed in your solver-interfaces-quad and solver-elements-hex
declarations that you have included a parameter vcjh-eta (probably related to a
Vincent, Castonguay, Jameson, Huynh term), but this doesn’t appear in the
documentation either. Lastly, I noticed that you set the order for the solver
in your configuration file for the simulation to 1. You might consider changing
this value to 3rd or 4th order since this is one of the advantages of Flux
Reconstruction after all..
These are just some of the things I noticed straight away, but I’m sure the
experts may have other comments as well.
Best Regards,
Zach Davis
Rescale, Inc.
944 Market Street, Ste. 300
San Francisco, CA 94102
[email protected]
P: (855) 737-2253
> On Mar 11, 2015, at 10:34 AM, Antonio Garcia-Uceda
> <[email protected]> wrote:
>
> Dear all,
>
> My name is Antonio Garcia-Uceda, and I'm a researcher on Flux Reconstruction
> methods. I'm using pyFR as part of my project.
>
> I'm trying to perform the euler case: subsonic flow around a sphere. You can
> find attached the mesh in .gmsh format, as well as a first attempt of .ini
> files.
>
> Could you please help me out with the following? Thanks.
>
> - When running pyFR, an error pops-up asking for the following:
> [soln-bcs-sup_in_fa], [soln-bcs-sub_in_char], [soln-bcs-slip_wall]. The mesh
> attached only has two boundary faces: Slip-Wall, Subsonic Characteristic.
> What is the other BCs required? How pyFR detects the correct type? Perhaps I
> have to input the correct "physical name" in the .gmsh file? If so, which is
> this one? I can't find anything related in the user guide section of pyFR
> website.
>
> - The bcs of type: [soln-bcs-sub_in_char] is not in the user guide. Could it
> be that I'm running a too old version of the code?
>
> - When runninf the .ini file attached, an error pops-up with the following:
> "ValueError: Invalid characters in expression". What is wrong with it?
>
> Many thanks in advance for your help.
>
> Best regards,
> Antonio
>
> --
> 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 http://groups.google.com/group/pyfrmailinglist
> <http://groups.google.com/group/pyfrmailinglist>.
> For more options, visit https://groups.google.com/d/optout
> <https://groups.google.com/d/optout>.
> <sphere_lev2o1_o1.ini><Sphere_lev2_o1.msh>
--
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.
signature.asc
Description: Message signed with OpenPGP using GPGMail
