Deliver FESA3 equipment at GSI

In order to run your equipment, you first need to deliver it to the testing-directory.

NOTE: To have the writing rights to deploy a Deployment-Unit your Linux user account must be included in the fesa group.

1. Open the Deployent-Unit file (extension: .deploy)
2. Press the button "Deliver the Deploy Unit".
3. On success, the delivery directory path is displayed in the FESA Console View. Also the paths to the delivery directories of the instance file and the start script is displayed.

Deliver FESA3 equipment at the MCS

For the MCS (See Details in the FAIR.PlinacSource ), the delivery of the files has to be done manually ( at least as soon as the system is installed in sacley/france) DietrichBeck has provided a nice script, in order to simplify the necessary steps. Details can be found here.

Running a FESA binary on the asl-cluster

The asl-cluster (asl73x, where x is 0 ..4) primary should be used to develop FESA3 classes. Anyhow it is as well possible (and maybe useful) to run the binaries there. If intended, there are some restrictions one has to keep in mind:

• It is not possible to use RT-Priorities, instead NICE-scheduling is used. This could have a strong impact on your class behaviour!! (use application argument -noRTSched)
• Since normal users do not have root rights on the asl-cluster, possibly some operations of your class cannot be performed.
• It is not possible to connect any additional hardware to the asl-cluster! For such use-cases test FECs are available.

Follow these steps in order to run your FESA-binary:

1. Go to the folder where the binary is located:
2. # cd /common/usr/export/fesa/arch/[CPU]/eqp_software/[YourDeployUnitName]/[STATE]
3. Modify the entry for the FESA configuration file: in the asl-cluster the file fesa.aslCluster.cfg is the better choice compared to fesa.fec.cfg
4. Execute the startScript with the necessary parameters E.g:
5. # ./startScript.sh -noRTSched -vv &
6. Use the option -h for a full list of possible arguments

Running a FESA3 binary on a FEC

For testing several test-FEC's are available. You can take a look on a list of all available front-ends

1. Connect to your FEC ( Usually as root. Ask infrastructure-team for password )
2. # ssh root@myFEC
3. Go to the folder where the binary is located:
4. /opt/fesa/arch/eqp_software/[YourDeployUnitName]/[STATE]
5. Execute the startScript with the necesarry parameters E.g:
6. # ./startScript.sh &
7. Use the option -h for a full list of possible arguments

NOTES:

• Currently (02.07.2013) the LD_LIBRARY_PATH variable isn't set automatically, so you need to set it per hand. A simple way to do it is to write an own starting script, which sets the LD_LIBRARY_PATH to /opt/fesa/arch/lib on a FEC. Otherwise the class will missing some cmw specific libraries like libcurl.
• The instance file may be given explicitly using the -instance argument as:
  • ​-instance /opt/fesa/nfs/data/[SCU]/[STATE]/fesa-data/[INSTANCE_FILE]