Possible bug in batch process when changing batch size

Question

question

christian.n asked Nov 30, '16 Ben Wilson commented Dec 1, '16

Possible bug in batch process when changing batch size

Hey FlexSim

We have found an irregularity in the batching activity.

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

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:

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.

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

Can anyone take a guess at what happens?

Thanks in advance.

Christian

Software Version:

FlexSim 16.2.2

bug report

screenshot0052.jpg (30.0 KiB)

screenshot0051.jpg (36.2 KiB)

screenshot0054.jpg (45.1 KiB)

batcherrortest.fsm (16.9 KiB)

Answer 1 · 2016-11-30T20:51:22Z

Matt Long answered Nov 30, '16 Ben Wilson commented Dec 1, '16

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.

· 1

christian.n commented · Dec 01, 2016 at 07:03 AM

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 ·

question