diff options
| author | tradke <tradke@17b73243-c579-4c4c-a9d2-2d5706c11dac> | 2004-05-01 22:06:14 +0000 |
|---|---|---|
| committer | tradke <tradke@17b73243-c579-4c4c-a9d2-2d5706c11dac> | 2004-05-01 22:06:14 +0000 |
| commit | 62260e52a7ba71d831916afd195d261beec6c385 (patch) | |
| tree | 3e0460d58ca233771401e151dfa991cc31c93a76 /doc/FAQ | |
| parent | ed80ce68d35203f7fb3eeeaa1094226a4894ce7e (diff) | |
Added D12: Cactus with MPI on a single processor says:
"Unable to open parameter file ..."
git-svn-id: http://svn.cactuscode.org/flesh/trunk@3681 17b73243-c579-4c4c-a9d2-2d5706c11dac
Diffstat (limited to 'doc/FAQ')
| -rw-r--r-- | doc/FAQ | 20 |
1 files changed, 19 insertions, 1 deletions
@@ -1,7 +1,7 @@ Cactus Code Frequently Asked Questions -$Header: /mnt/data2/cvs2svn/cvs-repositories/Cactus/doc/FAQ,v 1.78 2004-03-22 02:29:31 allen Exp $ +$Header: /mnt/data2/cvs2svn/cvs-repositories/Cactus/doc/FAQ,v 1.79 2004-05-01 22:06:14 tradke Exp $ Also available at http://www.cactuscode.org/Documentation/FAQ @@ -197,6 +197,9 @@ D10 Output to screen using the Info IO method of IOBasic doesn't work. D11 I get an error saying "CCTK_Equals: First string null". +D12 I have a Cactus executable compiled with MPI. When running it on a single + processor (without using mpirun) I get an error saying "Unable to open + parameter file ...". ------------------------------------------------------------------------------ Thorn Writing: @@ -1211,6 +1214,21 @@ D11 I get an error saying "CCTK_Equals: First string null". Try to re-configure your application, perform a "make CONFIG-realclean", and then recompile. +D12 I have a Cactus executable compiled with MPI. When running it on a single + processor (without using mpirun) I get an error saying "Unable to open + parameter file ...". + + If you built Cactus with the ch_p4 device of the MPICH distribution + and then execute the program directly (without using mpirun), it will + start in the directory where the executable resides. + If you specified a relative path to your parameter file Cactus would + start searching for it from that directory (rather than the directory + you are currently working in) and then potentially not find it. + + The solution is to never run an MPICH ch_p4 executable directly but + always use mpirun. This will make sure that the program will start + in your current working directory. + ------------------------------------------------------------------------------ Thorn Writing: |