forrtl: severe (29): file not found

[SteveG]

Hi,

I am attempting to get parallel processing working on our windows XP
machines. Both running FDS5 (latest) and MPICH2 (latest). I'm running
the program from the MPICH2 GUI interface and get the following
output:

Process 0 of 1 is running on FDS1.company.local
Process 1 of 1 is running on fds2.company.local
Mesh 1 is assigned to Process 0
Mesh 2 is assigned to Process 1
forrtl: severe (29): file not found, unit 4, file C:\MPITEST\OPG1.smv
Image PC Routine Line
Source
fds5_mpi.exe 006D548A Unknown Unknown Unknown
fds5_mpi.exe 006D2D45 Unknown Unknown Unknown
fds5_mpi.exe 00674FAC Unknown Unknown Unknown
fds5_mpi.exe 00674AE5 Unknown Unknown Unknown
fds5_mpi.exe 00663C8F Unknown Unknown Unknown
fds5_mpi.exe 00559B21 Unknown Unknown Unknown
fds5_mpi.exe 00629060 Unknown Unknown Unknown
fds5_mpi.exe 006D94E1 Unknown Unknown Unknown
fds5_mpi.exe 006BBADF Unknown Unknown Unknown
kernel32.dll 7C816FD7 Unknown Unknown Unknown

Both computers have full read/write access to the working directories
and firewalls are disabled.
Any help or guidance on this would be greatly appreciated!

Thanks!
Steve G.

[Kevin]

OPG1.smv is the Smokeview input file that FDS writes. It appears as if
one of the processes cannot find this file or does not have access to
it. Can you run this case on one machine only?

[SteveG]

Yes, I used this case because it had previously been run successfully
on one machine.
Does the .smv file need to exist on both machines? or does Machine 2
write to the file that exists on Machine 1?

I have turned on every read/write permission I could find on both
computers and created the working folders right in the root of the C:\
drive to try to limit any pathname issues.

[Andrew Louie]

can you post the contents of the config.txt file, or the exact command
you used to start this parallel simulation?

--
-Andrew Louie :wq
--雷恩銘

[SteveG]

I started the simulation using the GUI interface of MPICH2
I now have the simulation running, I tried copying the OPG1.smv file
that was created on machine 1 (this file was created when I tried to
run the simulation the first time and got the error) onto machine 2.

Machines 1 and 2 are now creating distinctly named output files
however the smokeview file on both machines has the same name so I'm
not sure what that will look like after the simulation is complete.

[SteveG]

Apologies I forgot to give you the command line from the Interface

C:\Program Files\MPICH2\bin\mpiexec.exe" -wdir C:\MPITEST -hosts 2
fds1 fds2 -noprompt C:\MPITEST\fds5_mpi.exe opg1.fds

[Kevin]

Do you mean that there are two working directories? Normally, the
parallel version writes to one working directory that exists on one of
the machines. It can be seen and written to by the other machine. If
you have it configured so that you are using independent working
directories, set

SHARED_FILE_SYSTEM=.FALSE.

on the MISC line. This tells FDS to break up the .smv file and
distribute it to the individual machines. To view the output, you need
to catenate the .smv's together again into CHID.smv

> > > --雷恩銘- Hide quoted text -
>
> - Show quoted text -

[SteveG]

I originally did not have two working directories but was getting the
error that the specified directory did not exist on Machine 2.
Machine 2 has full read/write access to the working directory on
Machine 1.

Is there something I can configure so that the simulation runs using a
shared working directory?

> > - Show quoted text -- Hide quoted text -

[Andrew Louie]

for the command you are using to run the simulation:

>> > C:\Program Files\MPICH2\bin\mpiexec.exe" -wdir C:\MPITEST -hosts 2
>> > fds1 fds2 -noprompt C:\MPITEST\fds5_mpi.exe opg1.fds

Try using the network path name instead of the local name:
Instead of: "C:\WORKING_DIR" use "\\HOSTNAME\WORKING_DIR"
In your case:
instead of "C:\MPITEST" use "\\fds1\MPITEST"

Obivously make sure the folder "MPITEST" is shared and that the other
computer can access it.

mpiexec will simply pass the directory name to the other machines, and
the other machines will look on their own "C:\MPITEST" folders for the
required files, you want them to look for the files on the original
machine, fds1.

you should make this same change for the "C:\MPITEST\fds5_mpi.exe"

I think this should work.

2008/6/25 SteveG <stev...@gmail.com>:

--
-Andrew Louie :wq
--雷恩銘

[SteveG]

GENIUS!
It's working now with only 1 working directory
Thanks for your help!

On Jun 25, 5:28 pm, "Andrew Louie" <lou...@gmail.com> wrote:
> for the command you are using to run the simulation:
>
> >> > C:\Program Files\MPICH2\bin\mpiexec.exe" -wdir C:\MPITEST -hosts 2
> >> > fds1 fds2 -noprompt C:\MPITEST\fds5_mpi.exe opg1.fds
>
> Try using the network path name instead of the local name:
> Instead of: "C:\WORKING_DIR" use "\\HOSTNAME\WORKING_DIR"
> In your case:
> instead of "C:\MPITEST" use "\\fds1\MPITEST"
>
> Obivously make sure the folder "MPITEST" is shared and that the other
> computer can access it.
>
> mpiexec will simply pass the directory name to the other machines, and
> the other machines will look on their own "C:\MPITEST" folders for the
> required files, you want them to look for the files on the original
> machine, fds1.
>
> you should make this same change for the "C:\MPITEST\fds5_mpi.exe"
>
> I think this should work.
>

> 2008/6/25 SteveG <stevgr...@gmail.com>: