https://mooseframework.inl.gov
Loading...
Searching...
No Matches
NumNonlinearIterations.h
Go to the documentation of this file.
1//* This file is part of the MOOSE framework
2//* https://mooseframework.inl.gov
3//*
4//* All rights reserved, see COPYRIGHT for full restrictions
5//* https://github.com/idaholab/moose/blob/master/COPYRIGHT
6//*
7//* Licensed under LGPL 2.1, please see LICENSE for details
8//* https://www.gnu.org/licenses/lgpl-2.1.html
9
10#pragma once
11
13
19{
20public:
22
24
28 virtual void timestepSetup() override;
29
30 virtual void initialize() override {}
31 virtual void execute() override {}
32 virtual void finalize() override;
33
37 virtual Real getValue() const override;
38
39protected:
42
45
47 unsigned int _num_iters;
48
50 Real _time;
51};
Specialization of SubProblem for solving nonlinear equations plus auxiliary equations.
This class is here to combine the Postprocessor interface and the base class Postprocessor object alo...
The main MOOSE class responsible for handling user-defined parameters in almost every MOOSE system.
const InputParameters & parameters() const
Get the parameters of the object.
Definition MooseBase.h:131
NumNonlinearIterations is a postprocessor that reports the number of nonlinear iterations.
virtual void execute() override
Execute method.
FEProblemBase * _fe_problem
Pointer to the FEProblemBase.
unsigned int _num_iters
Stores the nonlinear iteration count.
virtual void timestepSetup() override
Initialization to be done at each timestep.
virtual Real getValue() const override
Get the number of nonlinear iterations.
Real _time
Stores the last time this was executed.
virtual void initialize() override
Called before execute() is ever called so that data can be cleared.
bool _accumulate_over_step
True if we should accumulate over all nonlinear solves done as part of Picard iterations in a step.
static InputParameters validParams()
virtual void finalize() override
This is called after execute() and after threadJoin()! This is probably where you want to do MPI comm...