Kill second splitted token after first token reaches the join

Question

question

Jesús López asked Feb 2, '24 Felix Möhlmann commented Feb 3, '24

Kill second splitted token after first token reaches the join

Hi,

I'm fairly new to flexsim. Is there a way to end a split just after one of the tokens arrives at the join? In my model I want the operator to either wait until there are more than 2 boxes in the queue 1 or after a certain amount of time has passed. As seen, with a normal split the operator waits for both tokes to arrive. Is there a way to "kill" the second token after the first has arrived at the join?

Thank you

Software Version:

FlexSim 24.0.1

process flow split fastest path

fastest-lane.fsm (53.5 KiB)

Answer 1 · 2024-02-03T06:46:22Z

Joerg Vogel answered Feb 3, '24

You have two event states:

by amount
by time.

If one is successful, then the other becomes invalid.

You can preempt invalid tokens to a sink. Alternatively you can add labels to them and compare them against process label values later before any purposefully actions occurs, if they are still valid. If they are not then divert an involved invalid token to a sink.
I would suggest not to split a token rather than to create another, because split activities expect a join combination. If you delete one involved token before it gets joined then this can result in unresolved errors.
Split, Synchronize and Join are activities when you want to fulfill stages simultaneously.

If you need a coupled relation of tokens, then use parent child mechanism. Please test, what happens if one looses its existence. And what you have to do to keep data available, if one of them is destroyed and when.

Answer 2 · 2024-02-03T13:59:26Z

Jesús López answered Feb 3, '24 Felix Möhlmann commented Feb 3, '24

Fastest lane.fsm

Thank you Mr. Vogel,

you were correct in avoiding the split and join option. Instead I built a kind of loop asking both questions. It might not be very elegant, but it does the job.

fastest-lane.fsm (53.9 KiB)

· 2

Jesús López commented · Feb 03 at 02:04 PM

The label Waiting has to be put back to zero when more than 2 loads before 60 s. I corrected that.

0 ·

Felix Möhlmann Jesús López commented · Feb 03 at 04:56 PM

You can actually replace that entire loop with a single Pull from List activity by giving it a maximum wait time and leaving the pulled entries on the list.

fastest-lane_1.fsm

The same "Use Max Wait Timer" option is available in Wait for Event activities.

2 ·

fastest-lane-1.fsm (52.4 KiB)

question