Skip to content
Alessio Cecconi edited this page Apr 1, 2021 · 5 revisions

Measurememnt Framework for Declarative Specificaions

This is the expected command to launch the Janus measurements:

`java -cp Janus.jar $JANUS_MAINCLASS -iLF ${INPUT_LOG} -iME json -iMF ${INPUT_MODEL} -JSON ${OUTPUT_FILE}`

where:

  • JANUS_MAINCLASS is "minerful.JanusMeasurementsStarter"
  • INPUT_LOG the path to the input log file. If the file is a TXT text file add the following option "-iLE strings"
  • INPUT_MODEL the path to the JSON file containing the model to check
  • OUTPUT_FILE the path where to save the results as a JSON file

Optional Parameters

-encodeTasksFlag,--flag-encoding-tasks Flag if the output tasks/events should be encoded

-nanLogSkip,--nan-log-skip Flag to skip or not NaN values when computing log measures

-nanTraceSubstitute,--nan-trace-substitute Flag to substitute or not the NaN values when computing trace measures

-nanTraceValue,--nan-trace-value <number> Value to be substituted to NaN values in trace measures

EXPLANATION OF MODEL CHECKING OUTPUT

  • Janus uses constraints defined in a reactive form "Activator []-> Target", where both Activator and Target are arbitrary LTLpf formulas. Only a subset of DECLARE constraints is used for now.
  • For readability, regardless of the input log, the output events are encoded in characters like "A", "B", "C",...
  • The result is a 3D matrix of bytes to be read as follows: for each trace -> for each constraint -> for each event of the trace -> byte result = [activator evaluation of (event;constraint;trace)][target evaluation of (event;constraint;trace)]
  • Each byte stores the results of both Activator and target evaluation of a given constraint in a specific trace for a specific event. The left bit is for the activator, the right bit for the target,i.e.,[activator-bit][target-bit] In details:
    • 0 -> 00 -> Activator: False, Target: False
    • 1 -> 01 -> Activator: False, Target: true
    • 2 -> 10 -> Activator: True, Target: False
    • 3 -> 11 -> Activator: True, Target: True
  • Based on the single events evaluation, it is reported a set of measures for the each trace and constraint (Support, Confidence, Lovinger's measure, ...)

e.g.

{
	"TRACE-1":[
		{
            "DECLARE-CONSTRAINT-A(VARIABLE1, VAR2, ...)": [ {"EVENT-1": BYTE},{"EVENT-2": BYTE},... ]
            "Support": S.S
            "Confidence": C.C
            "Lovinger": L.L
            "...": ...
		},
		{
		    "DECLARE-CONSTRAINT-B(...)": [ ... ]
            "Support": ...
            "Confidence": ...
            "Lovinger": ...,
        },
        {...}
	],
	
	"TRACE-2":[
		{
            "DECLARE-CONSTRAINT-A(...)": [ ... ]
            "Support": ...
            "Confidence": ...
            "Lovinger": ...
		},
		{...}
	],
	...
}

Notes:

  • The measurement framework main class is named "ModelCheck" for historical reason, but it will be refactored in the future.

Clone this wiki locally