HasSpace Return Value Changes Based on Stacking Order??

[stan_e_davis]

[ FlexSim 22.2.2 ]

I am using the HasSpace method in a Find Slot activity. With a X+ > Y+ > Z+ stacking order, the HasSpace is failing to find space for 4 items when there is still plenty of space in the rack (1 slot per bay).

It appears it is returning 0 because the items' dimension would exceed the boundary at the back of the rack...

However, if I change the stacking order to X+ > Z+ > Y+, HasSpace finds space for all items...

With the X+ > Y+ > Z+ stacking order, if HasSpace can't find space on the first row, why doesn't it simply find space by starting a second row??

It seems you'll eventually you'll run into the same problem described above regardless of the stacking method. Thanks - Stan

[jason_lightfoot_adsk]

In my quick test it observes the stacking order - can you post your test model?

[joerg_vogel_HsH]

@Stan Davis , method hasSpace has got a really simple character. It keeps item orientation and stack each item accordingly the order. Optimizing space and produce a compact block is not its metric. You see it in Jasons picture. There are many holes and some items look like if they are floating.

[stan_e_davis]

Jason, pls see attached model. I sanitized & scaled it down for submission, but it retains its issue.

The Find Slot's query also uses PartNo labels which are cleared and applied via 'Clear-Rack_Paint' and 'Update_Paint_Rack' respectively

The size of the items is controlled by the DimTable.

The items will be stored for certain changes in size.

I also discovered if the 4 remaining items (Grapes) are placed in the front of the arrival list, they are stored in the rack.

It's a mystery.

Thanks - Stan

Find Slot HasSpace Issue - 10OCT22.fsm

[stan_e_davis]

Understood. I'm not expecting optimization just placement when there is truly space. Thanks

[Jeanette_Fullmer]

Hello @Stan Davis

Something went wrong in your upload. It shows the text in the body of your reply for a model but there is no attachment. Can you please upload again?

[stan_e_davis]

File re-uploaded. - Stan

[FelixMoehlmann · Accepted solution]

I can corroborate the observation. This looks like a bug/oversight. It appears that if there is already at least one item in the current "row" and the next item would fit beside it going by its x-size but not by its y-size, the hasSpace method returns a false instead of checking if the item could be placed in a new layer.

This makes sense when the "row" is the first one, because the item not fitting in the y-dimension would mean that it is longer than the rack is deep. But for further rows the rack depth will be different from the available depth.

Blue would fit beside green in the x-direction but not y. -> Blue stays in the queue.

If blue is the first item in the "row", it is placed in a new layer.

[stan_e_davis]

Thanks Felix.

[Jeanette_Fullmer]

I will send this in as a bug to the dev team.

[stan_e_davis]

Thanks Jeanette.

[Matthew_Gillespie]

@Stan Davis @Felix Möhlmann This bug has been fixed for 22.0.10 which comes out next week.