lgwagner / SpeAR

Specification and Analysis for Requirements Tool
Other
20 stars 4 forks source link

Autosave Analysis results #72

Open lgwagner opened 7 years ago

lgwagner commented 7 years ago

Develop and emit a textual file that captures analysis results.

jendavis commented 6 years ago

I'm adding some detail on what I'd like to see for this feature. This is similar to my recent feature request for AGREE: https://github.com/smaccm/smaccm/issues/134.

A feature that auto-saves analysis results would help save time of taking screenshots and opening and saving counterexamples. It would help prevent user error and would be very beneficial in the event that some sort of system interrupt (forced computer restart, etc.) happens after analysis completes but before results are manually saved. Ideally, such a feature would do the following:

1) Emit results to a predictable, intuitive location. I suggest my_SpeAR_project_folder/results or perhaps folder_containing_SpeAR_file_being_run/[SpeAR_filename]_results 2) Emit a summary table of results and any counterexamples found by the model checker to separate files. The summary table should include the information shown in the Results tab today (name of property, result, and analysis time). The form of the summary table could be *.csv or Excel. The counterexamples could simply be the Excel files emitted when the user opens the counterexample from the GUI. Observers should be saved off as Excel files as well. 3) Emit a short text file with the user's analysis settings for the run. 4) Append a timestamp from when the run was started to the auto-generated filenames. This should prevent accidentally overwriting previous results.

Auto-saving results could be an optional feature that the user selects from the Preferences menu.