I'm using experimenter to export simulation results in sqlite format, but the resulting file is quite heavy. I would like to know if there is a way to select which outputs to export via experimenter sqlite.
For example, exporting only data from statistics collector, instead of dashboards.
This is not currently supported - you'd need to customize the experimenter (preferably using a module) to do it at the moment. @Jordan Johnson will have more insight on this.
If you'd like to see this as a standard feature then I'd suggest it in the ideas section (it's a good idea).
I would like to understand your concern more. I understand that the results file can become large, and I understand that you are looking for ways to make it smaller. But I am interested to know why. Is something going slow when the file is large? Are you doing something with the files later (maybe emailing?) that makes a large file inconvenient? Any insight you can give would be appreciated.
Previously the results were exported via txt. Which allowed the choice of the desired output to be exported individually.
We've switched to the new version of experimenter 22 and we're having trouble sharing the results file. The sqlite file is getting quite heavy, even in small models, which makes it difficult to send it by email to the client, and it takes a long time to download the file from the cloud and import it into Power BI, for example.
We would like to export results only from statistics collector to make handling the sqlite file easier.
If you were using some method to export data to txt file before version 22, you should still be able to use a similar method in version 22. The change is that the data is stored in the database file, instead of in the tree. But all the same data is being recorded.
But maybe, since a sqlite file is a single file, it's better to try to share that file directly, instead of creating txt files yourself. One possibility is to delete the results you don't need. The attached model has a script that drops really big tables after running the experiment, and then uses VACUUM to shrink the file size. So first you run the experiment, then the script. The exact code may not work in future versions. But it should work for 22.0, 22.1, and (most likely) 22.2.
I will also add an issue to the dev list to possibly improve this.
19 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.
