iCFTL-Diagnostics dataset

This dataset accompanies the paper "Diagnosing Violations of Time-based Properties Captured in iCFTL", by Cristina Stratan, Joshua Heneage Dawes, and Domenico Bianculli, to appear in the proceedings of FormaliSE 2024. Together with the dataset, we provide the source code (iCFTL-Diagnostics-tool.zip) of the tool developed as part of the contribution of this paper. iCFTL-Diagnostics tool is also available at https://github.com/SNTSVV/icftl-diagnostics. The instructions on usage can be found in the README both in the zip file and GitHub).The dataset.zip has three folders:rq1 for research question RQ1rq2 for research question RQ2rq3 for research question RQ3In folder rq1 we have rq1.csv file that contains the data used to answer RQ1 and it has the following columns:project - for the project full nameexpected PNR, for the line number expected to be returned by the diagnostics approachdetected PNR, for the line number of the PNR detected by our diagnostics approachcorrect PNR, Boolean values to show if expected PNR coincides with detected PNRIn folder rq2 we have time-men-diagn.csv and time-men-diagn2.csv files that contain the data used to build Table 2: Average (over 5 runs) time and memory consumed by the diagnostics approach. Both time-men-diagn.csv and time-men-diagn2.csv have the columns:project - for the project full nametime-mean - for the mean time calculated over the 5 runs of the projecttime_std - for the standard deviation of the time takenmemory-mean - for the mean memory calculated over the 5 runs of the projectmemory_std - for the standard deviation of the memory consumedID - for the project IDbinding-count - for the number of binding the project hasavg-trace-length - for the average trace lengthFinally, in rq3 we have the rq3.csv file that contain data used to build Table 3: Mean of time and memory consumed by different instrumentation schemes. rq3.csv has the columns:project - for the project namemean-n-t - for mean time calculated over 5 runs of the non-instrumented programstd-n-t - standard deviation of the time taken over 5 runs of the non-instrumented programmean-v-t - for mean time calculated over 5 runs of the vanilla instrumented programstd-v-t - standard deviation of the time taken over 5 runs of the vanilla instrumented programmean-d-t - for mean time calculated over 5 runs of diagnostics instrumented programstd-d-t - standard deviation of the time taken over 5 runs of the diagnostics instrumented programID-t - for the project IDmean-n-m - for mean memory calculated over 5 runs of non-instrumented programstd-n-m - standard deviation of the memory consumed over 5 runs of the non-instrumented programmean-v-m - for mean memory calculated over 5 runs of vanilla instrumented programstd-v-m - standard deviation of the memory consumed over 5 runs of the vanilla instrumented programmean-d-m - for mean memory calculated over 5 runs of diagnostics instrumented programstd-d-m - standard deviation of the memory consumed over 5 runs of the diagnostics instrumented programID-m - for the project IDt-d-v - for approximate percentage of time taken by the diagnostics instrumented program over vanilla instrumented program (in percentage)m-d-v - for approximate percentage of memory consumed by the diagnostics instrumented program over vanilla instrumented program (in percentage)t-d-n-raw - for the time the diagnostics instrumented program took over non-instrumented program (in percentage)t-d-v-raw - for the time the diagnostics instrumented program took over vanilla instrumented program (in percentage)m-d-n-raw - for memory the diagnostics instrumented program took over non-instrumented program (in percentage)m-d-v-raw - for memory the diagnostics instrumented program took over vanilla instrumented program (in percentage)