Timing Runtime Environment
The Timing Runtime Environment contains binaries, libraries, dependencies and configuration files required by Etherbone and Saftlib.
Location
Resources are in /common/export/timing-rte/
FEC start scripts are in /common/export/nfsinit/global
Configuring a Frontend
Choose a Version (see below)
Navigate to the NFSINIT directory for the frontend /common/export/nfsinit/FECNAME
Link the start script, e.g.
ln -s ../global/timing-rte-R8-balloon_0 20_timing_rte
Adjust the prefix number to change the order of start scripts (timing_rte must be before fesa). The suffix name must be timing_rte.
Recommended Versions
FESA 4.0.0 Testing |
timing-rte-RC8-balloon_0 |
FESA 4.0.0 Production |
timing-rte-R8-balloon_0 |
SCUs with WR3 Firmware (Balloon)
FESA 4.2.0 Production |
timing-rte-R8-balloon_0 |
SCUs with WR4 Firmware (Snapshot240417)
FESA 4.2.0 Production |
timing-rte-tg-snapshot_noFD_040517 |
FESA DEV (using file-descriptor saftlib) |
timing-rte-tg-snapshot_240417_threadsafe ? |
https://www-acc.gsi.de/wiki/Timing/TimingSystemNodesCurrentRelease
Versions
Timing Environments are available in release, integration test, development and timing internal versions
Release Version
Official Stable Release for production. Post-release changes will be deployed with a separate patch number.
timing-rte-RN-NAME_M
N=CS/CO Release Number
NAME=Timing release name
M=Patch Number
e.g. timing-rte-R8-balloon_0
Integration Test Version (Release Candidate)
Stable pre-release for integration testing. Changes will be deployed with a separate patch number.
timing-rte-RCN-NAME_M
As above
e.g. timing-rte-RC8-balloon_0
Development Version
Latest stable release
timing-rte-proposed-master
Timing Development Version
For Timing Dept. testing
timing-rte-tg-dev
--
DominicDay - 05 Sep 2016