question

Eric D5 avatar image
0 Likes"
Eric D5 asked tannerp commented

Child token reference overwritten?

Error happens at 35.05. Operator id:1 is working on task id:8. When the task is completed, the child of token id:2 gets written over to id:8. This only shows up when checking with the script; it does not show when looking at the token. Work in Process code at "Release Token: Other Operators Waiting".


Here is what I am trying to do: This is a simplified version of my primary model, where operators have their own logic, pulling from a global task list. I am trying to add coordinated tasks. If a task required multiple operators, the first operator to pull the task will ask for help from others by adding additional tasks.

This seemed to work until I put 3 tasks in a row, requiring 2 operators each. They are at a standstill, all waiting for each other. ("Operators Work - No Cancel" logic and OpQty = 2 for row 1-3 on table "Worklist")

I tried to add some cancel task logic; so far it works with two operators, but issues arise when I try to add a third or more. If the primary operator asks for two assistants and gives up before getting assistant #2, I would like to send assistant #1 to return looking for work. The error occurs when trying to reference child tokens (tasks) of the primary operator. I need to reference these tasks to ultimately reference the task pullers (assistants).

Am I hitting a bug or what is going on?

OR is there a much better way to do this?

process-time_multiple-operators.fsm

FlexSim 20.1.2
flexsim 20.1.2bugcoordinated task sequences
· 2
5 |100000

Up to 12 attachments (including images) can be used with a maximum of 23.8 MiB each and 47.7 MiB total.

tannerp avatar image tannerp commented ·
@Eric D5,

I've been trying to dig through the model and understand exactly what's going on. It might be useful to set up a Zoom call in which we can talk through the issue because I'm not sure I quite get it yet. The biggest thing that stands out to me is the error that's showing. It indicates that the Release Token: Other Operators Waiting activity has a bad token reference. I looked at it, and it looks like an operator is being returned; not a token. The token reference should be a reference to a token, not an operator. If you fix this, it might just work as is.

I'd start there and see if you can get that to work because otherwise, the tokens are at a standstill. If you can't get that to work, let me know and we can set up a Zoom call.

0 Likes 0 ·
Eric D5 avatar image Eric D5 commented ·

@tanner.p

I am getting the error when trying to access the child tokens (tasks) of the parent token (operator), before I even get a chance to look at the operator token (task puller).

I am available for a zoom call anytime today.

0 Likes 0 ·

0 Answers

·

Write an Answer

Hint: Notify or tag a user in this post by typing @username.

Up to 12 attachments (including images) can be used with a maximum of 23.8 MiB each and 47.7 MiB total.