EVAC) exit selection algorithm
375 views
Skip to first unread message
spring-tiger
Apr 28, 2016, 12:13:07 AM4/28/16
to FDS and Smokeview Discussions
I attached input file. this file is from EVAC web site and modified on some lines.
I know that the default Herding Type is 'conservative type'.
In this case, how do persons on 1st floor determine their target door ?
I think that the other door is closer than that they actually are used.
What is their strategy for selecting target ?
Thank you in advance.
FDS 6.4.0
TimoK
May 3, 2016, 6:07:48 AM5/3/16
to FDS and Smokeview Discussions
Well, in your case the agents do not have any known door in the upper floor.
In this case, the agent picks up some door at the floor. Well, seems to be the
first door of that floor given in the input file. If there are both exits and doors
in the given floor, then the first exit given in the input file or the first door
given in the input file is used. I do not remember if EXITs or DOORs are
read in first.
So, if there is no visible nor known door => pick some "random" guiding
flow field towards some door/exit. This could be made more specific,
but this is the way that it is now programmed.
TimoK
In this case, the agent picks up some door at the floor. Well, seems to be the
first door of that floor given in the input file. If there are both exits and doors
in the given floor, then the first exit given in the input file or the first door
given in the input file is used. I do not remember if EXITs or DOORs are
read in first.
So, if there is no visible nor known door => pick some "random" guiding
flow field towards some door/exit. This could be made more specific,
but this is the way that it is now programmed.
TimoK
spring-tiger
May 4, 2016, 5:56:25 AM5/4/16
to FDS and Smokeview Discussions
Thank you very much !
2016년 5월 3일 화요일 오후 7시 7분 48초 UTC+9, TimoK 님의 말:
2016년 5월 3일 화요일 오후 7시 7분 48초 UTC+9, TimoK 님의 말:
Peng
Jun 17, 2016, 12:07:35 AM6/17/16
to FDS and Smokeview Discussions
It seems that an agent pick up the nearest known door or exit in the door selection algorithm, but it is not clear how the the herding charateristics get involved. Does the herding happen when the agent does not know any door or exit? Thanks a lot.
在 2016年5月4日星期三 UTC+8下午5:56:25，spring-tiger写道：
TimoK
Jun 17, 2016, 4:22:55 AM6/17/16
to FDS and Smokeview Discussions
Hi!
There is some explanation on the herding behaviour and different agent types
in the FDS+Evac Readme.txt file: http://virtual.vtt.fi/virtual/proj6/fdsevac/documents/Readme.txt
Yes, the default agent type picks usually the nearest known door. If there are a long queue on
this door, then the agent might try some other known door. If there are no known doors
available (at this floor), then default agent picks the nearest visible door, usually. If there
is a long queue, then the other visible doors are also considered.
The herding behaviour for the default agents (and for the rational agents) is only applied,
when there is no available known nor visible door. So, if an agent does know see/know
where to go, it sees where the others are going.
=======================================
User Input Changes, Evac 2.3.1 vs 2.3.0
=======================================
*) Added herding behaviour for agents.
EVAC-namelist:
AGENT_TYPE: Default is 2
1 rational agents (visible doors and known doors equal)
2 known doors first, then the visible ones (like in the manual)
3 herding (choose the door that the others are using if no known doors given)
PERS-namelist: I_HERDING_TYPE=0 (default)
0: default herding (follow the default flow field if no door found)
1: keep the first choice (follow the default flow field if no door found)
2: do not move, if no door found
3: do not move, if no door found + keep the first choice
(keep the first choice: If the agent does NOT know/see any door then it tries
to check the other agents. If it finds this way a door, then it does not
try anymore to find any other door. The other mode of operation is that
the agent constantly sees what the others are doing around and changes
its mind accordingly, if no known or visible door available.)
FYI: I added "NOT" above. It has been missing in the Readme.txt file...
And some other explanation: "does not know/see" is there for the
normal and rational agents. Herding agents "do no see doors", they
just use known doors. If there is no available known door, then herding
agents are "lost" and they must see, what others are doing.
And there is nowadays fourth agent type, AGENT_TYPE=4:
Agent type 4 may follow others if they find that door to better than their own choice.
This means that if the agents in front are going towards a visible door, then the
agent type 4 agents considers this visible door to be a known door in its door
selection algorithm. If the door of the other agents is not visible, then the agent
type 4 agent does not consider this door (it is not set as known door).
I should add this to the Readme.txt file. And I should make verification
example cases for all of these different agent types and herding types.
After this I could add them in the manual. Well, I might add them to
the manual and add note, that they are not yet verified. So, the user
should check that they work as they should.
Wbr,
Timo
There is some explanation on the herding behaviour and different agent types
in the FDS+Evac Readme.txt file: http://virtual.vtt.fi/virtual/proj6/fdsevac/documents/Readme.txt
Yes, the default agent type picks usually the nearest known door. If there are a long queue on
this door, then the agent might try some other known door. If there are no known doors
available (at this floor), then default agent picks the nearest visible door, usually. If there
is a long queue, then the other visible doors are also considered.
The herding behaviour for the default agents (and for the rational agents) is only applied,
when there is no available known nor visible door. So, if an agent does know see/know
where to go, it sees where the others are going.
=======================================
User Input Changes, Evac 2.3.1 vs 2.3.0
=======================================
*) Added herding behaviour for agents.
EVAC-namelist:
AGENT_TYPE: Default is 2
1 rational agents (visible doors and known doors equal)
2 known doors first, then the visible ones (like in the manual)
3 herding (choose the door that the others are using if no known doors given)
PERS-namelist: I_HERDING_TYPE=0 (default)
0: default herding (follow the default flow field if no door found)
1: keep the first choice (follow the default flow field if no door found)
2: do not move, if no door found
3: do not move, if no door found + keep the first choice
(keep the first choice: If the agent does NOT know/see any door then it tries
to check the other agents. If it finds this way a door, then it does not
try anymore to find any other door. The other mode of operation is that
the agent constantly sees what the others are doing around and changes
its mind accordingly, if no known or visible door available.)
FYI: I added "NOT" above. It has been missing in the Readme.txt file...
And some other explanation: "does not know/see" is there for the
normal and rational agents. Herding agents "do no see doors", they
just use known doors. If there is no available known door, then herding
agents are "lost" and they must see, what others are doing.
And there is nowadays fourth agent type, AGENT_TYPE=4:
Agent type 4 may follow others if they find that door to better than their own choice.
This means that if the agents in front are going towards a visible door, then the
agent type 4 agents considers this visible door to be a known door in its door
selection algorithm. If the door of the other agents is not visible, then the agent
type 4 agent does not consider this door (it is not set as known door).
I should add this to the Readme.txt file. And I should make verification
example cases for all of these different agent types and herding types.
After this I could add them in the manual. Well, I might add them to
the manual and add note, that they are not yet verified. So, the user
should check that they work as they should.
Wbr,
Timo
Reply all
Reply to author
Forward
0 new messages