Hello Eric,
Are you under WindowsXP ?
I believe your might have a few more problems with your setup - I will just mention two for now and advise on the solution depending on your answer ...
Problem 1: I noted that your working directory is C:\ ...
Problem 2: WindowsXP has a default registry setup on the number of access to the same file ...
But first an introduction note:
Your cluster should be capable of running TELEMAC under the following conditions (and we have other Windows users who do operate under these conditions):
- a run in parallel on one computer Xo, launched from a DOS command on that same computer Xo (what you are doing at the moment)
- a run in parallel on one computer Y, launched from a DOS command on another computer Xo
- a run in parallel on two or more computers, Xo, X1,X2, ..., launched from a DOS command on one of the same computers, for example Xo
- a run in parallel on two or more computers, Yo,Y1,Y2, ..., launched from a DOS command on another computer Xo
The version and compilation of TELEMAC that you use under the configurations above is the one you access through the DOS command - i.e. Xo. The important/critical point here is that you will get a much better speed-up if you split your computation over all your computers, even if you use one 1 core/processor of each computer. You can actually setup a default mpi_telemac.cong file to include:
Xo 1
Y1 1
y2 1
...
and use more core of each processor (I would advise not more than 2 for quad-core intel)
Last but not least -- where do you store your input/output files (related to Problem 1). This is where you need drive mapping.
Say your files are on Zo, say a Windows Server 2003 computer, you have to map the directory (or one of the root directories including all your TELEMAC project/simulation files) to a letter on the computer you are running the DOS command from, say using the letter T:. But that is not enough -- you need also all the other computers on the cluster to understand T:\...\..\..\files as being the same absolute location of your files, which implies you need to map in the exact same way, the same directory, using the same letter T: on all computers within the cluster (or all those you will use in your simulation).
In your case, while C:\TELEMAC\TestMultiProc is a location known by computer Xo, it does not reference the same absolute location on computer Y1 - C:\TELEMAC\TestMultiProc might not even exist on Y1.
However, having setup this configuration for many users, I have noted that storing your file on a distant server could slow down your simulation dramatically. It would be much faster if the files where stored on one of the computers of your cluster. The procedure above remains exactly the same, in that your need to map with the same letter, the same location on all computers, including Xo, where the files could be. If you do not have enough disk space to store all project files on one computer, you can store this on different computers, then using different letters, for each location or individuals to point to that individual's or project's location.
It does not matter whether your simulation files are where the TELEMAC install is.
Regarding Problem 2, WindowsXP has a manufactured maximum number of accesses to the same file. To allow WindowsXP (and the most recent patch solve this) to get up to 4 connection (running TELEMAC with 4 core, whether on the same computer or not) you need to change a couple of registry keys. Ideally, to get up to many more connection, you need to store your files on a Windows Server 2003 (and above). Windows Server allows for more than 4 connections.
You can do the tests using your organisation’s file server computers even if it is much slower. Ideally you need one of your cluster PC to be a file sharing system. Note that I have seen configuration where the file sharing system is a linux Samba installed on a PC, dual-booted with standard WindowsXP. Samba will authorise the multiple connections. But this gets into expert IT ...
Hope this helps
Sébastien.
