Thanks for all the answers. John Peterson <[email protected]> writes:
> On Thu, Apr 4, 2013 at 8:50 AM, Martin Luethi <[email protected]> wrote: >> The subject says it all: how are PETSC options set at the command line? >> I don't see anything setting for example >> >> ./example-opt -log_summary > > So if you're running examples, you can do > > LIBMESH_OPTIONS="-ksp_monitor -pc_type lu" ./run > > in the example directory, and it will pick up those options... Yes, for example examples/fem_system/ex1 If I try out the above line, the script nicely echoes the options, but nothing happens. This is with fairly recent Petsc (3.3_p6) and Libmesh 2f856d8e4bd03018347de0d24697fa1eb1a73456 (20 March 2013). Might this be that options are eaten by GetPot? I just tried the Petsc examples, and there log_summary and ksp_monitor work nicely. I'll try upgrading and recompiling Libmesh, hoping this helps. Thanks, Martin ------------------------------------------------------------------------------ Minimize network downtime and maximize team effectiveness. Reduce network management and security costs.Learn how to hire the most talented Cisco Certified professionals. Visit the Employer Resources Portal http://www.cisco.com/web/learning/employer_resources/index.html _______________________________________________ Libmesh-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libmesh-users
