All Trilinos support is still very much in development at this point. If you look closely you'll see that it is very incomplete and what is in there is just hacked up at this point. In particular, the NOX stuff is currently limited to solving Matrix Free at this point... with no capability for any preconditioning. Further, Aztec stuff hasn't been properly hooked up to accept the new "tolerance" scheme, so there is no way to change convergence tolerances.
These are just a coupled of the shortcomings... the point is... it's not done. Now... with that said... if you want to pitch in I would really appreciate the help! I don't currently have a good build of libmesh with trilinos to do any testing on the Laplace Young problem with NOX... but I'll be getting back to that soon. I was pretty sure though that everything was working in parallel when I last committed stuff... so I can't say off hand why it wouldn't work. I did a lot of work to make EpetraVector work properly in parallel... In summary, if you want to look closer into this and try to fix it yourself... feel free. Otherwise, it's going to be a bit before I can get back to it. If I can't replicate your problem with Laplace Young in parallel (which I'm sure I can) I'll ping you for some output. Thanks for trying this though! Hopefully Real Soon Now (tm) it will Just Work (R). ;-) Derek On Oct 14, 2008, at 7:51 AM, Norbert Stoop wrote: > Hi everybody, > > > I'm planning to use the Trilinos NOX solvers (and LOCA in particular) > to solve nonlinear buckling problems with special geometric boundary > conditions. > > I started playing around with the inofficial Young-Laplace example and > the latest libmesh SVN. The example works fine on a single CPU with > NOX, > but in parallel numeric errors occur along the interface between > subdomains calculated on different CPUs - I can send some GMV output > if > requested. > No problems occur when running the same in parallel with PETSc, and > linear problems also work perfectly with Trilinos/Aztec. > trilinos_nox_nonlinear_solver.C looks fine to me - could this be an > issue with the EpetraVector or EpetraMatrix in libmesh? > > > Thank in advance, > Norbert > > > > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's > challenge > Build the coolest Linux based applications with Moblin SDK & win > great prizes > Grand prize is a trip for two to an Open Source event anywhere in > the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > _______________________________________________ > Libmesh-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/libmesh-users ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Libmesh-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libmesh-users
