*I just added timing and modify the meshing code (to generate 30*30*30 cells),
and nothing else.*
I added timing to the member function solve() like the following and change
nothing else.
template <int dim>
unsigned int ElasticProblem<dim>::solve ()
{
*TimerOutput::Scope t(computing_timer, "solve");*
SolverControl solver_control (solution.size(),
1e-8*system_rhs.l2_norm());
PETScWrappers::SolverCG cg (solver_control,
mpi_communicator);
PETScWrappers::PreconditionBlockJacobi preconditioner(system_matrix);
cg.solve (system_matrix, solution, system_rhs,
preconditioner);
Vector<double> localized_solution (solution);
hanging_node_constraints.distribute (localized_solution);
solution = localized_solution;
return solver_control.last_step();
}
*Thus I think the timing includes both the time to build the preconditoner, as
well as the time to solve Ax=b;*
Yes, that looks correct. I'm impressed it goes this fast.
In your TimerOutput object, do you output wall time or CPU time? Do you
initialize it with the MPI communicator object?
Best
W.
--
------------------------------------------------------------------------
Wolfgang Bangerth email: bange...@colostate.edu
www: http://www.math.colostate.edu/~bangerth/
--
The deal.II project is located at http://www.dealii.org/
For mailing list/forum options, see
https://groups.google.com/d/forum/dealii?hl=en
---
You received this message because you are subscribed to the Google Groups "deal.II User Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to dealii+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
