Hello,
I have set up the import of my data "on model reset", but then I also have code in "on set" parameter, which involves changes in this data (f.e : the order of production).
If the import involves the load of an excel sheet, how the "on set" reacts. Which acts first? is the "on set" change data properly after excel data is imported or is there a clash?
Thanks
I just did a simple test with the print() command and it appears the OnSet triggers of the parameters executes before the model reset trigger, in the order that the parameters appear in the table. Not sure how you would go about making the data import happen first, maybe by writing your import code in the first parameter in the paameter table's OnSet trigger instead of model reset?
Not what I expected... and so confusing right now
Hi @Marc R5,
We haven't heard back from you. Were you able to solve your problem? If so, please add and accept an answer to let others know the solution. Or please respond to the previous comment so that we can continue to help you.
If we don't hear back in the next 3 business days, we'll assume you were able to solve your problem and we'll close this case in our tracker. You can always comment back at any time to reopen your question, or you can contact your local FlexSim distributor for phone or email help.
Here it is the model. You can see that there is code "on model reset" and on order parameter "on set".
I need both, and the on set code needs to "play" with the data of a global table that is created/updated using the on model reset code.
When you click the reset button, the very first thing that happens is the parameter OnSet triggers are fired. The "isReset" parameter is true (1) in this case. The model's OnReset trigger fires after this.
The OnSet trigger is also fired when you change the value of the parameter. In this case, the "isReset" flag is false (0).
In general, we advise against always importing data on reset. First, it usually isn't necessary. If the data hasn't changed since the last reset, then there's no reason to import it again. Consider running replications in the Experimenter or Optimizer; all of the replications will call the On Reset trigger, and they don't need to re-import the data.
Second, if you always import excel data on reset, then you'll be unable to use the Experimenter or Optimizer with more than one CPU. The current Excel import doesn't allow multiple processes to access a given sheet at exactly the same time, so the import will work for some replications, but not for others.
It is much better to add a custom button to your dashboard that says "import data", or something like that. You can then click that button when you want to refresh the data, and then reset the model. This avoids the timing issue you are seeing. If you plan to use this model operationally, you could add your import code to the On Model Open trigger as well. This would also avoid the conflict you have.
I don't import every time I reset the model. I have a parameter to enable the import and when the input changes I change it to update the data. But when this is the case, I need to do all the other stuff after the import, the same when not importing.
That's why I needed to understand this, and I still don't know which would be the solution so far.
Thanks
I suggest you request a trigger for OnScenarioChange to be added to the experimenter to allow you to load new data when parameters change. It should fire before applying the parameter table.
15 People are following this question.
FlexSim can help you understand and improve any system or process. Transform your existing data into accurate predictions.
FlexSim is a fully 3D simulation software environment. FlexSim can be used to simulate any process in any industry.
FlexSim®, FlexSim Healthcare™, Problem Solved.®, the FlexSim logo, the FlexSim X-mark, and the FlexSim Healthcare logo with stylized Caduceus mark are trademarks of FlexSim Software Products, Inc. All rights reserved.
