******************* This email 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. ******************* Hi Jeremy, Thanks very much for looking into this. I had since also cloned the repo and compiled on a CentOS 7.7.1908 machine. That had also raised a segmentation fault. I've now done a "git pull upstream master" to 707783cc647b64b25f3b82c35a1ebd3ecb430e13, recompiled and get the same (or rather a bit more since I've also since discovered the -v option):
Execution sequence: InputXml -> InputXml -> InputFld -> ProcessGrad -> OutputFld InputXml: Processing input xml file InputXml session reader CPU Time: 0.000269238s Parameters: LAMBDA = 2.5
Solver Info: EQTYPE = Helmholtz GLOBALMATRIXSTORAGETYPE = SmvBSR GLOBALSYSSOLN = DirectMultiLevelStaticCond LINSYSITERSOVLER = ConjugateGradient LOCALMATRIXSTORAGESTRATEGY = Sparse PRECONDITIONER = Diagonal PROJECTION = Continuous InputXml mesh graph setup CPU Time: 0.005176s InputXml CPU Time: 0.00561237s InputXml: Processing input xml file InputXml CPU Time: 1.4876e-05s InputFld: Processing input fld file InputFld CPU Time: 0.00216752s ProcessGrad: Calculating gradients CreateExp setexpansion CPU Time: 7.927e-05s CreateExp set first exp CPU Time: 0.00194836s Segmentation fault (core dumped)
Also, reading about FILTERS in Section 3.4 of the users guide <https://doc.nektar.info/userguide/latest/user-guidese9.html#x15-620003.4>, I tried putting <FILTERS> <FILTER TYPE="FieldConvert"> <PARAM NAME="OutputFile">gradient</PARAM> <PARAM NAME="Modules"> gradient </PARAM> </FILTER> </FILTERS> in Helm_conditions.xml, just before the closing </NEKTAR> and reran ADRSolver -v Helm_{mesh,conditions}.xml. This didn't seem to do anything; it seemed to be silently ignored, no seg fault, but no gradient.