Vikram just cooked up a nice new libMesh example to demonstrate his
multiphysics weighted adjoint residual error estimator, decided he'd
try out the new DirichletBoundary code in the process... and ran into
the natural problem when he discovered that the solver happily
enforced the requested heterogenous Dirichlet constraints even in the
adjoint problem where he wanted (and where penalty-method based codes
would have automatically produced) homogeneous constraints instead.
So this is going to take some changes. My best idea so far is to have
the adjoint_solve "back up" and zero out the right hand side values on
any heterogenous constraints, then do the solve, then restore the
backups before returning. Any thoughts? I'm somewhat concerned about
any possible weird interactions with arbitrary additions via
System::user_constrain().
---
Roy
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Libmesh-devel mailing list
Libmesh-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libmesh-devel
