Reference documentation for deal.II version GIT relicensing-218-g1f873f3929 2024-03-28 15:00:02+00:00
\(\newcommand{\dealvcentcolon}{\mathrel{\mathop{:}}}\) \(\newcommand{\dealcoloneq}{\dealvcentcolon\mathrel{\mkern-1.2mu}=}\) \(\newcommand{\jump}[1]{\left[\!\left[ #1 \right]\!\right]}\) \(\newcommand{\average}[1]{\left\{\!\left\{ #1 \right\}\!\right\}}\)
Loading...
Searching...
No Matches
step-26.h
Go to the documentation of this file.
1,
679 *   const unsigned int component) const
680 *   {
681 *   (void)component;
682 *   Assert(component == 0, ExcIndexRange(component, 0, 1));
683 *   return 0;
684 *   }
685 *  
686 *  
687 *  
688 * @endcode
689 *
690 *
691 * <a name="step_26-ThecodeHeatEquationcodeimplementation"></a>
692 * <h3>The <code>HeatEquation</code> implementation</h3>
693 *
694
695 *
696 * It is time now for the implementation of the main class. Let's
697 * start with the constructor which selects a linear element, a time
698 * step constant at 1/500 (remember that one period of the source
699 * on the right hand side was set to 0.2 above, so we resolve each
700 * period with 100 time steps) and chooses the Crank Nicolson method
701 * by setting @f$\theta=1/2@f$.
702 *
703 * @code
704 *   template <int dim>
705 *   HeatEquation<dim>::HeatEquation()
706 *   : fe(1)
707 *   , dof_handler(triangulation)
708 *   , time_step(1. / 500)
709 *   , theta(0.5)
710 *   {}
711 *  
712 *  
713 *  
714 * @endcode
715 *
716 *
717 * <a name="step_26-codeHeatEquationsetup_systemcode"></a>
718 * <h4><code>HeatEquation::setup_system</code></h4>
719 *
720
721 *
722 * The next function is the one that sets up the DoFHandler object,
723 * computes the constraints, and sets the linear algebra objects
724 * to their correct sizes. We also compute the mass and Laplace
725 * matrix here by simply calling two functions in the library.
726 *
727
728 *
729 * Note that we do not take the hanging node constraints into account when
730 * assembling the matrices (both functions have an AffineConstraints argument
731 * that defaults to an empty object). This is because we are going to
732 * condense the constraints in run() after combining the matrices for the
733 * current time-step.
734 *
735 * @code
736 *   template <int dim>
737 *   void HeatEquation<dim>::setup_system()
738 *   {
739 *   dof_handler.distribute_dofs(fe);
740 *  
741 *   std::cout << std::endl
742 *   << "===========================================" << std::endl
743 *   << "Number of active cells: " << triangulation.n_active_cells()
744 *   << std::endl
745 *   << "Number of degrees of freedom: " << dof_handler.n_dofs()
746 *   << std::endl
747 *   << std::endl;
748 *  
749 *   constraints.clear();
750 *   DoFTools::make_hanging_node_constraints(dof_handler, constraints);
751 *   constraints.close();
752 *  
753 *   DynamicSparsityPattern dsp(dof_handler.n_dofs());
754 *   DoFTools::make_sparsity_pattern(dof_handler,
755 *   dsp,
756 *   constraints,
757 *   /*keep_constrained_dofs = */ true);
758 *   sparsity_pattern.copy_from(dsp);
759 *  
760 *   mass_matrix.reinit(sparsity_pattern);
761 *   laplace_matrix.reinit(sparsity_pattern);
762 *   system_matrix.reinit(sparsity_pattern);
763 *  
764 *   MatrixCreator::create_mass_matrix(dof_handler,
765 *   QGauss<dim>(fe.degree + 1),
766 *   mass_matrix);
767 *   MatrixCreator::create_laplace_matrix(dof_handler,
768 *   QGauss<dim>(fe.degree + 1),
769 *   laplace_matrix);
770 *  
771 *   solution.reinit(dof_handler.n_dofs());
772 *   old_solution.reinit(dof_handler.n_dofs());
773 *   system_rhs.reinit(dof_handler.n_dofs());
774 *   }
775 *  
776 *  
777 * @endcode
778 *
779 *
780 * <a name="step_26-codeHeatEquationsolve_time_stepcode"></a>
781 * <h4><code>HeatEquation::solve_time_step</code></h4>
782 *
783
784 *
785 * The next function is the one that solves the actual linear system
786 * for a single time step. There is nothing surprising here:
787 *
788 * @code
789 *   template <int dim>
790 *   void HeatEquation<dim>::solve_time_step()
791 *   {
792 *   SolverControl solver_control(1000, 1e-8 * system_rhs.l2_norm());
793 *   SolverCG<Vector<double>> cg(solver_control);
794 *  
795 *   PreconditionSSOR<SparseMatrix<double>> preconditioner;
796 *   preconditioner.initialize(system_matrix, 1.0);
797 *  
798 *   cg.solve(system_matrix, solution, system_rhs, preconditioner);
799 *  
800 *   constraints.distribute(solution);
801 *  
802 *   std::cout << " " << solver_control.last_step() << " CG iterations."
803 *   << std::endl;
804 *   }
805 *  
806 *  
807 *  
808 * @endcode
809 *
810 *
811 * <a name="step_26-codeHeatEquationoutput_resultscode"></a>
812 * <h4><code>HeatEquation::output_results</code></h4>
813 *
814
815 *
816 * Neither is there anything new in generating graphical output other than the
817 * fact that we tell the DataOut object what the current time and time step
818 * number is, so that this can be written into the output file :
819 *
820 * @code
821 *   template <int dim>
822 *   void HeatEquation<dim>::output_results() const
823 *   {
824 *   DataOut<dim> data_out;
825 *  
826 *   data_out.attach_dof_handler(dof_handler);
827 *   data_out.add_data_vector(solution, "U");
828 *  
829 *   data_out.build_patches();
830 *  
831 *   data_out.set_flags(DataOutBase::VtkFlags(time, timestep_number));
832 *  
833 *   const std::string filename =
834 *   "solution-" + Utilities::int_to_string(timestep_number, 3) + ".vtk";
835 *   std::ofstream output(filename);
836 *   data_out.write_vtk(output);
837 *   }
838 *  
839 *  
840 * @endcode
841 *
842 *
843 * <a name="step_26-codeHeatEquationrefine_meshcode"></a>
844 * <h4><code>HeatEquation::refine_mesh</code></h4>
845 *
846
847 *
848 * This function is the interesting part of the program. It takes care of
849 * the adaptive mesh refinement. The three tasks
850 * this function performs is to first find out which cells to
851 * refine/coarsen, then to actually do the refinement and eventually
852 * transfer the solution vectors between the two different grids. The first
853 * task is simply achieved by using the well-established Kelly error
854 * estimator on the solution. The second task is to actually do the
855 * remeshing. That involves only basic functions as well, such as the
856 * <code>refine_and_coarsen_fixed_fraction</code> that refines those cells
857 * with the largest estimated error that together make up 60 per cent of the
858 * error, and coarsens those cells with the smallest error that make up for
859 * a combined 40 per cent of the error. Note that for problems such as the
860 * current one where the areas where something is going on are shifting
861 * around, we want to aggressively coarsen so that we can move cells
862 * around to where it is necessary.
863 *
864
865 *
866 * As already discussed in the introduction, too small a mesh leads to
867 * too small a time step, whereas too large a mesh leads to too little
868 * resolution. Consequently, after the first two steps, we have two
869 * loops that limit refinement and coarsening to an allowable range of
870 * cells:
871 *
872 * @code
873 *   template <int dim>
874 *   void HeatEquation<dim>::refine_mesh(const unsigned int min_grid_level,
875 *   const unsigned int max_grid_level)
876 *   {
877 *   Vector<float> estimated_error_per_cell(triangulation.n_active_cells());
878 *  
879 *   KellyErrorEstimator<dim>::estimate(
880 *   dof_handler,
881 *   QGauss<dim - 1>(fe.degree + 1),
882 *   std::map<types::boundary_id, const Function<dim> *>(),
883 *   solution,
884 *   estimated_error_per_cell);
885 *  
886 *   GridRefinement::refine_and_coarsen_fixed_fraction(triangulation,
887 *   estimated_error_per_cell,
888 *   0.6,
889 *   0.4);
890 *  
891 *   if (triangulation.n_levels() > max_grid_level)
892 *   for (const auto &cell :
893 *   triangulation.active_cell_iterators_on_level(max_grid_level))
894 *   cell->clear_refine_flag();
895 *   for (const auto &cell :
896 *   triangulation.active_cell_iterators_on_level(min_grid_level))
897 *   cell->clear_coarsen_flag();
898 * @endcode
899 *
900 * These two loops above are slightly different but this is easily
901 * explained. In the first loop, instead of calling
902 * <code>triangulation.end()</code> we may as well have called
903 * <code>triangulation.end_active(max_grid_level)</code>. The two
904 * calls should yield the same iterator since iterators are sorted
905 * by level and there should not be any cells on levels higher than
906 * on level <code>max_grid_level</code>. In fact, this very piece
907 * of code makes sure that this is the case.
908 *
909
910 *
911 * As part of mesh refinement we need to transfer the solution vectors
912 * from the old mesh to the new one. To this end we use the
913 * SolutionTransfer class and we have to prepare the solution vectors that
914 * should be transferred to the new grid (we will lose the old grid once
915 * we have done the refinement so the transfer has to happen concurrently
916 * with refinement). At the point where we call this function, we will
917 * have just computed the solution, so we no longer need the old_solution
918 * variable (it will be overwritten by the solution just after the mesh
919 * may have been refined, i.e., at the end of the time step; see below).
920 * In other words, we only need the one solution vector, and we copy it
921 * to a temporary object where it is safe from being reset when we further
922 * down below call <code>setup_system()</code>.
923 *
924
925 *
926 * Consequently, we initialize a SolutionTransfer object by attaching
927 * it to the old DoF handler. We then prepare the triangulation and the
928 * data vector for refinement (in this order).
929 *
930 * @code
931 *   SolutionTransfer<dim> solution_trans(dof_handler);
932 *  
933 *   Vector<double> previous_solution;
934 *   previous_solution = solution;
935 *   triangulation.prepare_coarsening_and_refinement();
936 *   solution_trans.prepare_for_coarsening_and_refinement(previous_solution);
937 *  
938 * @endcode
939 *
940 * Now everything is ready, so do the refinement and recreate the DoF
941 * structure on the new grid, and finally initialize the matrix structures
942 * and the new vectors in the <code>setup_system</code> function. Next, we
943 * actually perform the interpolation of the solution from old to new
944 * grid. The final step is to apply the hanging node constraints to the
945 * solution vector, i.e., to make sure that the values of degrees of
946 * freedom located on hanging nodes are so that the solution is
947 * continuous. This is necessary since SolutionTransfer only operates on
948 * cells locally, without regard to the neighborhood.
949 *
950 * @code
951 *   triangulation.execute_coarsening_and_refinement();
952 *   setup_system();
953 *  
954 *   solution_trans.interpolate(previous_solution, solution);
955 *   constraints.distribute(solution);
956 *   }
957 *  
958 *  
959 *  
960 * @endcode
961 *
962 *
963 * <a name="step_26-codeHeatEquationruncode"></a>
964 * <h4><code>HeatEquation::run</code></h4>
965 *
966
967 *
968 * This is the main driver of the program, where we loop over all
969 * time steps. At the top of the function, we set the number of
970 * initial global mesh refinements and the number of initial cycles of
971 * adaptive mesh refinement by repeating the first time step a few
972 * times. Then we create a mesh, initialize the various objects we will
973 * work with, set a label for where we should start when re-running
974 * the first time step, and interpolate the initial solution onto
975 * out mesh (we choose the zero function here, which of course we could
976 * do in a simpler way by just setting the solution vector to zero). We
977 * also output the initial time step once.
978 *
979
980 *
981 * @note If you're an experienced programmer, you may be surprised
982 * that we use a <code>goto</code> statement in this piece of code!
983 * <code>goto</code> statements are not particularly well liked any
984 * more since Edsgar Dijkstra, one of the greats of computer science,
985 * wrote a letter in 1968 called "Go To Statement considered harmful"
986 * (see <a href="http://en.wikipedia.org/wiki/Considered_harmful">here</a>).
987 * The author of this code subscribes to this notion whole-heartedly:
988 * <code>goto</code> is hard to understand. In fact, deal.II contains
989 * virtually no occurrences: excluding code that was essentially
990 * transcribed from books and not counting duplicated code pieces,
991 * there are 3 locations in about 600,000 lines of code at the time
992 * this note is written; we also use it in 4 tutorial programs, in
993 * exactly the same context as here. Instead of trying to justify
994 * the occurrence here, let's first look at the code and we'll come
995 * back to the issue at the end of function.
996 *
997 * @code
998 *   template <int dim>
999 *   void HeatEquation<dim>::run()
1000 *   {
1001 *   const unsigned int initial_global_refinement = 2;
1002 *   const unsigned int n_adaptive_pre_refinement_steps = 4;
1003 *  
1005 *   triangulation.refine_global(initial_global_refinement);
1006 *  
1007 *   setup_system();
1008 *  
1009 *   unsigned int pre_refinement_step = 0;
1010 *  
1011 *   Vector<double> tmp;
1012 *   Vector<double> forcing_terms;
1013 *  
1014 *   start_time_iteration:
1015 *  
1016 *   time = 0.0;
1017 *   timestep_number = 0;
1018 *  
1019 *   tmp.reinit(solution.size());
1020 *   forcing_terms.reinit(solution.size());
1021 *  
1022 *  
1023 *   VectorTools::interpolate(dof_handler,
1025 *   old_solution);
1026 *   solution = old_solution;
1027 *  
1028 *   output_results();
1029 *  
1030 * @endcode
1031 *
1032 * Then we start the main loop until the computed time exceeds our
1033 * end time of 0.5. The first task is to build the right hand
1034 * side of the linear system we need to solve in each time step.
1035 * Recall that it contains the term @f$MU^{n-1}-(1-\theta)k_n AU^{n-1}@f$.
1036 * We put these terms into the variable system_rhs, with the
1037 * help of a temporary vector:
1038 *
1039 * @code
1040 *   const double end_time = 0.5;
1041 *   while (time <= end_time)
1042 *   {
1043 *   time += time_step;
1044 *   ++timestep_number;
1045 *  
1046 *   std::cout << "Time step " << timestep_number << " at t=" << time
1047 *   << std::endl;
1048 *  
1049 *   mass_matrix.vmult(system_rhs, old_solution);
1050 *  
1051 *   laplace_matrix.vmult(tmp, old_solution);
1052 *   system_rhs.add(-(1 - theta) * time_step, tmp);
1053 *  
1054 * @endcode
1055 *
1056 * The second piece is to compute the contributions of the source
1057 * terms. This corresponds to the term @f$k_n
1058 * \left[ (1-\theta)F^{n-1} + \theta F^n \right]@f$. The following
1059 * code calls VectorTools::create_right_hand_side to compute the
1060 * vectors @f$F@f$, where we set the time of the right hand side
1061 * (source) function before we evaluate it. The result of this
1062 * all ends up in the forcing_terms variable:
1063 *
1064 * @code
1065 *   RightHandSide<dim> rhs_function;
1066 *   rhs_function.set_time(time);
1067 *   VectorTools::create_right_hand_side(dof_handler,
1068 *   QGauss<dim>(fe.degree + 1),
1069 *   rhs_function,
1070 *   tmp);
1071 *   forcing_terms = tmp;
1072 *   forcing_terms *= time_step * theta;
1073 *  
1074 *   rhs_function.set_time(time - time_step);
1075 *   VectorTools::create_right_hand_side(dof_handler,
1076 *   QGauss<dim>(fe.degree + 1),
1077 *   rhs_function,
1078 *   tmp);
1079 *  
1080 *   forcing_terms.add(time_step * (1 - theta), tmp);
1081 *  
1082 * @endcode
1083 *
1084 * Next, we add the forcing terms to the ones that
1085 * come from the time stepping, and also build the matrix
1086 * @f$M+k_n\theta A@f$ that we have to invert in each time step.
1087 * The final piece of these operations is to eliminate
1088 * hanging node constrained degrees of freedom from the
1089 * linear system:
1090 *
1091 * @code
1092 *   system_rhs += forcing_terms;
1093 *  
1094 *   system_matrix.copy_from(mass_matrix);
1095 *   system_matrix.add(theta * time_step, laplace_matrix);
1096 *  
1097 *   constraints.condense(system_matrix, system_rhs);
1098 *  
1099 * @endcode
1100 *
1101 * There is one more operation we need to do before we
1102 * can solve it: boundary values. To this end, we create
1103 * a boundary value object, set the proper time to the one
1104 * of the current time step, and evaluate it as we have
1105 * done many times before. The result is used to also
1106 * set the correct boundary values in the linear system:
1107 *
1108 * @code
1109 *   {
1110 *   BoundaryValues<dim> boundary_values_function;
1111 *   boundary_values_function.set_time(time);
1112 *  
1113 *   std::map<types::global_dof_index, double> boundary_values;
1115 *   0,
1116 *   boundary_values_function,
1117 *   boundary_values);
1118 *  
1119 *   MatrixTools::apply_boundary_values(boundary_values,
1120 *   system_matrix,
1121 *   solution,
1122 *   system_rhs);
1123 *   }
1124 *  
1125 * @endcode
1126 *
1127 * With this out of the way, all we have to do is solve the
1128 * system, generate graphical data, and...
1129 *
1130 * @code
1131 *   solve_time_step();
1132 *  
1133 *   output_results();
1134 *  
1135 * @endcode
1136 *
1137 * ...take care of mesh refinement. Here, what we want to do is
1138 * (i) refine the requested number of times at the very beginning
1139 * of the solution procedure, after which we jump to the top to
1140 * restart the time iteration, (ii) refine every fifth time
1141 * step after that.
1142 *
1143
1144 *
1145 * The time loop and, indeed, the main part of the program ends
1146 * with starting into the next time step by setting old_solution
1147 * to the solution we have just computed.
1148 *
1149 * @code
1150 *   if ((timestep_number == 1) &&
1151 *   (pre_refinement_step < n_adaptive_pre_refinement_steps))
1152 *   {
1153 *   refine_mesh(initial_global_refinement,
1154 *   initial_global_refinement +
1155 *   n_adaptive_pre_refinement_steps);
1156 *   ++pre_refinement_step;
1157 *  
1158 *   std::cout << std::endl;
1159 *  
1160 *   goto start_time_iteration;
1161 *   }
1162 *   else if ((timestep_number > 0) && (timestep_number % 5 == 0))
1163 *   {
1164 *   refine_mesh(initial_global_refinement,
1165 *   initial_global_refinement +
1166 *   n_adaptive_pre_refinement_steps);
1167 *   tmp.reinit(solution.size());
1168 *   forcing_terms.reinit(solution.size());
1169 *   }
1170 *  
1171 *   old_solution = solution;
1172 *   }
1173 *   }
1174 *   } // namespace Step26
1175 * @endcode
1176 *
1177 * Now that you have seen what the function does, let us come back to the issue
1178 * of the <code>goto</code>. In essence, what the code does is
1179 * something like this:
1180 * <div class=CodeFragmentInTutorialComment>
1181 * @code
1182 * void run ()
1183 * {
1184 * initialize;
1185 * start_time_iteration:
1186 * for (timestep=1...)
1187 * {
1188 * solve timestep;
1189 * if (timestep==1 && not happy with the result)
1190 * {
1191 * adjust some data structures;
1192 * goto start_time_iteration; // simply try again
1193 * }
1194 * postprocess;
1195 * }
1196 * }
1197 * @endcode
1198 * </div>
1199 * Here, the condition "happy with the result" is whether we'd like to keep
1200 * the current mesh or would rather refine the mesh and start over on the
1201 * new mesh. We could of course replace the use of the <code>goto</code>
1202 * by the following:
1203 * <div class=CodeFragmentInTutorialComment>
1204 * @code
1205 * void run ()
1206 * {
1207 * initialize;
1208 * while (true)
1209 * {
1210 * solve timestep;
1211 * if (not happy with the result)
1212 * adjust some data structures;
1213 * else
1214 * break;
1215 * }
1216 * postprocess;
1217 *
1218
1219 * for (timestep=2...)
1220 * {
1221 * solve timestep;
1222 * postprocess;
1223 * }
1224 * }
1225 * @endcode
1226 * </div>
1227 * This has the advantage of getting rid of the <code>goto</code>
1228 * but the disadvantage of having to duplicate the code that implements
1229 * the "solve timestep" and "postprocess" operations in two different
1230 * places. This could be countered by putting these parts of the code
1231 * (sizable chunks in the actual implementation above) into their
1232 * own functions, but a <code>while(true)</code> loop with a
1233 * <code>break</code> statement is not really all that much easier
1234 * to read or understand than a <code>goto</code>.
1235 *
1236
1237 *
1238 * In the end, one might simply agree that <i>in general</i>
1239 * <code>goto</code> statements are a bad idea but be pragmatic and
1240 * state that there may be occasions where they can help avoid code
1241 * duplication and awkward control flow. This may be one of these
1242 * places, and it matches the position Steve McConnell takes in his
1243 * excellent book "Code Complete" @cite CodeComplete about good
1244 * programming practices (see the mention of this book in the
1245 * introduction of @ref step_1 "step-1") that spends a surprising ten pages on the
1246 * question of <code>goto</code> in general.
1247 *
1248
1249 *
1250 *
1251
1252 *
1253 *
1254 * <a name="step_26-Thecodemaincodefunction"></a>
1255 * <h3>The <code>main</code> function</h3>
1256 *
1257
1258 *
1259 * Having made it this far, there is, again, nothing
1260 * much to discuss for the main function of this
1261 * program: it looks like all such functions since @ref step_6 "step-6".
1262 *
1263 * @code
1264 *   int main()
1265 *   {
1266 *   try
1267 *   {
1268 *   using namespace Step26;
1269 *  
1270 *   HeatEquation<2> heat_equation_solver;
1271 *   heat_equation_solver.run();
1272 *   }
1273 *   catch (std::exception &exc)
1274 *   {
1275 *   std::cerr << std::endl
1276 *   << std::endl
1277 *   << "----------------------------------------------------"
1278 *   << std::endl;
1279 *   std::cerr << "Exception on processing: " << std::endl
1280 *   << exc.what() << std::endl
1281 *   << "Aborting!" << std::endl
1282 *   << "----------------------------------------------------"
1283 *   << std::endl;
1284 *  
1285 *   return 1;
1286 *   }
1287 *   catch (...)
1288 *   {
1289 *   std::cerr << std::endl
1290 *   << std::endl
1291 *   << "----------------------------------------------------"
1292 *   << std::endl;
1293 *   std::cerr << "Unknown exception!" << std::endl
1294 *   << "Aborting!" << std::endl
1295 *   << "----------------------------------------------------"
1296 *   << std::endl;
1297 *   return 1;
1298 *   }
1299 *  
1300 *   return 0;
1301 *   }
1302 * @endcode
1303<a name="step_26-Results"></a><h1>Results</h1>
1304
1305
1306As in many of the tutorials, the actual output of the program matters less
1307than how we arrived there. Nonetheless, here it is:
1308@code
1309===========================================
1310Number of active cells: 48
1311Number of degrees of freedom: 65
1312
1313Time step 1 at t=0.002
1314 7 CG iterations.
1315
1316===========================================
1317Number of active cells: 60
1318Number of degrees of freedom: 81
1319
1320
1321Time step 1 at t=0.002
1322 7 CG iterations.
1323
1324===========================================
1325Number of active cells: 105
1326Number of degrees of freedom: 136
1327
1328
1329Time step 1 at t=0.002
1330 7 CG iterations.
1331
1332[...]
1333
1334Time step 249 at t=0.498
1335 13 CG iterations.
1336Time step 250 at t=0.5
1337 14 CG iterations.
1338
1339===========================================
1340Number of active cells: 1803
1341Number of degrees of freedom: 2109
1342@endcode
1343
1344Maybe of more interest is a visualization of the solution and the mesh on which
1345it was computed:
1346
1347<img src="https://www.dealii.org/images/steps/developer/step-26.movie.gif" alt="Animation of the solution of step 26.">
1348
1349The movie shows how the two sources switch on and off and how the mesh reacts
1350to this. It is quite obvious that the mesh as is is probably not the best we
1351could come up with. We'll get back to this in the next section.
1352
1353
1354<a name="step-26-extensions"></a>
1355<a name="step_26-Possibilitiesforextensions"></a><h3>Possibilities for extensions</h3>
1356
1357
1358There are at least two areas where one can improve this program significantly:
1359adaptive time stepping and a better choice of the mesh.
1360
1361<a name="step_26-Adaptivetimestepping"></a><h4>Adaptive time stepping</h4>
1362
1363
1364Having chosen an implicit time stepping scheme, we are not bound by any
1365CFL-like condition on the time step. Furthermore, because the time scales on
1366which change happens on a given cell in the heat equation are not bound to the
1367cells diameter (unlike the case with the wave equation, where we had a fixed
1368speed of information transport that couples the temporal and spatial scales),
1369we can choose the time step as we please. Or, better, choose it as we deem
1370necessary for accuracy.
1371
1372Looking at the solution, it is clear that the action does not happen uniformly
1373over time: a lot is changing around the times when we switch on a source, things
1374become less dramatic once a source is on for a little while, and we enter a
1375long phase of decline when both sources are off. During these times, we could
1376surely get away with a larger time step than before without sacrificing too
1377much accuracy.
1378
1379The literature has many suggestions on how to choose the time step size
1380adaptively. Much can be learned, for example, from the way ODE solvers choose
1381their time steps. One can also be inspired by a posteriori error estimators
1382that can, ideally, be written in a way that they consist of a temporal and a
1383spatial contribution to the overall error. If the temporal one is too large,
1384we should choose a smaller time step. Ideas in this direction can be found,
1385for example, in the PhD thesis of a former principal developer of deal.II,
1386Ralf Hartmann, published by the University of Heidelberg, Germany, in 2002
1387(see @cite Har02).
1388
1389
1390<a name="step_26-Bettertimesteppingmethods"></a><h4>Better time stepping methods</h4>
1391
1392
1393We here use one of the simpler time stepping methods, namely the second order
1394in time Crank-Nicolson method. This is surely already better than the even
1395more widely used (and even less accurate) implicit Euler method,
1396but many other, more accurate methods such as
1397Runge-Kutta methods are available and should be used as they do not represent
1398much additional effort. It is not difficult to implement this for the current
1399program, if one wanted; a more systematic treatment is also given in @ref step_52 "step-52".
1400
1401As a general rule, however, one should not be implementing time stepping
1402methods by hand, as we do here, for problems that do not require
1403exploiting special properties of the equation and consequently require
1404specialized time stepping methods. (The heat equation does not fall into
1405this category, and "standard" time stepping methods are all we need here.)
1406Rather, one should use one of the available
1407high-quality libraries for time stepping, for the same reasons as one should
1408not be implementing finite element methods by hand but use deal.II instead.
1409Indeed, deal.II has interfaces to one such time stepping library,
1410[SUNDIALS](https://computing.llnl.gov/projects/sundials), already available.
1411In particular, the SUNDIALS::ARKode class would make for a great starting
1412point for the use of much better (and much more accurate) time steppers;
1413the methods one would then get also implement the automatic time step
1414control mentioned above.
1415
1416
1417<a name="step_26-Betterrefinementcriteria"></a><h4>Better refinement criteria</h4>
1418
1419
1420If you look at the meshes in the movie above, it is clear that they are not
1421particularly well suited to the task at hand. In fact, they look rather
1422random.
1423
1424There are two factors at play. First, there are some islands where cells
1425have been refined but that are surrounded by non-refined cells (and there
1426are probably also a few occasional coarsened islands). These are not terrible,
1427as they most of the time do not affect the approximation quality of the mesh,
1428but they also don't help because so many of their additional degrees of
1429freedom are in fact constrained by hanging node constraints. That said,
1430this is easy to fix: the Triangulation class takes an argument to its
1431constructor indicating a level of "mesh smoothing". Passing one of many
1432possible flags, this instructs the triangulation to refine some additional
1433cells, or not to refine some cells, so that the resulting mesh does not have
1434these artifacts.
1435
1436The second problem is more severe: the mesh appears to lag the solution.
1437The underlying reason is that we only adapt the mesh once every fifth
1438time step, and only allow for a single refinement in these cases. Whenever a
1439source switches on, the solution had been very smooth in this area before and
1440the mesh was consequently rather coarse. This implies that the next time step
1441when we refine the mesh, we will get one refinement level more in this area,
1442and five time steps later another level, etc. But this is not enough: first,
1443we should refine immediately when a source switches on (after all, in the
1444current context we at least know what the right hand side is), and we should
1445allow for more than one refinement level. Of course, all of this can be done
1446using deal.II, it just requires a bit of algorithmic thinking in how to make
1447this work!
1448
1449
1450<a name="step_26-Positivitypreservation"></a><h4>Positivity preservation</h4>
1451
1452
1453To increase the accuracy and resolution of your simulation in time, one
1454typically decreases the time step size @f$k_n@f$. If you start playing around
1455with the time step in this particular example, you will notice that the
1456solution becomes partly negative, if @f$k_n@f$ is below a certain threshold.
1457This is not what we would expect to happen (in nature).
1458
1459To get an idea of this behavior mathematically, let us consider a general,
1460fully discrete problem:
1461@f{align*}{
1462 A u^{n} = B u^{n-1}.
1463@f}
1464The general form of the @f$i@f$th equation then reads:
1465@f{align*}{
1466 a_{ii} u^{n}_i &= b_{ii} u^{n-1}_i +
1467 \sum\limits_{j \in S_i} \left( b_{ij} u^{n-1}_j - a_{ij} u^{n}_j \right),
1468@f}
1469where @f$S_i@f$ is the set of degrees of freedom that DoF @f$i@f$ couples with (i.e.,
1470for which either the matrix @f$A@f$ or matrix @f$B@f$ has a nonzero entry at position
1471@f$(i,j)@f$). If all coefficients
1472fulfill the following conditions:
1473@f{align*}{
1474 a_{ii} &> 0, & b_{ii} &\geq 0, & a_{ij} &\leq 0, & b_{ij} &\geq 0,
1475 &
1476 \forall j &\in S_i,
1477@f}
1478all solutions @f$u^{n}@f$ keep their sign from the previous ones @f$u^{n-1}@f$, and
1479consequently from the initial values @f$u^0@f$. See e.g.
1480<a href="http://bookstore.siam.org/cs14/">Kuzmin, H&auml;m&auml;l&auml;inen</a>
1481for more information on positivity preservation.
1482
1483Depending on the PDE to solve and the time integration scheme used, one is
1484able to deduce conditions for the time step @f$k_n@f$. For the heat equation with
1485the Crank-Nicolson scheme,
1486<a href="https://doi.org/10.2478/cmam-2010-0025">Schatz et. al.</a> have
1487translated it to the following ones:
1488@f{align*}{
1489 (1 - \theta) k a_{ii} &\leq m_{ii},\qquad \forall i,
1490 &
1491 \theta k \left| a_{ij} \right| &\geq m_{ij},\qquad j \neq i,
1492@f}
1493where @f$M = m_{ij}@f$ denotes the @ref GlossMassMatrix "mass matrix" and @f$A = a_{ij}@f$ the stiffness
1494matrix with @f$a_{ij} \leq 0@f$ for @f$j \neq i@f$, respectively. With
1495@f$a_{ij} \leq 0@f$, we can formulate bounds for the global time step @f$k@f$ as
1496follows:
1497@f{align*}{
1498 k_{\text{max}} &= \frac{ 1 }{ 1 - \theta }
1499 \min\left( \frac{ m_{ii} }{ a_{ii} } \right),~ \forall i,
1500 &
1501 k_{\text{min}} &= \frac{ 1 }{ \theta }
1502 \max\left( \frac{ m_{ij} }{ \left|a_{ij}\right| } \right),~ j \neq i.
1503@f}
1504In other words, the time step is constrained by <i>both a lower
1505and upper bound</i> in case of a Crank-Nicolson scheme. These bounds should be
1506considered along with the CFL condition to ensure significance of the performed
1507simulations.
1508
1509Being unable to make the time step as small as we want to get more
1510accuracy without losing the positivity property is annoying. It raises
1511the question of whether we can at least <i>compute</i> the minimal time step
1512we can choose to ensure positivity preservation in this particular tutorial.
1513Indeed, we can use
1514the SparseMatrix objects for both mass and stiffness that are created via
1515the MatrixCreator functions. Iterating through each entry via SparseMatrixIterators
1516lets us check for diagonal and off-diagonal entries to set a proper time step
1517dynamically. For quadratic matrices, the diagonal element is stored as the
1518first member of a row (see SparseMatrix documentation). An exemplary code
1519snippet on how to grab the entries of interest from the <code>mass_matrix</code>
1520is shown below.
1521
1522@code
1523Assert (mass_matrix.m() == mass_matrix.n(), ExcNotQuadratic());
1524const unsigned int num_rows = mass_matrix.m();
1525double mass_matrix_min_diag = std::numeric_limits<double>::max(),
1526 mass_matrix_max_offdiag = 0.;
1527
1528SparseMatrixIterators::Iterator<double,true> row_it (&mass_matrix, 0);
1529
1530for(unsigned int m = 0; m<num_rows; ++m)
1531{
1532 // check the diagonal element
1533 row_it = mass_matrix.begin(m);
1534 mass_matrix_min_diag = std::min(row_it->value(), mass_matrix_min_diag);
1535 ++row_it;
1536
1537 // check the off-diagonal elements
1538 for(; row_it != mass_matrix.end(m); ++row_it)
1539 mass_matrix_max_offdiag = std::max(row_it->value(), mass_matrix_max_offdiag);
1540}
1541@endcode
1542
1543Using the information so computed, we can bound the time step via the formulas
1544above.
1545 *
1546 *
1547<a name="step_26-PlainProg"></a>
1548<h1> The plain program</h1>
1549@include "step-26.cc"
1550*/
virtual void reinit(const size_type N, const bool omit_zeroing_entries=false)
Point< 2 > second
Definition grid_out.cc:4614
Point< 2 > first
Definition grid_out.cc:4613
__global__ void set(Number *val, const Number s, const size_type N)
#define Assert(cond, exc)
void loop(IteratorType begin, std_cxx20::type_identity_t< IteratorType > end, DOFINFO &dinfo, INFOBOX &info, const std::function< void(DOFINFO &, typename INFOBOX::CellInfo &)> &cell_worker, const std::function< void(DOFINFO &, typename INFOBOX::CellInfo &)> &boundary_worker, const std::function< void(DOFINFO &, DOFINFO &, typename INFOBOX::CellInfo &, typename INFOBOX::CellInfo &)> &face_worker, AssemblerType &assembler, const LoopControl &lctrl=LoopControl())
Definition loop.h:442
void random(DoFHandler< dim, spacedim > &dof_handler)
void hyper_L(Triangulation< dim > &tria, const double left=-1., const double right=1., const bool colorize=false)
void refine(Triangulation< dim, spacedim > &tria, const Vector< Number > &criteria, const double threshold, const unsigned int max_to_mark=numbers::invalid_unsigned_int)
const std::vector< bool > & used
spacedim & mesh
Definition grid_tools.h:980
double diameter(const Triangulation< dim, spacedim > &tria)
for(unsigned int j=best_vertex+1;j< vertices.size();++j) if(vertices_to_use[j])
@ matrix
Contents is actually a matrix.
@ general
No special properties.
void mass_matrix(FullMatrix< double > &M, const FEValuesBase< dim > &fe, const double factor=1.)
Definition l2.h:57
void apply_boundary_values(const std::map< types::global_dof_index, number > &boundary_values, SparseMatrix< number > &matrix, Vector< number > &solution, Vector< number > &right_hand_side, const bool eliminate_columns=true)
Point< spacedim > point(const gp_Pnt &p, const double tolerance=1e-10)
Definition utilities.cc:191
Tensor< 2, dim, Number > F(const Tensor< 2, dim, Number > &Grad_u)
void interpolate(const Mapping< dim, spacedim > &mapping, const DoFHandler< dim, spacedim > &dof, const Function< spacedim, typename VectorType::value_type > &function, VectorType &vec, const ComponentMask &component_mask={})
void interpolate_boundary_values(const Mapping< dim, spacedim > &mapping, const DoFHandler< dim, spacedim > &dof, const std::map< types::boundary_id, const Function< spacedim, number > * > &function_map, std::map< types::global_dof_index, number > &boundary_values, const ComponentMask &component_mask={})
void create_right_hand_side(const Mapping< dim, spacedim > &mapping, const DoFHandler< dim, spacedim > &dof, const Quadrature< dim > &q, const Function< spacedim, typename VectorType::value_type > &rhs, VectorType &rhs_vector, const AffineConstraints< typename VectorType::value_type > &constraints=AffineConstraints< typename VectorType::value_type >())
void run(const Iterator &begin, const std_cxx20::type_identity_t< Iterator > &end, Worker worker, Copier copier, const ScratchData &sample_scratch_data, const CopyData &sample_copy_data, const unsigned int queue_length, const unsigned int chunk_size)
const InputIterator OutputIterator out
Definition parallel.h:167
const Iterator const std_cxx20::type_identity_t< Iterator > & end
Definition parallel.h:610
const InputIterator OutputIterator const Function & function
Definition parallel.h:168
const ::parallel::distributed::Triangulation< dim, spacedim > * triangulation
DEAL_II_HOST constexpr SymmetricTensor< 2, dim, Number > invert(const SymmetricTensor< 2, dim, Number > &)