Question about Action Timer
Posted: Monday 21 November, 2016 - 08:49
Hello,
I’ve got a problem with the Action timer and their connection to Local obstacles (or Passageways).
With a first Action timer I want to reset the run clock, trigger all agents in the system and update local obstacles, like there was an incident. This works like a charm.
After that I want a second (or even more) Action timer to update more local obstacles. This is currently not working at all. Since my first AT will have an event time like 1-3 hours and the second ones 6-12 minutes, the second one is usually faster or doesn’t work at all.
I can imagine two possibilities how this could work but I cannot implement it.
First: The first AT should trigger the second AT within the “Event Trigger” menu. So the settings for the second AT first starts counting when the first AT updated the system. This is similar to how the local obstacles get updated.
Second: If possible, I would make an If-Statement within the "Event time" of the second AT. The query would look after the incident time (the red clock). So if 0,1 or 6 minutes elapsed than the second AT should start counting. The problem is, I can only think that "RunClock_GetEvacuationTime(c)" is suitable for this one but it won't work.
If there is a more elegant method, I appreciate it to. See the provided model as an example for the basic idea.
A question besides:
The agents aren’t allowed to walk past the local obstacles. If you look in the provided model this is working. But instead searching for another way out, they just keep running against the local obstacle. Passageways seem like to do a better job, so I guess i should place those, if I want to block a route?
Best regards,
Ralf
I’ve got a problem with the Action timer and their connection to Local obstacles (or Passageways).
With a first Action timer I want to reset the run clock, trigger all agents in the system and update local obstacles, like there was an incident. This works like a charm.
After that I want a second (or even more) Action timer to update more local obstacles. This is currently not working at all. Since my first AT will have an event time like 1-3 hours and the second ones 6-12 minutes, the second one is usually faster or doesn’t work at all.
I can imagine two possibilities how this could work but I cannot implement it.
First: The first AT should trigger the second AT within the “Event Trigger” menu. So the settings for the second AT first starts counting when the first AT updated the system. This is similar to how the local obstacles get updated.
Second: If possible, I would make an If-Statement within the "Event time" of the second AT. The query would look after the incident time (the red clock). So if 0,1 or 6 minutes elapsed than the second AT should start counting. The problem is, I can only think that "RunClock_GetEvacuationTime(c)" is suitable for this one but it won't work.
If there is a more elegant method, I appreciate it to. See the provided model as an example for the basic idea.
A question besides:
The agents aren’t allowed to walk past the local obstacles. If you look in the provided model this is working. But instead searching for another way out, they just keep running against the local obstacle. Passageways seem like to do a better job, so I guess i should place those, if I want to block a route?
Best regards,
Ralf