My first pass recommendation is to confirm that you have enough resources per computer to handle the requirements of the simulation.
Even though there is 2GB of physical RAM on a computer, does not mean that there will be enough available for all of the processes (OS overhead, etc).

These errors are always tricky, as it is not easy to determine if it is a hardware resource issue, an OS memory handling issue or a bug in the program itself.
Another approach is to step up incrementally from one mesh to all ten and see when it fails. 

Since this is happening before the first time step, my guess is that it is a memory overflow/error problem one one of the nodes in the network.

-Bryan

Bryan
The modelling is distributed over 7 computers all 32bit. Three of the computers handle 2 mesh each (6 no), the remainder of the computers (4 no) handle one mesh each. We have a network of computers which are used for Modelling. Most of them are quad core, few dual. The Minimum RAM is 2gig for dual core and higher for high specs.
I wont be able to tell you exactly which system has which spec as  i am not responding from workplace but can tell you tomorrow (UK time) if you want the specifics. let me know of you need that infor. 
R

I looked at the screenshots, but my questions still remain.
10 processes/meshes does not equal 10 computers, 10 processors (cores) or 10GB of RAM (minimum).

For a simulation like this, you would probably need to be running FDS on a 64bit computer with at least 16GB of RAM.
Or, you would need to have distributed it over a few separate computers each with enough RAM to handle the number of cells distributed to it.

As a rough estimate you will need about 1GB of RAM for each million grid cells.  As the number of millions increase, so does the overhead above the 1GB per million cell estimate.

Could you please give a bit more information about the computer(s) you are trying to run this on?

-Bryan

Bryan,
as you may see from the attached screen shot, there are ten processes each supposed to handle one mesh - that was why the domain is divided into ten mesh. 
I tried to make each mesh domain about a million cells each - although some are slightly more - in order to be within a million cells per core guidance.
R

Access violation 157 is usually due to some kind of memory read/write error.
With almost 10 million mesh cells, you may be running into out of bounds or overflow errors.

How many computers are you using to run the simulation?
How much memory is available on each computer?
How many meshes are you allocating to each computer?

-Bryan Klein

Hello,
when I am running parallel FDS I encountered a 157 ....... access violation error similar to one posted on http://www.thunderheadeng.net/forum/index.php/topic,304.msg543.html#msg543 thread previously. I had followed the advice on that thread and use FDS 5.4.3 but it still could not work.
 In order to isolate the problem I ran same model but with only one mesh ID (Fire zone) and it runs okay
Could you advise on what is likely going to be the problem?
The input file is attached.


PS - the screen dump of the error message and the successful single mesh run is attached.

Hi, tell me please, how to parallelize the calculation of 2 PCs.
At the core 1 PC I was able to, but as a PC?
Thank you

I spoke to the regular users of pathfinder at my company and found that with large models, turning off "heirarchical path planning" solved my problem.

If you are having an issue similar to this, I suggest turning it off to see if it solves the problem.

Hello,

I have an email into support already, but I might as well describe the problem here just in case anyone else has run across it:

I am building a model of a large assembly building, and I will have about 12000 occupants by the end.  I have all the geometry set and all the occupants are placed in the appropriate rooms.  When I try to run the simulation, "run time" runs at real time for about the first 40 seconds, then slows to about .2 or .1 seconds per second.  "Sim Time" never starts, after about 30 minutes of waiting.  I am used to the program churning out calculations in a minute or two, even for about 4000 occupants.  Has anyone run into the strange time problem in their travels with this program?

The DXF files I used for the background were quite large (100000 objects or so), so I deleted them after finishing the geometry, just in case that was the snag.  This made the "run time" run normally until the 60 second mark, but then it began the same problem of moving slowly.  Is the model just too large for the software to handle?

Is there some way of increasing the amount of memory the program can use, in case that is the issue?

Thanks for the help!

Hey there,

I am have problems using the Pyrosim interface to run parallel FDS simulations. It prompts me for my password, but when I enter it, it says invalid.

I searched the forum and saw that Pyrosim requires an password for MPI access. So I set my password for my administrator account (my only one).

I restarted my computer and tried to run parallel simulation again, and typed in my password when prompted, here is what it says:

Invalid username or password.
Parallel FDS was unable to start processes on this computer.

So I searched more threads and tried to run the simulation in CMD prompt, based on someone elses thread questions... i used the following cmd prompt and got the following error:

C:CEP FilesFire Model testfds>mpiexec -noprompt -port 52200 -priority 1:3 -channel ssm -n 4 fds5_mpi 11.fds

Error while connecting to host, No connection could be made because the target m
achine actively refused it. (10061)
Connect on sock (host=mike-PC, port=52200) failed, exhaused all end points
Unable to connect to ''mike-PC:52200'',
sock error: Error = -1


Help???

Regards,

Mike