On Thu, Apr 4, 2013 at 2:24 PM, Martin Luethi <[email protected]> wrote: > 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
Try this: from your build directory, 1.) cd examples/fem_system/fem_system_ex1 2.) make check 3.) LIBMESH_OPTIONS="-ksp_monitor" make check The latter prints out all the KSP residual norms, the former does not... It seems that 'make check' is the only way to compile the examples(?) but it also involves running them. -- John ------------------------------------------------------------------------------ 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
