Linking the settings file path to the alog

[prmango43]

I am requesting that when generating the roast log that the path for the aset file be captured as part of the log's data processing. By chance I found out that my Kaleido M2S may have and may still be generating spurious events. When I posted for assistance, I was asked to provide the associated aset file for the roast. But I could not meet analysis requirements as I had not been matching files.

[MAKOMO]

Thanks for your request. There is no settings file that can be referred to when you start a roast. The settings are a programming state persisted by your operating system. That state can be changed even during a roast. Thus even recording the last loaded artisan settings file is not enough to record that state.

[mrpenner]

Just thinking some more, I guess Artisan could make a timestamped backup of the settings each time they change. Then it would be possible to compare the date and time of the roast log and the settings backup to find which settings were in effect for that roast. Not sure if that would be a good solution or not.

[prmango43]

mrpenner:
The quest came as a result of Artisan request to provide associated aset and log files for a problem roast. I was not asking for the history of changes to the persisted settings.

[mrpenner]

Yes, I've been following the discussion. The issue is, there is not an an associated aset file for a roast unless you had the forethought to save one. The two solutions I have thought of is for Artisan to save an aset file for each roast, which seems a bit excessive for most users, or save an aset file each time settings are changed, which would allow finding the one that was in effect for a certain roast. I'm not sure if either option is actually desirable, I'm just brainstorming.

[prmango43]

I thought of several solutions, including yours and found all problematic. I like simplicity. In my request only a line with path would be added to the log. I may not have phrased my request clearly, but this has been closed. So I move on.
Thanks for the interest.

[MAKOMO]

Artisan settings are not stored in files. Only if a user "exports" them via the menu item Help the settings at that very moment are saved to a file. The app settings are to hold things like window positions and others as many other apps, to return to the state the user left the app on next start. The .alog profiles contain the actual roast data (like the text files a world processing app is saving). Artisan writes the file name of the last loaded settings file into those .alog files for pure debugging purposes.

App settings (handled by the operating system) and app data files (saved in .alog files) serve two very different purposes.