The Application Description (AD)

The Application Description (AD) describes the general characteristics of one application. There is one AD per application, i.e. per code which when compiled forms one executable. An application may contain one or more component model. This description XML file should be created by the application developer, either by hand or with the graphical user interface wizard.tcl available in oasis4/util/gui, to provide information about the application general characteristics but it is not used by the OASIS4 coupler.

The AD Schema is given in oasis4/util/xmlfiles/ad.xsd. The AD file name must be
$<$application_local_name$>$_ad.xml where $<$application_local_name$>$ is the application name.

The AD contains the element `application' which is composed of (see the ad.xsd):

• the application name: attribute `local_name', which should match argument appl_name of PSMILe call prism_init (see section 5.1.1);

• a description of the application: attribute `long_name';

• the mode into which the application may be started: attribute `start_mode': `spawn', `notspawn' or `notspawn_or_spawn' (see section 4.1);

• the mode into which the application may run: attribute `coupling_mode': `coupled', `standalone', or `coupled_or_standalone';

• the arguments with which the application may be launched: element `argument';

• the total number of processes the application can run on: element `nbr_procs';

• the platforms on which the application has run: element `platform';

• the list of components included in the application: element `component'; for each component:
  • the component name: attribute `local_name', which should match the argument comp_name of PSMILe call prism_init_comp (see section 5.1.2);

  • a description of the component: attribute `long_name';

  • whether or not this component is always active in the application: attribute `default', either true or false);

  • the number of processes on which the component can run (element `nbr_procs').