Hi Alex, If I remember correctly from our previous email exchange, you are using a Fourier expansion. In that case, the way I get round it, is to calculate it on the 2D mesh w/o the Fourier expansion. You will have to modify your settings.xml to convert it to 2D. The spacing will be the same in the 3rd direction. Hope this helps, Guglielmo ________________________________ From: nektar-users-bounces@imperial.ac.uk <nektar-users-bounces@imperial.ac.uk> on behalf of Alexander Schukmann <alexander.schukmann@protonmail.com> Sent: 17 April 2024 21:30 To: nektar-users <nektar-users@imperial.ac.uk> Subject: [Nektar-users] FieldConvert Surfdistance Module for Quasi-3D Simulations This email from alexander.schukmann@protonmail.com originates from outside Imperial. Do not click on links and attachments unless you recognise the sender. If you trust the sender, add them to your safe senders list<https://spam.ic.ac.uk/SpamConsole/Senders.aspx> to disable email stamping for this address. Hello everyone, in order to calculate y+ in my quasi-3D simulation of the ReD = 3900 cylinder flow benchmark, I tried the surfdistance module within FieldConvert fo calculate the height of the near-wall prism layer elements. Since surfdistance threw an error indicating that quasi-3D models are not supported, I first used the meanmode module to get a spanwise averaged planar field and then tried it again with that. However, the surface distance is equal to zero over the whole cylinder wall. In the next step I extruded my 2D mesh to 3D with NekMesh extrude utility, but receive the same results: the calculated surface distance is 0 everywhere (see attached pic) with no errors during the calculation. Am I missing something? What would be the correct way to use surfdistance? Thanks and all the best Alex[surf_dist.PNG] Sicher versendet mit Proton Mail<https://proton.me/>.