Dear all, My name is Antonio Garcia-Uceda, and I'm a researcher working on Flux Reconstruction Methods.
I have a question about the "Anti-Aliasing" technique available in PyFR in order to improve the stability of the method. I see there are several options available, so as to apply over-integration of the fluxes in the cell (<<flux>>), interfaces (<<surf-flux>>), or div_flux (<<div-flux>>) in the cell, or coupling some of these together (<<flux | surf-flux>>, ...). Could you please let me know the difference in between these different options? I mean, Are there particular cases where an option turns out to be more efficient than the others in enhancing the stability? Which option do you users of PyFR utilise most often? Also, which option is more efficient in terms of computational time? Finally, I've seen that the combined options (<<flux | div-flux>>, ...) are broken in PyFR (I get the following error message when launching PyFR: "Invalid anti-alias option", which is an Exception raised in shapes.py). Is this normal, or perhaps I''m setting something wrong in the .ini file? Thanks a lot in advance for your help. Best regards, Amntonio -- 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.
