Bug report in queue placeoffset

Question

question

Steven Hamoen asked Jul 5, '19 Matthew Gillespie answered Jul 10, '19

Bug report in queue placeoffset

if you have the queue placement option as "stack inside queue" and you call placeoffsetx() to find out where a taskexecuter is travelling to and after that you actually create the unload task you will see that the crane is not going to the same location as the first time you call placeoffsetx. If the time between the calls to placeoffsetx is not 0 then it will give you a different location everytime you call it. Test model is attached. Problem lies most likely in the calculateNextLocation function.

bugqueueplaceoffset.fsm

Software Version:

FlexSim 19.1.1

queue placeoffsetx

bugqueueplaceoffset.fsm (31.4 KiB)

· 1

Benjamin W2 commented · Jul 05, 2019 at 04:02 PM

Hi @steven.hamoen,

I will forward this on to our developers. Thank you for pointing it out!

0 ·

Answer 1 · 2019-07-10T19:51:58Z

Matthew Gillespie answered Jul 10, '19

The Stack Inside option works very differently than the other item placement options. This is because the queue caches data from the last call to getPlaceOffset() in internal variables.

Consider the following model: placeoffset.fsm. The operators can all walk to the correct location despite there being multiple people walking towards the queue before they actually place any items. We don't want to get rid of this feature.

We'll add this case to the dev list so we can consider if there's anything we need to do about it.

A workaround you can use if you need it is to write a couple lines of code after the placeoffsetx() call in order to clear the queue's cached data. To do this you need to change the queue's input or output stat and then call updatelocations(). See the attached model.

placeoffsetworkaround.fsm

placeoffset.fsm (105.5 KiB)

placeoffsetworkaround.fsm (31.7 KiB)

question