On 4/26/19 2:28 PM, 'Maxi Miller' via deal.II User Group wrote: > I think the current version is the smallest version I can get. It will work > for a single thread, but not for two or more threads.
I tried to run this on my machine, but I don't have NOX as part of my Trilinos installation. That might have to wait for next week. But I think there is still room for making the program shorter. The point is that the parts of the program that run before the error happens do not actually have to make sense. For example, could you replace your own boundary values class by ZeroFunction? Instead of assembling something real, could you just use the identity matrix on each cell? Other things you don't need: Timers, convergence tables, etc. Which of the parameters you set in solve_for_NOX() are necessary? (Necessary to reproduce the bug; I know they're necessary for your application, but that's irrelevant here.) Could you replace building the residual by just putting random stuff in the vector? Similarly, the computeJacobian and following functions really just check conditions, but when you run the program to illustrate the bug you're chasing, do these checks trigger? If not, remove them, then remove the calls to these functions (because they don't do anything any more), then remove the whole function. I think there's still room to make this program smaller by at least a factor of 2 or 3 or 4 :-) 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]. For more options, visit https://groups.google.com/d/optout.
