Possible bug in batch process when changing batch size

Possible bug in batch process when changing batch size

christian_norregaard
Not applicable
72 Views
2 Replies
Message 1 of 3

Possible bug in batch process when changing batch size

christian_norregaard
Not applicable

[ FlexSim 16.2.2 ]

Hey FlexSim

We have found an irregularity in the batching activity.

To illustrate the problem, here is a small sample model:

4006-screenshot0052.jpg

Two sources create tokens, representing two different machines. The tokens have three labels on them: "MachineNum", "QTY" and "BatchSize".

The tokens from Source1 have MachineNum = 1, QTY = 20 and BatchSize = 3. (Green tokens) The tokens from Source2 have MachineNum = 2, QTY = 20 and BatchSize = 2. (Blue tokens)

Initially, a couple of tokens from Source1 will arrive and then a couple of tokens from source 2 will arrive.

.The batching activity is set up like this:

4007-screenshot0051.jpg

The expected result from this model is that the tokens get split up into a number of tokens based on QTY and Batch Size. One token with QTY 20 and Batch Size 2 should turn in to 10 tokens with QTY 2 and so on.

When the tokens (With a new batch size) start arriving from Source2, something odd happens.

4008-screenshot0054.jpg

The batching process seems to be broken from this point on.

Can anyone take a guess at what happens?

Thanks in advance.

Christian

0 Likes
Accepted solutions (1)
73 Views
2 Replies
Replies (2)
Message 2 of 3

matt_long
Not applicable
Accepted solution

If you update your model to match your description:

"The tokens from Source1 have MachineNum = 1, QTY = 20 and BatchSize = 3. (Green tokens) The tokens from Source2 have MachineNum = 2, QTY = 20 and BatchSize = 2. (Blue tokens)"

then the model will run just fine. Right now you have both Source's output MachineNum = 1.

Your model does show a bug, however, when you have both token's set to MachineNum = 1. The issue has to do with the Batch Quantities being different. We have fixed the issue for the next version.

Message 3 of 3

christian_norregaard
Not applicable

Hey Matt.

The MachineNums being identical was my bad. The attached model was only a quickly built model to demonstrate the issue you described.

Thanks for always providing swift aid 🙂

0 Likes