CRV-2015 Monitor Phase (March 30, 2015 -> June 10, 2015)

In this phase, competitors provide monitors for benchmarks. Participants decide to compete on a benchmark described by a pair (team_id, benchmark_number) where the team_id is the id of the team who has provided the benchmark and benchmark_number is the number of the benchmark provided by the team.

The following description is purposed to indicate the headlines and give a general idea to participants as of what will be requested at the time of submission. A more detailed description of monitor submission shall be posted on the Wiki of the competition.

In this phase, a contribution takes one of the two forms below depending on whether a program or a trace is monitored. Contributions should be submitted before the deadline, June 10, 2015.

Contribution for the Java and C Tracks:

• The monitor given by two scripts to build and run the monitored program.
• The property from which the monitor has been synthesized, where the property is described by:
  • a formal definition of the property in a well-defined specification language;
  • reference to the specification language;
  • informal explanation of the property.
• The source code for instrumentation (e.g., AspectJ file for the Java track).
• The source code of the monitoring code.

That is, a contribution is related to a program and contains a monitor for the property of this program. A monitor consists of two scripts, one for building the monitored version of the program, one for running it. The actions performed by the script should be documented. The description of the property should contain a formal definition of the property in the specification language chosen by the participants. References to the specification language should be given. An informal description of the property should be provided to help understanding the formalization. If the property that was used to synthesize the monitor has been expressed in a different specification language than the one used to define the benchmark, explanations should be given as of why the submitted specification indeed corresponds to the one in the benchmark. A contribution also contains the source of the code for monitoring.

Contribution for the Offline Track:

• The monitor given by two scripts to build and run the monitor over the trace.
• The property from which the monitor has been synthesized, where the property is described by:
  • a formal definition of the property in a well-defined specification language;
  • reference to the specification language;
  • informal explanation of the property.
• The code that is used to build concrete events out of the log entries.

The above elements should follow the same constraints as in the Java and C tracks.