People acting strange after using an ENTR

[gforney]

Application Version: 5.4.2
SVN Revision Number: 4957
Compile Date: 19 Oct 2009
Operating System: Windows XP Professional Version 2002

Hey, could somebody please delete the file model6a.1.fds and my 
earlier question? I uploaded a newer version of the file (test1.fds) 
but somehow the people are still acting strange. 
I have two DOOR-to-ENTR connections between rooms and after entering 
the second room through the entrance, the people turn their faces back 
to the entrance and ignore the flow field or slowly walk along a wall 
(face turned to the wall) before turning around and walking to the 
EXIT (normal speed again). 
Could someone please take a look at this? (check smoke view, this is not 
normal!) 
Thank you! 

Original issue reported on code.google.com by Pukie.Vanderra on 2009-12-08 14:25:13

---

• Attachment: Test1.fds

[gforney]

Timo will take a look at this.

Original issue reported on code.google.com by mcgratta on 2009-12-08 14:38:12

[gforney]

Are you using the latest version of FDS?

Fire Dynamics Simulator
Version: 5.4.3; MPI Disabled; OpenMP Disabled
SVN Revision Number: 5210
Compile Date: Thu, 03 Dec 2009

gives an error for me:

ERROR: EXIT line RightExit problem with XYZ, inside solid

Well, I took the "XYZ"s away (the default is the midpoin
of XB and about 5cm "in front of the door"). Now it seems
to run.

And there is something wrong in you input also. You do not
need to have door ==> entr for the "internal doors" within
a floor. You could use just HOLEs with "EVACUATION=.TRUE."
to make the floor as one "evacuation zone". If you want
to have the internal doors like door ==> entr, then you
should define each of your rooms (you have three rooms)
to be as an evacuation zone. So, should define for
each room its own main evacuation mesh. door==>entr
is used to move agents from one main evacuation mesh
to some other one.

See the IMO test case 10, where you have many "rooms"
in a floor (actually, cabins in this case, you know, IMO...)
http://virtual.vtt.fi/virtual/proj6/fdsevac/imo_fds5.html

and the door algorithm verification test
(check the latest "online" manual, where you
have more information about the case)
http://www.vtt.fi/proj/fdsevac/fdsevac_validation.jsp
and there "Verification of Some Submodels" and "DoorAlgo"
http://virtual.vtt.fi/virtual/proj6/fdsevac/fds5/examples/DoorAlgo_A.fds
So, one floor is "one evacuation zone" usually, so you should have
"holes" connecting every room, where agents might be or go.

If your building is having two (or more) "completely" separate parts,
then you could model these with two separate (might be overlapping)
main evacuation meshes. This means that agents can not go from
one part to the other part (or at least they should not go in
your evacuation scenario).

TimoK

Original issue reported on code.google.com by tkorhon1 on 2009-12-08 15:40:23

[gforney]

Thank you very much, I will try that. I was trying out the different connections 
(training)...

Original issue reported on code.google.com by Pukie.Vanderra on 2009-12-08 16:34:31

[gforney]

Well, if you want to keep everything in one main evacuation
mesh and still have the door ==> entr connections as before,
then you should have outflow vents at the "internal" doors,
i.e., at the DOORs in your rooms. And, of course, also at
the final EXIT. The main evacuation mesh should have all
VENTs. An outflow VENT is not seen as a solid wall by an
agent and, thus, the agent can walk throught these "walls",
i.e., they are able to cross the DOOR/EXIT. Otherwise the 
agents would face repulsive forces from the walls.

By doing this you create a bad "guiding flow field" for
the agents in the main evacuation mesh, so you should give
EVAC input so that the main evacuation mesh field is not
used, so you should always have some known and/or visible
doors available to the agents.

And you need three additional door flow fields (EVAC_HUMANS=.FALSE.,
which is the default, and EVACUATION=.TRUE.), because you have
three doors/exits. Each of these additional "door flow fields" 
have just one outflow vent, and it is at the door/exit in question.

So, you could use DOOR==>ENTR but it is usually better just open
the doors (or walls or whatever) with EVACUATION=.TRUE. HOLEs.
But it is nice to know, that you can also do things like I said
above. There might be cases, where you have no other option than
doing things in that way. (no other option = not an easy way)

TimoK

Original issue reported on code.google.com by tkorhon1 on 2009-12-09 13:18:18

[gforney]

Hi,
I know use the latest fds version and I removed the DOORs and ENTRs and just added

HOLEs in the OBST (instead of the DOOR/ENTR connections) and everything is perfect

now. Thank you very much! As the DOOR/ENTR connections are not necessary (and will

probably not be necessary for the type op calculations I'll be doing) I won't use 
them any more (I still can't find my mistake).
Thank you very much.
L

Original issue reported on code.google.com by Pukie.Vanderra on 2009-12-09 17:24:30

[gforney]

This issue was not a "bug" in the programme, but
more or less user support, i.e., instructions how
to use the programme. So, I'll close this Issue.

TimoK

Original issue reported on code.google.com by tkorhon1 on 2009-12-10 09:36:49