this is for holding javascript data
Ruy H. A. Farias edited sectionPROPOSED_PRIM.tex
almost 9 years ago
Commit id: 58ee755fae4c19ea25390a7d8eda46a62f97f68b
deletions | additions
diff --git a/sectionPROPOSED_PRIM.tex b/sectionPROPOSED_PRIM.tex
index 8f2c298..95f9a18 100644
--- a/sectionPROPOSED_PRIM.tex
+++ b/sectionPROPOSED_PRIM.tex
...
{\em LNLS-UVX} combines ``beam trip'' and ``delayed beam delivery'' into ``no-beam'' events.
Such events occur when the beam current falls below the ``no beam'' threshold (60$\,$mA for the UVX multibunch
operation), operation)
or when the beamline shutters are closed by a machine interlock flag during user time.
The
scheduled injection period is
30 minutes; beyond that a ``no beam'' period
which starts and lasts until the interlock flags
that prevent the beamline shutters from opening are cleared.
Early delivery is not considered for reliability purposes but is considered for
yearly beam availability, which is calculated based on the recorded events in the
database. datalog.
``Low-beam-current" events It may happen
after electrical power glitches or power supply faults.
Usually that by some reason the current is
completely partially lost
but a ``low-beam-current" situation may also happen,
for instance when a sextupole or a steering magnet power supply trips.
In these events the current and although it is still above the ``no-beam'' threshold
but it is low compared to the expected
current. for that time.
When this kind of event occurs the users are consulted about
re-injections
and re-injection. If a new injection takes place the problem is
then accounted for as a ``no-beam'' event.
Otherwise just a "Fault" event is recorded.
{\em PETRA III} starts ``no-beam'' events (or ``downtime'') when the beam current
...
For those facilities where the limits are similar, the failure rates will allow a
meaningful comparison of the reliability of the injection process.