debug
Differences
This shows you the differences between two versions of the page.
| debug [2013/02/28 13:32] – created daniel | debug [2013/03/01 08:37] (current) – daniel | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | For debugging there are some very basic options already available in '' | + | ====== Debugging ====== |
| + | ---- | ||
| + | For debugging there are some very basic options already available in //potfit//: | ||
| - | If you compile | + | If you compile |
| - | * For every configuration the box vectors, normals and heights are written to stdout. There the number of periodic images needed is also given. | + | |
| - | * The different optimization algorithms give more details while they are running. For the meaning of the numbers please take a look at the source code. All additional output is enclosed in <tt>#ifdef DEBUG</ | + | * The different optimization algorithms give more details while they are running. For the meaning of the numbers please take a look at the source code. All additional output is enclosed in '' |
| If you need additional output of variables or other things, you will have to do this manually in the sourcecode. | If you need additional output of variables or other things, you will have to do this manually in the sourcecode. | ||
| - | ==== Profiling ==== | + | === Profiling |
| - | + | ||
| - | In the Makefile there are some options to enable profiling support in the binaries. This can be activated with the < | + | |
| - | + | ||
| - | [[Category: | + | |
| + | In the Makefile there are some options to enable profiling support in the binaries. This can be activated with the '' | ||
debug.1362054774.txt.gz · Last modified: 2013/02/28 13:32 by daniel
