Global Lookup Table refreshes on reset to non-zero values

Question

question

Pieter Cecat asked May 15, '17 Pieter Cecat commented May 16, '17

Global Lookup Table refreshes on reset to non-zero values

Hi everyone,

Each time I reset my model, one of my global lookup tables resets/refreshes to a bunch of non-zero values (always the same values though). The 'clear on reset' box is unchecked so it should not do this. Anyone any idea why this happens?

Thanks in advance!

Software Version:

FlexSim 16.0.9

reset global lookup table

· 2

Pieter Cecat commented · May 15, 2017 at 03:27 PM

It might help to say that I have not defined the values that appear in that table anywhere else... All help is appreciated.

0 ·

Pieter Cecat commented · May 16, 2017 at 02:23 AM

Does anyone know what might cause the problem? I have looked for the issue but can't seem to find it..

Thanks in advance for your time!!

0 ·

Answer 1 · 2017-05-15T15:31:44Z

Steven Hamoen answered May 15, '17 Pieter Cecat commented May 16, '17

@Pieter Cecat

Could you share the model? Or otherwise send it by mail to me? I will take a look then.

· 3

Pieter Cecat commented · May 15, 2017 at 03:39 PM

2m.fsm

Hi @steven.hamoen

The problem is at the 'Monthly Demand' table, more specifically the FIRST ROW: fixed. This row should have different values than those that are now entered. However, every time I reset the model, it gives the same values over and over again.

The second row is calculated during the simulation using the process flow in my model and displays random numbers with mean 25 and standard deviation 3. This data overwrites the numbers that are on reset still in the second row. There is no issue for that row.

Thanks for your help!!

0 ·

2m.fsm (68.5 KiB)

Steven Hamoen commented · May 16, 2017 at 07:34 AM

@Pieter Cecat If you look at your experimenter you will see that you have selected Scenario 4 as your default reset scenario. So every time on reset it will put those values into the "fixed" row of your table. If you change the reset scenario to "none" your problem is gone

0 ·

Pieter Cecat Steven Hamoen commented · May 16, 2017 at 10:53 AM

Thank you @steven.hamoen for your quick reply!

0 ·

question