Just to close this out in case others run into the same problem. The culprit was me declaring a local vector variable system_rhs in WaveEquation<dim>::run <https://www.dealii.org/current/doxygen/deal.II/namespaceWorkStream_1_1internal_1_1tbb__no__coloring.html#a8673698a405bf47aa24002aeb6d76d70> (). A careless mistake, which had the net effect of having my RHS just be zero since the global version of the variable, used in the solve function, is never touched or updated with anything. After that was addressed, I was able to tweak some typos and now the solution matches the tutorial and the case is closed.
I would like to ask about adding this approach to the tutorial of step 23 maybe at the bottom. For newcomers, it is not obvious how to deal with the 2nd order time derivative directly and there may be instances where my approach is better suited. It is also a much shorter program. Matt On Sat, 30 Jul 2022 at 22:47, Wolfgang Bangerth <[email protected]> wrote: > On 7/30/22 15:45, Matthew Rich wrote: > > > > I am trying a different time integration approach using the generalized > alpha > > method rather then reposing with a velocity variable. I am also > switching to > > the BC handled by affine constraints. > > > > I am not sure why the wave wont move through the mesh. I just see the BC > at > > the edge which quickly fades out in the tutorial. > > > > Any hints or nudges would be appreciated code attached. > > Matthew -- I think you're asking too much of us as well of yourself. In > essence, your question reads > I started with code X which I know works. Then I made substantial > changes > A, B, and C and the code is no longer working. Any help? > That's too many things at once one would have to check. Go back to the > original code and make one change at a time, then test. Make another check > and > test. Go on like this. If you work along this strategy, you know which > change > broke the functionality, and you can focus on these changes in trying to > figure out where the bug is. > > If, in addition, you use version control (via git or subversion or any > other > tool), you should commit every working version and you can always go back > to > that. You can also clearly identify what changes you have made and list > the > concrete lines where the newly introduced bug must be. > > Best > W. > > -- > ------------------------------------------------------------------------ > Wolfgang Bangerth email: [email protected] > 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 a topic in the > Google Groups "deal.II User Group" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/dealii/KD341CckGvc/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/dealii/b72eabc6-9e6e-227f-1b50-e228d411e268%40colostate.edu > . > -- 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/dealii/CAN3OR9pxGgiyX7bXiedQRj3YgBL3fp8rWnpnw%2BZkzjhPzR0XMw%40mail.gmail.com.
