Hi, does anybody have a good Explanation why the "deceleration" option in different Task Executers work different?
Attached is a model in which all Task Executers have an acceleration of 1 but a deceleration of 0.1. The deceleration seems to be called in the first TE only on it´s frist travel. The second TE does it allways. Operator same like Transporter never do it!?
For what it is worth, I explained what is happening here to Sebastian offline. Here's a summary:
The default travel tasks given to the task executer when using Use Transport have a desired end speed of "the maximum speed of the task executer" (see var1 of TASKTYPE_TRAVEL).
This causes the task executers to not start to decelerate until they finish their travel task and start performing their load or unload tasks. With a really low deceleration value and very little room to decelerate between when the travel finished and when they arrive at the load/unload location, the task executers that have a Navigator are moving a lot faster than the task executers without a Navigator because the task executers without a Navigator aren't doing the travel tasks at all and are instead immediately starting their load/unload tasks with a lot more space to decelerate.
After examining your model, I found that because Task Executer 1 was assigned to a Default Network Navigator, it was not looking to its own properties and obeying the deceleration rule which you set. I removed the Network and now the Task Executors behave the same.
Thanks. I´ve got some Questions on this:
1. I did not add a Default Network Navigator -> is it added in standard?
2. Who made this answer the best answer? Is it only because it is the only answer?
3. What is wrong with all other TE´s?
1. Here's where the setting is found to assign a Navigator to a TE:
I believe it is default and is therefore applied automatically. As to how to change the default settings, I'm not sure. I would need @jordan.johnson or @phil.bobo to help explain the code behind it.
2. I'm not sure who accepted this answer, but sometimes when we don't receive feedback for an extended period of time, the only answer available is accepted.
3. Could you clarify what you mean when you say there's something "wrong" with them? Are you referring to their deceleration as well?
1. You are right, if I change the option in the field to "none" the TaskExecuter1 is showing the complete same behavior like TaskExecuter2. But it also is not using the Network at all, so expect it should work so because now it is the same Szenario like the one with TaskExecuter2.
2. Shouldn´t I be the only one who accept an answer for my question?
3. The deceleration seems to be called in the first TE only on it´s frist travel. The second TE does it always. Operator same like Transporter never do it!? I´ve used standard settings for all Szenarios. So is it wrong if I expect completely same behavior for all of them?
10 People are following this question.
FlexSim can help you understand and improve any system or process. Transform your existing data into accurate predictions.
FlexSim is a fully 3D simulation software environment. FlexSim can be used to simulate any process in any industry.
FlexSim®, FlexSim Healthcare™, Problem Solved.®, the FlexSim logo, the FlexSim X-mark, and the FlexSim Healthcare logo with stylized Caduceus mark are trademarks of FlexSim Software Products, Inc. All rights reserved.
