On 11/14/23 16:25, Alex Quinlan wrote:
I'm curious what your thoughts are on this approach. I imagine it could have
an advantage in some situations, depending on the size of the mesh and the
number of constraints to be added.
I have not done any speed testing on this yet, tho. Do you think it would be
looking into? Or do you see some fatal flaw with this approach?
Alex:
the general approach most professional programmers will ascribe to is to write
a version of the code that is intelligible and easy to maintain. Only then do
you worry about speed. If the code in question is fast enough (say at most of
few percent up to 20% of the program's run time -- as measured with a class
such as TimerOutput), then it's not worth worrying about it.
So the questions you're asking are premature. Make the code work what it is
you want it to do, and then you can think about its performance.
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 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/d1a3c21c-5c34-a138-5290-0d9a70576343%40colostate.edu.
