# Errors on mesh with pyramid elements

**URL:** <https://pyfr.discourse.group/t/errors-on-mesh-with-pyramid-elements/501>\
**Category:** General\
**Created:** [22 November 2021 14:04 UTC](https://pyfr.discourse.group/t/errors-on-mesh-with-pyramid-elements/501 "2021-11-22T14:04:20Z")\
**Posts on this page:** 1\
**Showing post:** 31

<div class="post-metadata">

**Author:** ![WillT](https://avatars.discourse-cdn.com/v4/letter/w/bc79bd/32.png) [@WillT](https://pyfr.discourse.group/u/WillT)\
**Post date:** [13 January 2022 14:11 UTC](https://pyfr.discourse.group/t/errors-on-mesh-with-pyramid-elements/501/31 "2022-01-13T14:11:21Z")

</div>

Ok, it seems a little contradictory to me to run with filtering and flux anti-aliasing. I would just use anti-aliasing as that will probably be more accurate and doesn’t require empirical tuning. Also from your ini file, the anti-aliasing quad-deg is set to 7 for an order 4 simulation. I don’t think this is high enough for the various solution point layouts, although you’d need to check the quadrature directory in PyFR. See this post [Error associated with time step - #6 by p.vincent](https://pyfr.discourse.group/t/error-associated-with-time-step/509/6)

Did you try running with anti-aliasing and globally adaptive time stepping?

---

_[View the full topic](https://pyfr.discourse.group/t/errors-on-mesh-with-pyramid-elements/501)._