How To

Run AFECS platform

First of all make sure that you set following environmental variables:
EXPID, AFECS_HOME, COOL_HOME. Refer AFECS Installation & execution section for more details.
Execute $AFECS_HOME/bin/platform. This will start platform normative agents, pub-sub server and front end container. In case you don't want to run an AFECS container on that particular node run platform script with the -nofe option.If you need more verbosity run platform with the -debug option.


Run AFECS container

The software architecture of AFECS is based on coexistence of multiple containers, providing complete run time environment for AFECS agent execution and allows several agents to concurrently run on the same host. AFECS design choice limits to only one container per control node. To run the container execute $AFECS_HOME/bin/container. By default it will run with the -NOmulticast option. This means that container will connect to the platform through direct TCP using host name defined in the $COOL_HOME/setup.xml file. In the case you are not sure where the AFECS platform is running, then run $AFECS_HOME/bin/container with the -multicast option.

Start run control GUI

 Type $AFECS_HOME/bin/rcgui to start run control GUI. Synopsis of the rcgui is:
rcgui -<option> <value>
The list of rcgui options are shown in the table below.

 Option Description of the value
 -help  Prints synopsis with the description of the options
 -n  Unique name of the GUI (generated by default)
 -s  CODA run control session
 -e
  Experiment ID (EXPID defined as an environmental variable)
 -h  Host name of the AFECS platform
 -tp  TCP port number of the AFECS platform
 -up  UDP port number of the AFECS platform
 -f
  XML configuration file name
 -g  Enables debug flag

rcgui  option are non obligatory, and platform specific information (platform host name for example) from $COOL_HOME/setup.xml file will be used as default.
Attention: rcgui will not start if it will not be able to find an AFECS platform to connect to.

Connect GUI to a control system

  • Start rcgui (refer section How To > Start run control GUI for details).
  • Select CODA session
    • Sessions > session name
  • Select CODA configuration
    • Configurations > Cool > configuration name > OK
If configuration is active on the platform GUI will display the current state of the selected run control, including state, run number, information about participating components, charts, etc. In the case this is a new control, GUI will display the previously recorded run number for the selected session with the current state of the controls equal to connected.