Play-Out Configuration

From WeizmannWiki
Revision as of 14:45, 27 November 2012 by Smadar (Talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

In this properties page, one can control the parameters that will effect the execution.

Play-out properties

Right-click the project you work on and choose Properties->PlayGo->Play-Out:

Playout.properties.jpg


As shown in the screenshot above, there are four tabs, in which you can configure properties related to S2A Builder:

Behaviors

  1. Source interactions on build path: Add and remove model files that you want to compile with S2A. For the models you add, you may choose which LSCs should be compiled by S2A. In other words, which LSCs will participate in the system execution.
    1. Note that if no model is added, at runtime PlayGo will look for a model file in the project's root directory and will use it. If more than 1 such model file is found, PlayGo will NOT use any of them. Instead, when starting a play-out session, it will open the properties sheet and let the user chose the model file(s) to execute.
    2. One can choose to work with multiple model files, for example: each model file serves a different use case. This is done simply by adding all the files that participates in the run to the 'Source interactions on build path'. More about working with multiple model files
  2. Clear Automatically: If on, cleans the aspects directory before generating aspects.
  3. Polymorphism: Enable or disable polymorphism.
  4. Target Folder: Here you specify the directory in which the generated aspects will be located.
  5. Use System Model GUI: if selected, a default GUI will be generated and executed. The user can play the scenario from this GUI. Otherwise the user can provide his own GUI or play-out from the system model.

Imports

  1. Add and remove Java packages that will be imported in the generated aspects.
  2. Output package name: The package of the generated aspects.

Tracing

  1. Generate trace: Check if you want to generate a trace/log at runtime.
  2. Append: Check if you want to append the log to the existing log (rather then deleting and adding new content).
  3. Output file: The path and name of the generated trace file. By default, the trace file is generated in the root directory of your project.
  4. LSCs to trace: Check those LSCs you would like to trace. Check or uncheck the model root to apply your selection on all LSCs.

Strategy

Here you can choose a play-out strategy from a set of predefined strategies.

General

  1. Log4J configuration file: : use for specifying the log4j configuration location.
  2. Debug: use for specifying the port for debugging sessions
  3. Enable Trace Vis: Check if you want to generate a trace in the format that can be viewed via the TraveVis.

References