Ok, few DAKOTA issues here,
1) I tried running DAKOTA on CAHABA (note: mpirun in CAHABA is taken from /usr/local/lam/7.0.5/pgi/4.0/PBSPro/5.4.0/bin/mpirun) for some example test cases given along with the distribution and it gave me the same MPI_Init error message at the end.
so i used mpich mpirun in CAHABA i.e (mpirun taken from /usr/local/mpich/1.2.6/gnu/3.4.0/PBSPro/5.4.0/smp/bin/mpirun) and it ran without any MPI_Init error message at the end. This worked even for np greater than 1 as well.
on cahaba:
/usr/local/mpich/1.2.6/gnu/3.4.0/PBSPro/5.4.0/smp/bin/mpirun -np 2 dakota -i dakota_pce.in
works fine !!
When i tried the same on medusa i.e
/opt/mpich/gnu/bin/mpirun -np 1 /share/apps/Dakota/bin/dakota -i dakota_rosenbrock_ls.in
i got the error:
p0_7676: p4_error: interrupt SIGSEGV: 11
When we submit a job on CAHABA with a PBS job file, it generates a jobfile.e and jobfile.o file at the completion of the job run, which provides some information like Job ID, Username, Group, Job Name, Session, Limits, Resources, Queue and Account (this will be in jobfile.o , jobfile.e will have any error messages if present). I went through my simulation results i have done in cahaba and observed that all my jobfile.o files (wherever i have used mpirun) has that MPI_init error message. Since these .e and .o files were of no significance for my simulations, i had written a script to clear them soon after the job ends. I saw some surviving .e and .o files before i started using such scripts and was able to provide this information!!
2) Another issue which i saw in medusa is:
DAKOTA has two interface mechanisms with external codes a) Interface with an application 2) Interface with an approximation
Both interfaces writes and reads results to files for each iteration (note optimization is an iterative process).
For the many sample testcases in DAKOTA, reading and writing files takes place in /tmp directory. We can explicitly mention the file names to be created by giving the command:
parameters_file = 'params.in' \
results_file = 'results.out' \
anyway, what i started to say was i got the following error with the sample testcases in DAKOTA on medusa
Error: cannot open results file /tmp/fileOdjbhI
i guess this error will not be obtained when the external code path used in the input file will be given /share/apps/Dakota/path to code , as done in dakota_rosenbrock_ls.in testcase.
Do we have an issue with the mpich mpirun version we are using in medusa ?
Thanks,
Vinay Rao
_______________________________________________
Devel mailing list
Devel@metric.it.uab.edu
http://metric.it.uab.edu/mailman/listinfo/devel
