This is old DOUG wiki, please go to http://www.dougdevel.org/trac/wiki
Running
From DOUGWiki
Contents |
Running
Intel fortran
- Most tested, usually runs correctly
G95
- Runs correctly, but may give some warning messages like
Remaining memory: 40 bytes allocated at line 982 of datatypes/SpMtx/SpMtx_operation.F90 Remaining memory: 24 bytes allocated at line 988 of datatypes/SpMtx/SpMtx_operation.F90
GFortran
- Some cases fail to run, mostly because of not nullified fortran pointers.
- The problem is http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=369547. As said there resolved in gfortran 4.1 by specifying marker length in FCFLAGS (see Compiling).
Description of Control File Parameters
General
- solver
- which solver to use (1 - CG, 2 - Preconditioned CG)
- method
- which preconditioning method to use (0 - no preconditioning, 1 - Additive Schwarz, >1 - multiplicative Schwarz)
- input_type
- input matrix representation (1 - elemental, 2 - assembled)
- solve_maxiters
- maximum number if CG iterations
- solve_tolerance
- error tolerance in CG
- levels
- levels of preconditioner (1 - only first(fine)-level, 2 - coarse level preconditioner as well)
- overlap
- smoothers
Example of DOUG control file
solver 2 solve_maxiters 1000 solve_tolerance 1.0e-10 method 1 levels 2 overlap -1 smoothers 0 input_type 2 symmstruct T symmnumeric T # ################### # aggregate level 1: radius1 2 strong1 0.67e0 minasize1 2 #maxasize1 19 # aggregate level 2: radius2 2 strong2 0.67e0 minasize2 2 #maxasize2 96 # ################### matrix_type 1 number_of_blocks 1 initial_guess 2 start_vec_file ./NOT.DEFINED.start_vec_file start_vec_type 2 solution_format 1 solution_file ./solution.dat #debug -5 debug 0 verbose 3 plotting 0 assembled_mtx_file Lap4x4.txt assembled_mtx_format 0 assembled_rhs_format 1 assembled_rhs_file ./rhs.dat
Debugging
Using IDB
Attaching to local
- Run DOUG in MPI verbose mode
- mpirun -v -np 1 /home/olegus/uni/DOUG/doug/src/main/doug_main
- Find PID in output
- Run IDB
- libtool --mode=execute idb -gdb doug_main
- Attach to pid with attach GDB command
