Hi Spencer,

As I see it, there are two options to monitor the solution's progress. The first is to convert one of the checkpoint files to a vtu format and view the simulation on a post processor such as paraview. The second is to include a filter to write out history files at regular intervals which can be monitored as above. 

One also has the option of monitoring when values of certain variable exceed chosen maximum or minimum limits at through the ThresholdMax and ThresholdMin filters respectively.

Did I miss anything? 
Also, I think I'm missing an option where the solver prints out the L2 and Linf error after each iteration. For my cases the values only show up at the end -usually after the solution has crashed-. I was wondering what the option was to set it to print after every iteration.

Sincerely,

Amitvikram Dutta

MASc Candidate

Graduate Research Assistant 

Okanagan CFD Laboratory

University of British Columbia | Okanagan Campus 


On Wed, Jan 20, 2016 at 5:35 AM, Sherwin, Spencer J <s.sherwin@imperial.ac.uk> wrote:
Hi Amitvikram,

There are history points and force profiles. Much of this functionality is provided through filters. Have a look at the user guide info on this and let us know if there are any confusions.

Cheers,
Spencer.

On 19 Jan 2016, at 22:32, Amitvikram Dutta <amitvdutta23@gmail.com> wrote:

Hi,

Is there some form of a logfile implementation for Nektar++ which one can query as a simulation is proceeding in order to monitor convergence?


Sincerely,
_______________________________________________
Nektar-users mailing list
Nektar-users@imperial.ac.uk
https://mailman.ic.ac.uk/mailman/listinfo/nektar-users

Spencer  Sherwin
McLaren Racing/Royal Academy of Engineering Research Chair, 
Professor of Computational Fluid Mechanics,
Department of Aeronautics,
Imperial College London
South Kensington Campus
London SW7 2AZ

+44 (0) 20 759 45052