"Restore data" in drawable line chart
|
|
Hi!
I'd like to use a drawable line chart for array data input. However, the restore data functionality (under chart settings menu in UI) does not work as I think it should. 1. User messes around with the graph and decides to restore (settings/restore) => the graph changes to how it was initially => user proceeds one step => the changes as they were before restoring still take effect 2. User messes around with the graph and decides to restore (settings/restore) => the graph changes to how it was initially => user makes a modification and then proceeds one step => the modified graph takes effect as it should So I think there's a problem with case 1 - or is the functionality there by purpose? Br, Anssi |
|
|
Hi Anssi,
This is a bug with the drawable line chart. It will be fixed with our next release on Monday 3/14 in the evening, so available during working hours 3/15 Billy |
|
|
Hi!
It's nice that you are able to provide fixes in such a rapid pace! I've recently noticed other problems related to drawable line chart... I can provide details if necessary or see if my problems are reproducable, but the basic problem is that the graph is not updated correctly. I have this test sim where I have both a drawable graph and numeric decision steppers for the same (decision) array variable. Initially they are consistent, but when the sim proceeds, the decision stepper values are updated correctly (i.e., according to the model logic) whereas the graph is not. As I said, I can give a more detailed description if necessary, but if you think this is related to my previous bug then I'd rather wait for the fix and see if things are ok afterwards. What do you think? Anssi |
|
|
Hi,
We are interested in tracking this (and all other) bugs down. Let me see if I can regurgitate to you what you have told me to double check that I understand the issue. Lets say you have a sim that has a lookup table; lets call it 'Lookup Table' You have a drawable line graph that sets the variable Lookup Table. In addition you have a numeric stepper which sets just one value of the lookup table, Lookup Table[5]. After changing the numeric stepper, the value of Lookup Table[5] on the drawable line graph does not update? Let me know if I described it right. If so I have a few suggestions for you to work through the issue Billy |
|
|
Hi!
I did some testing and in the simple case that you described and the drawable graph updates just fine. However, I was able to reproduce the bug (or maybe it's my model that's wrong, IDK), see: http://forio.com/simulate/anssi.kaki/array-test-2/ The idea of the example is that we have a "sales plan" for 5 periods. In each step, user can adjust the plan for next two periods with array variable Adjusted plan. So initially (STEP=0), the user can adjust Sales[1] and Sales[2] with the auxiliary variable, in STEP=1 Sales[2] and Sales[3], and so on... When the sim starts, the graph and numeric steppers show consistently values (50,200). Now three cases are possible: 1) User does not adjust the values and proceeds one step. Result: numeric steppers are updated and figure is not. I find this confusing, even if the model logic would be wrong, since they essentially should show the same values, i.e. the values of Adjustes Sales array. 2) User adjusts the numeric stepper values, e.g. puts in 250 to Adjustes sales[1] and advances one step. Now everything is updated, but the numeric steppers are initialized (correctly) with values Sales[2] and Sales[3], whereas drawable graph shows updated Sales[1] and Sales[2]. 3) User adjusts the drawable graph values (say, to 78 and 143) and proceeds a step. Again, the drawable graph shows the updated Sales[1] and Sales[2], whereas the numeric steppers are updated to new Sales[2] and (original) Sales[3] as they should. So it seems that the drawable graph is updated before the model calculations are done (=> Adjusted sales updated) and stepper is updated afterwards? Hopefully you can make something out of my explanation :) Anssi |
|
|
Hi,
To me it all sounds like the same bug from yesterday. We will fix this on our Monday night release as well. Thanks for taking the time to describe it so well! Billy |
Please log in to reply to topics.