I want to track Input Vs Output per day on a single graph as we do in excel.
I have attached the model for your reference.
Here is a model that has the graph you want:
inputvsoutputgraph-updated.fsm
The key is to understand how the time plot expects data to be formatted, and then to build a table in that format.
In the Statistics Collector, every time the timer event fires, I create an array of stats that I want to get. Then I set that array as the row value. Since the row value is an array, the Statistics Collector makes more than one row each timer event. The row value contains the name of the statistic. So one row will have the Input stat, and the other will have the output stat. This format can be accepted by the Timeplot chart.
Hello Jordan,
I have used your concept for getting the results as per my requirement.
PFA the model for your reference
Hello Jordan,
Can you Upload the Example for FlexSim 18.1.2? I have kind of the same issue, but can not open it.
Is it also possible to do this, if i get my values of different tracked variables?
Hi @luca.s4,
The model attached to @jordan.johnson's answer is for version 19.0. You could open this model in any version of FlexSim 19.0 or later to examine what he did and recreate it in your older version of FlexSim.
There have been various upgrades and changes to statistics collectors over the years, and I'm not sure whether the things that Jordan did to solve this in version 19.0 would translate directly back to 18.1. You can always check and see. Or perhaps Jordan will see that I notified him and weigh in (you should always @mention someone using the @ symbol for the best chance at getting their attention).
Lastly, commenting on a long dormant question that has an accepted answer is generally not best practice, even if your comment is directly related. The way we track these issues doesn't lend itself to a comment like this being readily noticed and responded to. In the future, it would be better to begin a fresh question, and link back to this previous one for context. A new question that needs an answer is always easier to spot than an old, answered question with a new, easy to miss comment. See more community best practices.
Yes, the same method should work in version 18.1.2. With Tracked Variables, it is even easier. On the timer event, return an array with all the tracked variables you want. Column 1 can contain the time. Column 2 can show the name of the tracked variable:
data.rowValue.name
Column 3 can show the current value of that tracked variable
data.rowValue.as(TrackedVariable).value
Something like that should work.
11 People are following this question.
