Hi Varun,
Is there any chance you could email through the attachments as a zip or change the extensions to .txt? Our outlook policies unfortunately block xml files automatically so we can't download the session/mesh files to see what might be causing the issue.
Looking through the backtrace gives a good first hint of the error however. The error happens in SpatialDomains when trying to initialise the Driver Object. So would suggest its most likely a configuration error in the session file. Either something with the composites/boundaries or a combination of parameters that might not be available. But again, this is just a first guess from the backtrace. Maybe look at the mesh file and grep the composites tag and grab all the lines after that. Then make sure each of the composites you have in in that tag are present in BoundaryRegions in the session file. Other than that - are you using a different Driver than default?
If you can send through those files - someone should be able to take a look for you.
Thanks!
Kind Regards,James Slaughter.
From: nektar-users-bounces@imperial.ac.uk <nektar-users-bounces@imperial.ac.uk> on behalf of Kumar, Varun <varun_kumar2@brown.edu>
Sent: 10 August 2022 17:58
To: nektar-users <nektar-users@imperial.ac.uk>
Subject: [Nektar-users] Error in solving compressible NS equation with NACA airfoil
This email from varun_kumar2@brown.edu 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 to disable email stamping for this address.
Hi all,
I am trying to study compressible flow over a NACA airfoil with Nektar++ and I am seeing a Segmentation fault while running the simulation. The steps for creating the simulation are as follows:
- Create mesh in GMSH (File attached)
- Convert GMSH to Nektar++ compatible format using NekMesh
- Setup the session file as per problem statement (Session file attached).
I would appreciate any help that I can get with this in trying to understand the source of this error.
--ThanksVarun