ATTENTION

This FlexSim Community Forum is read-only. Please post any new questions, ideas, or discussions to our new community (we call it Answers) at https://answers.flexsim.com/. Our new Question & Answer site brings a modern, mobile-friendly interface and more focus on getting answers quickly. There are a few differences between how our new Q&A community works vs. a classic, threaded-conversation-style forum like the one below, so be sure to read our Answers Best Practices.


flexsim.com

Go Back   FlexSim Community Forum > FlexSim Software > Q&A
Downloads

Q&A Using Flexsim and building models

  #1  
Old 02-22-2016
David Besson David Besson is offline
Flexsim User
 
Join Date: Feb 2011
Posts: 7
Downloads: 1
Uploads: 0
Thanks: 3
Thanked 0 Times in 0 Posts
Rep Power: 0
David Besson is on a distinguished road
Post TASKTYPE_BREAK vs TASKTYPE_CALLSUBTASKS

Hello,

I do not understand the difference between TASKTYPE_BREAK and TASKTYPE_CALLSUBTASKS.

Here is an extract about CALLSUBTASKS task according to the FlexSim user manual (Task Sequences / Reference / Task Sequence Types):
Quote:
This task is just like the break task, except that it ensures that as soon as the second task sequence is finished, it will return immediately to the next task of the original task sequence
But with BREAK tasks, the TaskExecuter will also return to the next task of the original task sequence. As it is mentioned in the FlexSim user manual (Pick Lists / TaskExecuters / Break To):
Quote:
When the TaskExecuter receives a "Break" task, this is a notification that it may now put the currently active task sequence back in its queue and see if there are any other task sequences that it might want to do before it finishes the current one.
So are the two task types identical on this point?

The only differences I see are:
  1. to specify whether or not the content of the TaskExecuter should be screened before performing the break task (for the "break" task, var1)
  2. to specify whether or not the TaskExecuter should check to receive task sequences from an upstream Dispatcher (for the "break" task, var2)

Am I right?

Thanks for your reply!
David
  #2  
Old 02-22-2016
michaelsmith michaelsmith is offline
TMN Simulation -Australia
 
Join Date: Aug 2007
Location: Hobart Tasmania
Posts: 62
Downloads: 7
Uploads: 0
Thanks: 31
Thanked 19 Times in 12 Posts
Rep Power: 170
michaelsmith will become famous soon enough
Default

Call Sub Tasks allows you to call and choose sub tasks from within the current TS where as the Break allows the TE to break to other tasks.

Sub Tasks can be used when the destination and states of downstream processes/resources are unknown at the time the TS is created You could for instance decide at a Call Sub Tasks to proceed to a waiting area or direct to the destination when your reached a point in the travel.

Some of the functionality and it's uses will become simpler with the Task Sequence section of the Process Flow Library.
The Following 2 Users Say Thank You to michaelsmith For This Useful Post:
Sebastian Hemmann (02-23-2016)

Tags
break callsubtasks


Thread Thread Starter Forum Replies Last Post
question about TASKTYPE_BREAK LINWEIXU Q&A 5 08-05-2009 02:43 AM
TASKTYPE_BREAK qin tian Q&A 2 10-25-2008 11:46 PM
About TASKTYPE_CALLSUBTASKS qin tian Q&A 1 10-13-2008 08:15 AM


All times are GMT -6.
Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2020, vBulletin Solutions Inc.
Copyright 1993-2018 FlexSim Software Products, Inc.