Maxi, I know that both components will behave quite differently, thus I assumed > that I have to use two grids. > Having to deal with two grids always creates a lot of overhead for the coupling terms. So you normally want to avoid this if you can.
> In addition I was interested in how both parameters evolve over time. If I > need only one grid, then I still have to store them separately, but it > would be closer to example 33, wouldn't it? > In step-33 you only have one DoFHandler in combination with a FESystem that stores all components for all variables. In particular, these variables are stored in one common Vector<double>. This is the approach I would suggest unless you have special requirements. Of course, you can also use BlockSparseMatrix objects and BlockVector objects instead if you want to be able to access the individual components more easily. This approach is shown in step-22 [1]. Best, Daniel [1] https://www.dealii.org/8.5.0/doxygen/deal.II/step_22.html -- 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
