Bug with Process Flow Dashboards

Question

question

Cameron Pluim asked Oct 21, '16 Cameron Pluim commented Nov 23, '16

Bug with Process Flow Dashboards

There are actually 2 bugs here that I think are related. In the attached model you will find 2 processes that are identical as far as how they behave. One process is built with the standard Fixed resources, and the other is built using process flow.

If you run the model in it's current state, and push the button on the script window to execute the user command ExportTables(), you will get a folder in the model directory with .csv files for the queue content over time, and the zone request content over time.

The problem that I am seeing is that the zone request content over time is creating an empty (except for headers) file in the following 2 scenarios.

Close the dashboard window and run the model again. Then execute the script window again.
Run the experimenter. The script to run ExportTables() is in the End of Replication Trigger, so you do not need to do anything else.

In both of these scenarios you will find that the queue content is the same as if you run it with the dashboards open, but the zone request content is an empty file

processflowdashboards.fsm

Software Version:

FlexSim 16.2.1

process flow experimenter dashboards

processflowdashboards.fsm (22.6 KiB)

· 3

5 |100000

Attachments: Up to 12 attachments (including images) can be used with a maximum of 23.8 MiB each and 47.7 MiB total.

Sam Stubbs ♦ commented · Oct 21, 2016 at 03:44 PM

@jordan.johnson

0 ·

Cameron Pluim commented · Nov 14, 2016 at 02:22 PM

I just checked in the new beta for 2017, and this is still a problem.

0 ·

Cameron Pluim Cameron Pluim commented · Nov 23, 2016 at 02:40 PM

@jordan.johnson @Matt Long, Do you know if this is being looked into at all?

0 ·

Answer 1 · 2016-11-23T16:59:56Z

Jordan Johnson answered Nov 23, '16 Cameron Pluim commented Nov 23, '16

Sorry for the delay! I fixed this issue; the next beta/release should have the fix.

As a workaround for now, add this code into ExportTables(), before you call "createCSV" for the request chart:

treenode dummy = nodeinsertinto(node("Tools", model()));
function_s(node("/Tools/Statistics/RequestContent",model()), "getData",dummy);
destroyobject(dummy);

The "getData" function kicks the chart, so that it will update the internal data that it's keeping.

· 1

5 |100000

Attachments: Up to 12 attachments (including images) can be used with a maximum of 23.8 MiB each and 47.7 MiB total.

Cameron Pluim commented · Nov 23, 2016 at 05:04 PM

Thanks @jordan.johnson!

0 ·

question