Doubt on pull from list partition

Question

question

SudheerReddy asked Jun 07 2020 at 7:24 PM Matt Long commented Jun 19 2020 at 3:08 PM

Doubt on pull from list partition

Below image shows the list with partition before pulling.

After pulling from Partition Id 1. The entire PartitionID is vanished. Once the Partition ID is created even it is empty I would like to keep in the list. Is there any way to do that. Wait for Event which triggers onPartitionInputChange. But since the partionID is going it is not triggering.I am attaching the model for reference.

PullPartistions.fsm

I tried using Keep Empty Partitions but still the partitions are going from the list.

Software Version:

FlexSim 20.1.2

flexsim 20.1.2 pull from list

partition1.png (15.9 KiB)

partition2.png (10.9 KiB)

trigger.png (19.7 KiB)

part3.png (19.2 KiB)

pullpartistions.fsm (47.6 KiB)

· 3

tannerp commented · Jun 09 2020 at 3:49 PM

@Sudheer Reddy @Jordan Johnson The Keep Empty Partitions works for Item Lists when using 3D objects to push and pull, but it doesn't work in Process Flow for some reason. I've attached the model I used to test.

pullpartistions (2)_1.fsm

1 ·

pullpartistions-2-1.fsm (36.4 KiB)

Matt Long tannerp commented · Jun 19 2020 at 3:21 AM

The reason your Partition ID: 1 remains in the entries of your global list is because there is an active back order for that partition. The partition would disappear with no entries and no back orders in it.

0 ·

SudheerReddy commented · Jun 18 2020 at 5:47 PM

@Jordan Johnson is that bug?

0 ·

Answer 1 · 2020-06-19T03:18:53Z

Matt Long answered Jun 19 2020 at 3:18 AM Matt Long commented Jun 19 2020 at 3:08 PM

The Pull from List is working correctly. The partition is being saved, however, it doesn't show up in the List when there are no entries in the partition. This was a conscious decision to ensure the entries table isn't full of a bunch of empty partitions. The partition node is moved into a deadPartitions node so that it can retain all of its statistics. This is really the only reason to check the Keep Empty Partitions. It doesn't affect anything else.

The issue that's occurring is that there seems to be a bug in the Wait for Event. When it tries to add a listener to partition 1, it actually gets partition 0. Hence why the listener is never fired. I've added this to the dev list so we can get it fixed. As for a workaround until the fix is released, you can listen to the On Push event and set the Partition ID value to 1 with an Operation of match value. This will have the same effect.

1592536729576.png (9.4 KiB)

· 4

Matt Long commented · Jun 19 2020 at 3:08 PM

Alternatively, you can change the List shared asset to point to a Global List, and then use the Wait for Event to listen to the On Partition Input Change on the global list rather than the List shared asset. This works.

1 ·

SudheerReddy commented · Jun 19 2020 at 6:39 AM

@Matt Long

thanks for the detailed explanation. I have one follow up query

In below image Keep Empty Partitions checkbox is there. If Empty partitions are not visible in the list then what is the use of this feature as highlighted in below image.

0 ·

1592548388512.png (39.5 KiB)

Matt Long SudheerReddy commented · Jun 19 2020 at 12:05 PM

If you look at the tooltip, or hit the help button down at the bottom, it explains what that is used for. From the User Manual:

Keep Empty Partitions

If checked, the list will never remove partitions, even if they are empty. This is useful if you want to keep statistics on a specific partition. However, depending on how many unique partitions are created on the list, this can use significant amounts of memory.

0 ·

SudheerReddy Matt Long commented · Jun 19 2020 at 12:16 PM

@Matt Long

Yes I checked this in my model but still it is removing the empty partitions. For this particular reason only I asked this question.

But in your answer you specified as

The Pull from List is working correctly. The partition is being saved, however, it doesn't show up in the List when there are no entries in the partition. This was a conscious decision to ensure the entries table isn't full of a bunch of empty partitions. The partition node is moved into a deadPartitions node so that it can retain all of its statistics. This is really the only reason to check the Keep Empty Partitions. It doesn't affect anything else.

As you can see in below image I checked the Keep Empty Partition list but still the partition id is missing

0 ·

question