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,
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<mailto: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<mailto: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 s.sherwin@imperial.ac.uk<mailto:s.sherwin@imperial.ac.uk> +44 (0) 20 759 45052
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
s.sherwin@imperial.ac.uk +44 (0) 20 759 45052
Hi Amitvikram, Those are indeed the options available. We typically do not print L2/Linf errors every time-step due to the cost of the calculation (and communication in a parallel simulation) and their limited use in diagnosing problems in all but the simplest of simulations. They are typically only for evaluating the error between the computed solution and an analytical solution which might be available in some cases. If you wanted, you could probably quite easily write a Filter, similar in structure to the FilterCheckpoint module, which computes the L2/Linf errors and writes them out every N timesteps. Cheers, Chris On 20/01/16 21:39, Amitvikram Dutta wrote:
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 <mailto: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 <mailto: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 <mailto: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
s.sherwin@imperial.ac.uk <mailto:s.sherwin@imperial.ac.uk> +44 (0) 20 759 45052
_______________________________________________ Nektar-users mailing list Nektar-users@imperial.ac.uk https://mailman.ic.ac.uk/mailman/listinfo/nektar-users
-- Chris Cantwell Imperial College London South Kensington Campus London SW7 2AZ Email: c.cantwell@imperial.ac.uk www.imperial.ac.uk/people/c.cantwell
Thanks Chris, I'm running simulations for Re of the order of 10^5. I noticed that even the standard simulation of 2D flow over a pipe begins to break down at that Re. At present my simulation has around 100k mesh elements and I'm running the simulation with n=7 polynomial order. Do you think that increasing the mesh fine-ness would help in this case? Sincerely, *Amitvikram Dutta* *MASc Candidate* *Graduate Research Assistant * *Okanagan CFD Laboratory* *University of British Columbia | Okanagan Campus* On Tue, Feb 2, 2016 at 2:16 PM, Chris Cantwell <c.cantwell@imperial.ac.uk> wrote:
Hi Amitvikram,
Those are indeed the options available. We typically do not print L2/Linf errors every time-step due to the cost of the calculation (and communication in a parallel simulation) and their limited use in diagnosing problems in all but the simplest of simulations. They are typically only for evaluating the error between the computed solution and an analytical solution which might be available in some cases.
If you wanted, you could probably quite easily write a Filter, similar in structure to the FilterCheckpoint module, which computes the L2/Linf errors and writes them out every N timesteps.
Cheers, Chris
On 20/01/16 21:39, Amitvikram Dutta wrote:
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 <mailto: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
<mailto: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 <mailto: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
s.sherwin@imperial.ac.uk <mailto:s.sherwin@imperial.ac.uk> +44 (0) 20 759 45052
_______________________________________________ Nektar-users mailing list Nektar-users@imperial.ac.uk https://mailman.ic.ac.uk/mailman/listinfo/nektar-users
-- Chris Cantwell Imperial College London South Kensington Campus London SW7 2AZ Email: c.cantwell@imperial.ac.uk www.imperial.ac.uk/people/c.cantwell
_______________________________________________ Nektar-users mailing list Nektar-users@imperial.ac.uk https://mailman.ic.ac.uk/mailman/listinfo/nektar-users
participants (3)
-
Amitvikram Dutta
-
Chris Cantwell
-
Sherwin, Spencer J