deletions | additions       diff --git a/sectionPROPOSED_SECO.tex b/sectionPROPOSED_SECO.tex  index 0be3c07..bf9575a 100644  --- a/sectionPROPOSED_SECO.tex  +++ b/sectionPROPOSED_SECO.tex 
...
{\em LNLS-UVX} beam size is monitored using the X-ray photon beam at the beam diagnostics dipole beamline but there is no on-line beam blow-up monitoring.   Typically, beam dimensions are $\sigma_{\hbox{y-normal}}= 80\,\mathrm{\mu m}$ height and $\sigma_{\hbox{x-normal}}= 380\,\mathrm{\mu m}$ at the diagnostics beamline.  Beamlines are notified whenever a variation larger than 10\% of the beam size in either plan takes place.   However, the event is these events are sporadic and  not considered for reliability purposes.This kind of problem is sporadic.  Usually the causes of the beam size variation are identified and if maintenance is necessary it is scheduled for the next injection period.   If the problem is frequent and has detrimental impact on the experiments it may lead to a `no-beam'' event.   The beam is dumped so that the cause of the problem can be fixed.  Beam blow-up problems are usually related to the IDs or to pressure variations in the front-end of beamlines under commissioning.   {\em PETRA III} has right now no continuous, reliable beam size measurement available.  
...
Orbit feedback outages are recorded if they are longer than 10 sec.  {\em LNLS-UVX} warns the beamlines whenever the orbit distortion exceeds 10\% of the beam size in any plane.  Orbit distortion measurement refers plane, measured relative  to agolden orbit defined by  BBA procedures.  Whenever an orbit distortion occurs the beamlines are warned and a defined golden orbit. A  fault event is then  registered in the operation log. Depending on the impact of the distortion on the experiments it These events are quite rare but  may lead to a ``no-beam'' event to correct the problem.This kind of event is rare and usually due to problems in the power supplies of the beam steering magnets of the orbit correcting system.  The limits are Vertical = 8$\,\mu m$ and Horizontal = 30$\,\mu m$. 
...
There is no bunch-filling control in the UVX injection system.   The Linac does not operate in single bunch so that the long Linac pulse leads to about 30 bunches being ejected from the booster to the storage ring.   As the timing system shifts the target buckets at every Linac pulse it is possible to get a smooth filling pattern.  The filling pattern is monitored by an oscilloscope and an image of the filling pattern a screenshot  is stored saved  in the logging system after injection. When operating in the single bunch mode bunch purity can be measured and improved using the bunch-by-bunch feedback system.  
...
{\em LNLS-UVX} operator records all beam-unrelated failures in the e-log system.   The database includesevents connected to  the front-ends but, except for those events that have some impact on machine operation, it does not include data from the beamlines.There is no communication between the UVX control system and the beamlines controls.  UVX is basically a dipole based light source, with just two wigglers and a single elliptical polarised undulator (EPU) EPU,  which is the only device controlled by the users.If a problem happens with the EPU only that beamline will be affected, but the operator is aware of the problem and register it in the database.  Problems with the wigglers usually lead to a ``no-beam'' event since they usually happen in the injection periods.   They IDs  are registered as faults in the database. datalog even when they do not lead to a ``no-beam'' event.  Events related to infrastructure usually affect all beamlines and if they cannot operate the fault leads to a ``no-beam'' event.   But none of these events are automatically entered in the database.