From: Subhasis R. <ray...@gm...> - 2012-11-23 06:04:40
|
Hi Saeed, On Fri, Nov 23, 2012 at 12:05 AM, Saeed Shariati <s.s...@uf...>wrote: > I am new in Moose and I want to involve in development specially in > optimization and HPC side. > Welcome to the group. For this case, I need to execute application from shell or in a batch mode. > Executing from GUI is not a good way to measure the execution time. > You can run MOOSE simulations without the GUI. Read the documentations. > > Is the any profiling mechanism or any suggestion to check the execution > time of a model in the case of optimization? > You can compile it with profiling support. You need to look at the Makefile and edit it. I am not aware of any specific profiling mechanism built into MOOSE. Valgrind works, but it may be prohibitively slow. A simulation is executed by the start() function [ interfaced to shell/Shell.cpp: Shell::doStart(...) ]. Again, you can get better idea by first reading the documentation and then reading the code. You can use gdb (with a debug-build of MOOSE) to step through the code to some extent and understand how it works. One warning though, do not use debug builds of Python, the PyMOOSE interface will fail with an assertion error in the Python interpreter. Best, Subha |