Wrong statistic graphics in process flow

Question

question

Cindy Azuero asked Aug 30 2016 at 7:52 PM Jason Merschat commented Nov 17 2016 at 5:08 PM

Wrong statistic graphics in process flow

outputperhour.fsmI was trying to obtain the output per minute statistic from an activity on the process flow. First I attempt to Pin the output statistic of the activity to the dashboard and then I modify the graph properties as follow.

I though that this will return the output value after every minute has passed.

Then I realized that that is not the same as output per minute, because I thought it was only taking the last data of output in the range I established. So, I used the predefined option of the library for process flow statistics called Output per hour and I realized it has the same configuration as the one I configured above. In this manner of facts, I realize that the graph is not really calculating the output per hour. To confirm that, I create the same statistic using the objects from the 3D view where a know the statistic is well calculated and as I expected the graphics are different.

I'm sending you the model where I test this.

Software Version:

FlexSim 16.1.2

process flow statistics

outputperhour.fsm (22.4 KiB)

pin-to-dashboard.png (12.3 KiB)

· 4

Matt Long commented · Sep 06 2016 at 5:04 PM

It does look like the chart is including both ends of the minute, so when you're using 10 second intervals that cause the output to charge on exactly the minute, you're seeing a larger value than expected. We'll put this on the dev list, but if you're using numbers that do not land you write on the minute, you will see the correct output per minute value.

2 ·

Cindy Azuero Matt Long commented · Sep 06 2016 at 7:39 PM

I don't understand exactly what are you refering to.

0 ·

Matt Long Cindy Azuero commented · Sep 06 2016 at 9:14 PM

I was just responding to what you said about 'the graph is not really calculating the output per hour'. The value you're seeing in the Process Flow chart should be 24 per hour but you're getting 28 which is just due to your delay time being exactly 10 seconds causing a total of 28 tokens to be leaving the zone in the span of 60 seconds. Where as you would expect it to be 24 tokens, 4 tokens every 10 seconds.

1 ·

Jason Merschat commented · Nov 17 2016 at 5:08 PM

I agree with Cindy. This canned time series graph shows cumulative output and not a rate (output per hour) I am looking to have a time series of output per hour as a rate not as a cumulative over time. Whatever the intent is, it is not translating to us users.

I submit that the Output per Hour bar graph does indeed show instantaneous output per hour, and that is what I am aiming to capture in a time series.

0 ·

______

Cookie preferences

Your privacy is important to us and so is an optimal experience. To help us customize information and build applications, we collect data about your use of this site.

May we collect and use your data?

Learn more about the Third Party Services we use and our Privacy Statement.

Strictly necessary – required for our site to work and to provide services to you

These cookies allow us to record your preferences or login information, respond to your requests or fulfill items in your shopping cart.

YES

Improve your experience – allows us to show you what is relevant to you

These cookies enable us to provide enhanced functionality and personalization. They may be set by us or by third party providers whose services we use to deliver information and experiences tailored to you. If you do not allow these cookies, some or all of these services may not be available for you.

YES

NO

Customize your advertising – permits us to offer targeted advertising to you

These cookies collect data about you based on your activities and interests in order to show you relevant ads and to track effectiveness. By collecting this data, the ads you see will be more tailored to your interests. If you do not allow these cookies, you will experience less targeted advertising.

YES

NO

Are you sure you want a less customized experience?

We can access your data only if you select "yes" for the categories on the previous screen. This lets us tailor our marketing so that it's more relevant for you. You can change your settings at any time by visiting our privacy statement

Your experience. Your choice.

We care about your privacy. The data we collect helps us understand how you use our products, what information you might be interested in, and what we can improve to make your engagement with Autodesk more rewarding.

May we collect and use your data to tailor your experience?

Explore the benefits of a customized experience by managing your privacy settings for this site or visit our Privacy Statement to learn more about your options.

Answer 1 · 2016-09-06T17:02:41Z

Matt Long answered Sep 06 2016 at 5:02 PM Matt Long commented Sep 28 2016 at 1:00 PM

The two graphs are different. The standard Content vs Time graph that you set up to be Output Per Minute is doing calculating the output per hour as the model runs. You could think of this as more of a running average. The equation that chart is using to get each of its data points is:

output / (time / 60)

The Process Flow chart is giving you the actual Output Per Minute. It does this by recording the output each time it changes and then graphing the last minutes worth of data.

If you want to display a graph of the output / (time / 60) using Process Flow, you can write that data to a tracked variable and then graph the tracked variable. Create a Tracked Variable through the Toolbox with the Level type. Then somewhere in your Process Flow add the code:

treenode delay = getactivity(processFlow, "Delay");
settrackedvariable("OutputPerMin", getstat(delay, "Output", STAT_CURRENT) / (time() / 60.0));

Then create a Tracked Variable vs Time chart in the Dashboard that is linked to your OutputPerMin tracked variable.

· 7

Cindy Azuero commented · Sep 06 2016 at 7:36 PM

Thanks

0 ·

Cindy Azuero commented · Sep 27 2016 at 10:42 PM

@Matt Long which place could be "somewhere in your Process Flow"? I try to put this after the delay in a custom code, but I realize that the graph must be constructed every second...

0 ·

Matt Long Cindy Azuero commented · Sep 27 2016 at 10:54 PM

Well it's all dependent on what kind of precision you want in your graph. If you want it to be calculated every second, just add a Schedule Source or use a Create Tokens to kick off a token that goes through a Delay of 1 second and then to a Custom Code to write to the tracked variable, then loop it back through the Delay.

1 ·

Cindy Azuero Matt Long commented · Sep 27 2016 at 11:04 PM

yes, I try that, but I have a question. In this model if I use a delay with 1 second it is problematic, but if I use a delay of 30 seconds it works fine. Which could be the cause?

graph with delay 1 second:

graph with delay 30 seconds:

0 ·

delay-1-s.png (20.2 KiB)

delay-30-s.png (18.0 KiB)

Show more comments

Cindy Azuero commented · Sep 27 2016 at 11:11 PM

About your question "Over that length of time are the results that much different doing a larger time interval?" the results do not change a lot, Its just a question in order to determine the time delay when i want hours. I just wanna know if there is any rule about it. I can us a bigger time interval.

0 ·

Matt Long Cindy Azuero commented · Sep 28 2016 at 1:00 PM

It's a bug that needs to be addressed, it's just a more difficult problem than one might expect. As for a rule, no, really it's just trying out a time interval and seeing if it works. A lot of it will depend on how long you're running your model for.

1 ·

Answer 2 · 2016-08-30T22:06:22Z

Adrian Haws answered Aug 30 2016 at 10:06 PM Cindy Azuero commented Sep 06 2016 at 2:13 PM

Cindy,

That's right, that's how it's supposed to work. The "Output per Hour" for a Process Flow activity displays the output value for the last hour (or whatever time unit you have set) while this statistic for a fixed resource displays the average output per such time unit over the entire run time.

If you want to display an activity's average output per minute, you can create a text display in your Process Flow and enter code similar to this:

treenode delay = getactivity(processFlow, "Delay");
if (time() == 0)
	return 0;
return getstat(delay, "Output", STAT_CURRENT) / (time() / 60.0);

See example model below.

output-per-hour-1.fsm (20.2 KiB)

· 1

question