kashif8595 / pfs-fire

Automatically exported from code.google.com/p/pfs-fire
0 stars 0 forks source link

Running, minor issues #3

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
So far I have been successful in running the code and getting output.  I 
get a couple of minor errors when running some of the Monte Carlo 
simulations.

My simulation is suppose to simulate a 3 room fire.  A PPV fan in room 1, 
connects to the fire in Room 2.  A victim room is connected to the fire 
room.  My variables are window sizes in the fire and victim room, and the 
time venting occurs (PPV door, fire room window, victim window).

1.  When I make the correlation coefficients with the "correlation" action 
button:  a plot is generated with the correlations, but there is a Visual 
Basic error I have to terminate.  The plot looks correct, except it 
includes variables not used as random variables.  (see chart 1 on file)

2.  Any Monte Carlo simulation longer than 1000 seem to crash excel.

3.  My histogram plots of the output data do not run when I hit the "Make 
Histogram of Original Data", because I do not have the "ATPVBAEN.XLA" file?  
I have installed the Analysis Toolpak for excel, but do not know what that 
file is.

4.  Is there a way to monitor carbon monoxide (CO) or species outputs for a 
fire?

Thanks so much for making the code and the help!  =)

Original issue reported on code.google.com by pose...@gmail.com on 22 Nov 2009 at 7:13

Attachments:

GoogleCodeExporter commented 8 years ago
Hello! I'm not sure about the first two problems yet, but for:

3. From the 'Tools'-menu select 'Add-Ins...' and then activate
   the 'Analysis Toolbox'-checkbox.

4. I think this depends on the fire model you are using...

Original comment by atpaajan@gmail.com on 26 Nov 2009 at 8:47

GoogleCodeExporter commented 8 years ago
And for

1. Check the Number of Random Variables in the MC_RandomNumbers-sheet. All of 
the 
variables are included in the correlation bar graphs. The VB error message can 
be 
avoided by removing protection of the MC_ScalarOutput-sheet (Tools --> 
Protection --
> Unprotect Sheet). 

Original comment by atpaajan@gmail.com on 6 May 2010 at 8:59

GoogleCodeExporter commented 8 years ago

Original comment by atpaajan@gmail.com on 18 Oct 2010 at 7:34