What user can/cannot do using Simulator

[prmango43]

I've not been able to find clear documentation and example(s) on using the simulator tool. What I've gleamed is this is maybe an on-the-fly method to make changes to a roast profile. Assumption is new saved profile will contain the changes, but will not do anything to the simulator roast curve which is fixed by the profile(log) data/events/alarms. My experience so far is that even though I make a change(s) using buttons/sliders, future roast data event(s) can/will wipe out my change(s) so I need to be continually editing. Example: latter part of roast I change burner from 40 to 30, but subsequently a burner entry in original roast data will change/revert my change. Am able to delete and make changes to the roast properties/events and even save the log, but the roast properties/data table is secure and overrides changes made to the roast properties/events entries.
So perhaps someone that has made the leap through simulator can address my request. I'd like a basic explanation of the simulator tool, an example or two, and maybe a cheat-sheet.

[beanoccio]

Did you study this?
https://artisan-scope.org/docs/simulator/

[prmango43]

Perhaps I'm have the same issue with Artisan's concept of simulation as I had with reset. To me a simulator is testing the "vehicle" (for ease of discussion) without any constraints except for whatever background data there might be on which the simulation is being run -- the sea, land, air etc. It has been some time since I played with a simulator so bare with me. For example, simulating a jet bomber I can make several runs starting from same location, running say 3 different flight plans and achieve the goal -- eliminate target and return safely.

So the vehicle (roaster) will be running a simulation but it needs background, which in this case is a saved profile. Let's say I load a profile that has a minimal set of alarms and events, and a data set. I am able to make changes to the alarms and events but not the data set. I make changes and run the simulator. But I see no corresponding changes in the curve to those made to the alarms/events. The BT curve stays the same no matter what changes I've made to the alarms/events. Not what I expected from my understanding of a simulation. Am I explaining myself clearly?? Am I missing something -- or done something incorrectly??

[MAKOMO]

The simulator is not simulating your roasting machine. It is taking the data of the profile loaded the moment you start the simulator and feeds that into Artisan as it would come from a machine. All communication is disabled while the simulator is active.

This feature allows to test Artisan features without having it being connected to a physical machine providing data. You can test for example your alarm rules and if they fire where you expect them to do so. However, as the data used for the simulation is static it will not change if you move the burner slider up and down.

Realizing a simulator for a roasting machines thermodynamic would be another 10 years project and then would most likely not simulate YOUR machine. The project is open for contributions. Just provide your code as GitHub Pull Requests!

[prmango43]

Thanks to all. So I load a previous roast I like but needs tweaking. I make changes to alarms/events as needed, run the simulation, save results and compare those to the targets I was trying to achieve.

[MAKOMO]

No. The simulated roast curves will be identically to that previous roast you started the simulator with as it is exactly this data that is replayed. However, you can see when alarms are triggered, you can play with various Artisan settings during the roast to see what they do without wasting green beans. Often the simulator is used by tutors who teach roasting.

[prmango43]

Understood. thanks