Dear developers/users,
I'm working on tutorial step 19, and I have some exact questions as well as some related follow-up questions. I'll list them here, and I would appreciate your help. 1. On line 313, there is the line “fe.shape_value(i, reference_location)”. The “reference_location” is defined from “particle.get_reference_location()”. “particle” is an instance of the “Particles::Particle” class, and the description of its “get_reference_location()” function says: "Return the reference location of this particle in its current cell.” My question is whether the reference location of the particle in its current cell refers to the real coordinates (x, y, z) or the reference coordinates (\xi_1, \xi_2, \xi_3) within the cell. 2. On line 509, 'cell->minimum_vertex_distance()', where 'cell' is defined by 'const auto &cell : dof_handler.active_cell_iterators()'. According to the documentation, 'cell' should be of type 'active_cell_iterator', because of ‘IteratorRange< active_cell_iterator > active_cell_iterators () const’ . However, I couldn't find 'minimum_vertex_distance()' as a method of 'active_cell_iterator' in the manual. What the exact type of 'cell' is and how it's able to access 'minimum_vertex_distance()'? 3. In the documentation, the FEValues<dim, spacedim> class template requires two template arguments, 'dim' and 'spacedim'. However, on lines 227 and 534, FEValues is instantiated with only one template argument, FEValues<dim>. Similarly, for ‘std::vector<Tensor<1, dim>> field_gradients(vertex_quadrature.size())’ on line 536, the Tensor class is used with two arguments. ‘fe_values.get_function_gradients(solution, field_gradients)’ on line 546 uses field_gradients. but the get_function_gradients in the documentaiton is ‘void FEValuesBase< dim, spacedim >::get_function_gradients ( const ReadVector< Number > & fe_function, std::vector< Tensor< 1, spacedim, Number > > & gradients ) const’ , the Tensor template appears to require three arguments. Why there is a discrepancy in the number of template arguments used in these instances? 4. In the inheritance diagram, what does the dashed yellow line represent? [image: Untitled.png] 5. In the 'Result' section of tutorial step-19, there's a simulation video. How can I create a similar animation, and what does the deep blue curve line in it represent? 6. In the ”make_grid()” function, four different boundary IDs are assigned to the boundaries. Is there a way I can visualize these boundaries in ParaView or VisIt, so that I can verify if the boundaries are set correctly? 7. When running code in deal.II, is there a way to enable a debug mode similar to MATLAB or other IDEs? I'd like to execute the code line by line starting from the main function, understand the program's logic, and check the values of parameters (e.g., vertex_quadrature.size()). This would help me gain a deeper understanding of what the program does. -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/dealii/2eac5ac4-9f0f-4003-99fd-edfce857cee9n%40googlegroups.com.