The OVA File is a 64-bit Ubuntu. USERNAME : artefact PASSWORD : artefact Once logged in to the VM, the desktop contains the folder 'SDTMC_Encoder' which contains all the scripts and other related files. To build and verify the PRISM models generated by our code, PRISM model checker is already installed on the machine. PRISM is located at /Home/prism/prism/bin where prism is the command line tool and xprism is the GUI based tool. We STRONGLY advise you to use the MRF generator to generate the machine-readable PRISM files and compile them to build and model-check as discussed in the paper as well as it is a quicker means. Since our original experiments were run on a 2.2GHz `Intel(R) Xeon(R) CPU E5-2650 v4' processor with 64GB System Memory running Ubuntu 20.04-LTS and PRISM 4.6, the running times in the reports are still of the same machine. Due to time constraints, we only checked a few experiments on the new VM and the times were a bit more when compared to smaller models which has PRISM 4.7. The report and the paper still provide the values for the experiments run on the workstation. All the mcrl2 specifications, generated lps and lts files are provided in the dedicated sub-directories, hence, the mCRL2 tool set is not installed on the VM. If one wishes to write and check for new specifications, he/she first needs to install mCRL2 on the VM. Other details of the VM: Base Memory: 4097 MB Processors: 2 Video Memory 16 MB Reproducibility Instructions: We assume that the python code and the lts files are in the same directory in the commands given below. In case it is not, modify the terminal line entry accordingly or make the same arrangements as assumed if you are unaware of the modifications. The Repository contains the following files: 1. LTS-to-MRF-PRISM-generator.py : A python code which takes in as input an ADTMC file generated from an mCRL2 code of an ADTMC via the sequence mCRL2LPS on the .mcrl2 file followed by the lps2lts on the generated lps in the previous stage with the output option chosen as .aut extension. The resultant file is input to this code. All the mCRL2 models are adapted from the given examples of probabilistic systems of the mCRL2 toolset. The subfolder mCRL2_Code_ADTMCs in this directory contains the mcrl2 code, generated lps and lts as mentioned before. The code file should be run as: (in case .aut generated via lts with .lts (Possible in mCRL2 GUI) python3 LTS-to-MRF-PRISM-generator.py python LTS-to-MRF-PRISM-generator.py ------------------OR--------------------------------- python3 LTS-to-MRF-PRISM-generator.py [These are aut files saved with .lts extensions. Code not compatible with any other type of lts file.] python LTS-to-MRF-PRISM-generator.py   [These are aut files saved with .lts extensions. Code not compatible with any other type of lts file.]           This will output three files: (a) ats.sta           (b) ats.tra        (c) ats.lab These files can be directly used to build the corresponding SDTMC in PRISM in the command line and model-checked for the formulas: ./prism -importtrans ats.tra -importstates ats.sta -importlabels ats.lab -dtmc .pctl The embedded formulas for each problem can be found in the subdirectory PRISM inside each problem subfolder. 2. LTS-to-PRISM-CODE-generator.py : A python code which takes in as input an ADTMC file generated from an mCRL2 code of an ADTMC via the sequence mCRL2LPS on the .mcrl2 file followed by the lps2lts on the generated lps in the previous stage with the output option chosen as .aut extension. The resultant file is input to this code. All the mCRL2 models are adapted from the given examples of probabilistic systems of the mCRL2 toolset. The subfolder mCRL2 in this directory contains the mcrl2 code, generated lps and lts as mentioned before. You can manually edit the code to tweak it to print the state mappings in case you require them. The code file should be run as: python3 LTS-to-PRISM-CODE-generator.py python2 LTS-to-PRISM-CODE-generator.py ------------------OR--------------------------------- python3 LTS-to-MRF-PRISM-generator.py [These are aut files saved with .lts extensions. Code not compatible for any other lts file.] python LTS-to-MRF-PRISM-generator.py   [These are aut files saved with .lts extensions. Code not compatible for any other lts file.]           This will output a single file: ats.prism           This file can be opened in the PRISM GUI or through the command line and built as follows:             ./prism ats.prism .pctl The embedded formulas for each problem can be found in the subdirectory Generated_PRISM_Models_with_Embedded_properties inside each problem subfolder. TROUBLESHOOTING PRISM ISSUES: In case you face parsing issues, one possible fix is: prism ats.prism .pctl -javastack In cases that the probabilities do NOT converge, you can increase the maximum iterations for it to converge by suffixing the query with '-maxiter 100000' where 100000 can be replaced with any number. This number is 10000 in default for PRISM. TROUBLESHOOTING PYTHON CODE: In case the lts file is not in the same directory as your code, you can use the ~ to locate your lts file. But remember that the output files will be in the directory where your python script is located. For e.g., python3 LTS-to-MRF-PRISM-generator.py ~/Desktop/SDTMC_Encoder/mCRL2_Files/LTSs will work and output the files as well. This might only solve the problem to a certain aspect. For big models, we suggest you build through the process mentioned in (1). This is for small models. 3. LTS-to-PRISM-CODE-REWARDS-generator.py : Similar to (2). Generates PRISM files with rewards defined. This is an initial version. Output generated as . DOWNLOAD THE PYTHON SCRIPTS ON YOUR LOCAL MACHINE AS WELL WORKS. THIS GIVES YOU MORE MEMORY AND SPACE AND THE RESULTS WILL BE QUICKER. IF YOU FACE ANY ISSUES, PLEASE WRITE TO US. All the problems discussed in the paper are generated using the above codes and are saved in the folder                       'Generated_PRISM_Models_with_Embedded_properties', under which, for each problem as a separate subdirectory, all the four PRISM files (3 MRFs and 1 code along with the properties files are shared).