From: hadaq@CountingHouse Date: Tue, 14 May 2013 15:26:03 +0000 (+0200) Subject: added documentation files X-Git-Tag: pre2018~139 X-Git-Url: https://jspc29.x-matter.uni-frankfurt.de/git/?a=commitdiff_plain;h=e47b7570849d9babbd265ad716cb474f8df91ee3;p=hadesdaq.git added documentation files --- diff --git a/hmon/doc/background.png b/hmon/doc/background.png new file mode 100755 index 0000000..d17851d Binary files /dev/null and b/hmon/doc/background.png differ diff --git a/hmon/doc/daq-busy.htt b/hmon/doc/daq-busy.htt new file mode 100644 index 0000000..9001235 --- /dev/null +++ b/hmon/doc/daq-busy.htt @@ -0,0 +1,20 @@ +

Number of busy boards

+

+This button gives you the number of busy front-end boards, that have stopped working and are blocking the trigger. +During normal operation, the full message gives the busy times for all sub-systems. + +

Error Handling if the button is not Green

+ + +
Note that in some cases this is not the real source of the error - e.g. if the data transport to EB failed, the board with the smallest buffer and the most data gets busy first. + + + + + + diff --git a/hmon/doc/daq-timeouts.htt b/hmon/doc/daq-timeouts.htt new file mode 100644 index 0000000..59f6b06 --- /dev/null +++ b/hmon/doc/daq-timeouts.htt @@ -0,0 +1,9 @@ +

DAQ Timeouts

+

+This button gives information about not responding front-ends. +

+

Error Handling if the button is not Green

+ diff --git a/hmon/doc/daq-trbnet.htt b/hmon/doc/daq-trbnet.htt new file mode 100644 index 0000000..5748530 --- /dev/null +++ b/hmon/doc/daq-trbnet.htt @@ -0,0 +1,16 @@ + +

TrbNet Basic Status

+The basic status of the DAQ network is checked by a simple access to one network hub to see, if a board in the network has failed +to answer, or the network is completely out of order. + + +

Error Handling

+This error typically pops up in combination with many other boxes showing errors. Follow the normal DAQ restart guidelines. + +
Error: RPC connection failed
Restart the interface to the DAQ network, i.e. trbnetd. Then restart DAQ +(Note that "RPC" refers to "Remote Procedure Call", not our detector!) +
Error: Timeout
The network failed to answer within the given amount of time. Try to restart the DAQ. +
Warning: One endpoint didn't react
Restart DAQ +
Other Errors
A DAQ restart should cure it. +
OK
Don't touch a running system. +
\ No newline at end of file diff --git a/hmon/doc/eb-bytes.htt b/hmon/doc/eb-bytes.htt new file mode 100644 index 0000000..9d6c65b --- /dev/null +++ b/hmon/doc/eb-bytes.htt @@ -0,0 +1,24 @@ +

Data Rate

+

+The data rate gives the amount of data per second transfered by all Eventbuilders.

+Also displayed are:
+the amount of data transfered per event and
+the number of +events per second per Eventbuilder. +

+ +

Error Handling if the button is not Green

+ +The number of MDC calibration events and status events are too low. Check at the CTS Monitor if they are switched on. +Check the long error message to see if the number of MDC calibration and status triggers increases by 1 per second - if so, everything is ok and the error can be ignored. +
+If not: Switch them on. +
+In case nothing helps: DAQ restart (For restart instructions, see restart-DAQ guidelines) + + + + + + + diff --git a/hmon/doc/eb-errbits.htt b/hmon/doc/eb-errbits.htt new file mode 100644 index 0000000..32304ad --- /dev/null +++ b/hmon/doc/eb-errbits.htt @@ -0,0 +1,11 @@ +

Error bits

+

+This buttons shows the number of accepted events (written to disk) with errors reported by the front-ends. +
Try to do a DAQ restart +
In some cases a power-cycle of the corresponding system / chamber is necessary. + + + + + + diff --git a/hmon/doc/eb-lostevt.htt b/hmon/doc/eb-lostevt.htt new file mode 100644 index 0000000..e58e8c4 --- /dev/null +++ b/hmon/doc/eb-lostevt.htt @@ -0,0 +1,5 @@ +

Number of discarded events

+

+This button gives you the number of discarded events in the Eventbuilders. +
The reason can be a overloaded CPU in the EB or any other error. Try to restart the Eventbuilders. + diff --git a/hmon/doc/eb-rate.htt b/hmon/doc/eb-rate.htt new file mode 100644 index 0000000..d4e319c --- /dev/null +++ b/hmon/doc/eb-rate.htt @@ -0,0 +1,27 @@ +

Comparison of CTS Rate and Eventbuilder Rate

+

+This number gives the difference between the Eventbuilder and the CTS Rate. This difference should be around zero. +As long as the button is green everything is O.K. - even if the box shows some large deviations for a short time. +

+

Error Handling if the button is not Green for more than 10 seconds:

+ +
+
In case of a negative deviation
+
the Eventbuilder rate is below the + CTS rate, first check the + #EB running + and + #Evt Discarded + buttons as + well. Usually they should give further information on what the + problem is.
+
In case of a positive deviation
+
the Eventbuilder rate is above the + CTS rate, there must be a seldom but serious error. Both the state of + all Eventbuilders and the CTS must be investigated in detail.
+
+ + + + + diff --git a/hmon/doc/eb-run.htt b/hmon/doc/eb-run.htt new file mode 100644 index 0000000..f24c473 --- /dev/null +++ b/hmon/doc/eb-run.htt @@ -0,0 +1,13 @@ +

Number of running Eventbuilders

+

+The right number gives the number of Eventbuilders where the DAQ sends data to (stays always the same).
+The left number gives the number of Eventbuilders writing data to disc.
+This number should be equal and in this case the button would be green. (Cosmics: 1 EB, Beamtime: 8 EB) + +

+

Error Handling if the button is not Green

+
+
Restart Eventbuilders
+
See restart-instructions for +Eventbuilders
+
diff --git a/hmon/doc/endp-mdc.htt b/hmon/doc/endp-mdc.htt new file mode 100644 index 0000000..faed10a --- /dev/null +++ b/hmon/doc/endp-mdc.htt @@ -0,0 +1,13 @@ +

MDC Endpoints

+ +This button shows if all MDC front-end modules are active. The button is red if at least one module is missing.
+ + +

Error Handling

+ +
+ diff --git a/hmon/doc/endp-other.htt b/hmon/doc/endp-other.htt new file mode 100644 index 0000000..f0e6114 --- /dev/null +++ b/hmon/doc/endp-other.htt @@ -0,0 +1,8 @@ +

Other Endpoints

+ +This button shows if all front-end modules of Shower, Forward Wall, Start-/Veto-detector and CTS are active. +The button is red if at least one module is missing. + +

Error Handling

+

Restart DAQ. If this doesn't help, do a power-cycle of the corresponding system. + diff --git a/hmon/doc/endp-rich.htt b/hmon/doc/endp-rich.htt new file mode 100644 index 0000000..a565bdb --- /dev/null +++ b/hmon/doc/endp-rich.htt @@ -0,0 +1,8 @@ +

RICH Endpoints

+ + +This button shows if all RICH front-end modules are active. The button is red if at least one module is missing. + +

Error Handling

+

Restart DAQ. If this doesn't help, do a power-cycle of the corresponding system. + diff --git a/hmon/doc/endp-rpc.htt b/hmon/doc/endp-rpc.htt new file mode 100644 index 0000000..4cd4cd7 --- /dev/null +++ b/hmon/doc/endp-rpc.htt @@ -0,0 +1,7 @@ +

RPC Endpoints

+ +This button shows if all RPC front-end modules are active. The button is red if at least one module is missing. + +

Error Handling

+

Restart DAQ. If this doesn't help, do a power-cycle of the corresponding system. + diff --git a/hmon/doc/endp-tof.htt b/hmon/doc/endp-tof.htt new file mode 100644 index 0000000..ec5577c --- /dev/null +++ b/hmon/doc/endp-tof.htt @@ -0,0 +1,9 @@ +

TOF Endpoints

+ + +This button shows if all TOF front-end modules are active. The button is red if at least one module is missing. + +

Error Handling

+

Restart DAQ. If this doesn't help, do a power-cycle of the corresponding system. + + diff --git a/hmon/doc/feeerr-feebuffer.htt b/hmon/doc/feeerr-feebuffer.htt new file mode 100644 index 0000000..6e7c45b --- /dev/null +++ b/hmon/doc/feeerr-feebuffer.htt @@ -0,0 +1 @@ +

FEE Buffer

diff --git a/hmon/doc/feeerr-feeerr.htt b/hmon/doc/feeerr-feeerr.htt new file mode 100644 index 0000000..76dd933 --- /dev/null +++ b/hmon/doc/feeerr-feeerr.htt @@ -0,0 +1,16 @@ +

Front-End Electronic Errors

+

+This button shows the number of boards that have not been initialised in the last few seconds. +This might appear from time to time because a front-end had an error bus recovered automatically. + +

Error Handling in case it is not Green for more than 30 seconds.

+ + + + + diff --git a/hmon/doc/feeerr-rich.htt b/hmon/doc/feeerr-rich.htt new file mode 100644 index 0000000..7e75a22 --- /dev/null +++ b/hmon/doc/feeerr-rich.htt @@ -0,0 +1,14 @@ +

+RICH APV Satus Report, it tells the status of all RICH APV Frontends. As +long as the button is green everything is O.K. +

+

Error Handling in case it is not Green

+In most cases a DAQ restart helps. In rare cases a power-cycle has to be performed. + +

Check the short Error Messgage Indicator dislayed on the button

+ + diff --git a/hmon/doc/feeerr-trb.htt b/hmon/doc/feeerr-trb.htt new file mode 100644 index 0000000..382f01a --- /dev/null +++ b/hmon/doc/feeerr-trb.htt @@ -0,0 +1,15 @@ +

TRB TDC

+

+This button shows if the TDC on the TRB are synchronized to the DAQ system. +

+

Error Handling in case it is not Green

+ +If they are not synchronized there is the danger of mixing different events.
+You should restart DAQ several times.
+ + + + + + + diff --git a/hmon/doc/feeerr-trginp.htt b/hmon/doc/feeerr-trginp.htt new file mode 100644 index 0000000..21c5679 --- /dev/null +++ b/hmon/doc/feeerr-trginp.htt @@ -0,0 +1,11 @@ +

Trigger Inputs

+

+This button shows the trigger input errors. This could indicate a problem with a trigger / reference time / common stop signal. +

+

Error Handling

+Restarting DAQ should help, but could also be a mechanical issue. + + + + + diff --git a/hmon/doc/feeerr-trgqual.htt b/hmon/doc/feeerr-trgqual.htt new file mode 100644 index 0000000..b255bdf --- /dev/null +++ b/hmon/doc/feeerr-trgqual.htt @@ -0,0 +1,6 @@ +

Trigger Quality

+

+This button shows the trigger errors per second and the total sum of errors since the last DAQ restart. This rate should be low to avoid events with errors. +

+

Error Handling in case it is not Green

+Try a DAQ restart. \ No newline at end of file diff --git a/hmon/doc/hades-stripes.png b/hmon/doc/hades-stripes.png new file mode 100644 index 0000000..cb94cda Binary files /dev/null and b/hmon/doc/hades-stripes.png differ diff --git a/hmon/doc/link.png b/hmon/doc/link.png new file mode 100644 index 0000000..0532d59 Binary files /dev/null and b/hmon/doc/link.png differ diff --git a/hmon/doc/main-clock.htt b/hmon/doc/main-clock.htt new file mode 100644 index 0000000..4b82d54 --- /dev/null +++ b/hmon/doc/main-clock.htt @@ -0,0 +1,4 @@ +

Wall Clock

+ + +

This is the system time. If it fails, run away. \ No newline at end of file diff --git a/hmon/doc/main-onlineqa.htt b/hmon/doc/main-onlineqa.htt new file mode 100644 index 0000000..30a2270 --- /dev/null +++ b/hmon/doc/main-onlineqa.htt @@ -0,0 +1,6 @@ +

Online QA

+

+Checks if the online QA server is running. +

+

Error Handling if the button is not Green

+Check the QA machine if everything is ok. diff --git a/hmon/doc/main-rate.htt b/hmon/doc/main-rate.htt new file mode 100644 index 0000000..89e0431 --- /dev/null +++ b/hmon/doc/main-rate.htt @@ -0,0 +1,10 @@ + +

CTS Current Rate

+The current rate at which triggers are sent by the CTS. The rate should always be in the expected region!!! If it is not, first take a look at the CTS monitor for the TOF and RPC rates to find out where the problem is located. + + +

Error Handling

+
Shown trigger rate is low, but DAQ is running faster
The counter has a bug if the trigger rate is above 65 kHz (only reachable with pulser) due to a counter overflow. Ignore the warning message in this case. +
Rate is 2-5 Hz
Typically this happens when only calibration triggers are sent and no additional triggers are generated. Make sure this is desired and trigger settings are right. +
The rate is 0
  • Check the "Busy Boards" monitor to see if a front-end has stopped working and is blocking the trigger. Follow the usual restart-DAQ guidelines to get the DAQ running again. +
  • Check the CTS settings if the right trigger source is selected. diff --git a/hmon/doc/main-time.htt b/hmon/doc/main-time.htt new file mode 100644 index 0000000..e6683c9 --- /dev/null +++ b/hmon/doc/main-time.htt @@ -0,0 +1,10 @@ +

    Wall Clock

    +

    This is the system time. Will always be "ok", because it is always a good time to work. + + +

    Error Handling

    + +
    • If it fails, run away. +
    • If you don't know what it means, ask your parents. +
    • If time seems to run slowly, pay more attention to the status reports of DAQ and QA. +
    \ No newline at end of file diff --git a/hmon/doc/mdc-blocked.htt b/hmon/doc/mdc-blocked.htt new file mode 100644 index 0000000..b02f4b7 --- /dev/null +++ b/hmon/doc/mdc-blocked.htt @@ -0,0 +1,9 @@ +

    MDC Blocked

    +

    +This button gives the number of MDC-MBO that do not deliver data (updated only if rate per motherboard is above 1000, and trigger is running at more than 1000 Hz). + +

    +

    Error Handling

    +Do a power-cycle of the corresponding MDC chamber. + + diff --git a/hmon/doc/mdc-linkqual.htt b/hmon/doc/mdc-linkqual.htt new file mode 100644 index 0000000..8f06cf6 --- /dev/null +++ b/hmon/doc/mdc-linkqual.htt @@ -0,0 +1,10 @@ +

    MDC Link Errors

    +

    +This button shows the number of link errors per second. If this number is too high, this could indicate that a front-end board +is damaged. No action on the DAQ is required. +

    +

    Problems can be related to unstable HV in some chambers. + + + + diff --git a/hmon/doc/mdc-oeps.htt b/hmon/doc/mdc-oeps.htt new file mode 100644 index 0000000..3082b1e --- /dev/null +++ b/hmon/doc/mdc-oeps.htt @@ -0,0 +1,10 @@ +

    MDC OEPS

    +

    +This button shows the number of "interesting" OEPS (without giving the adress). For error handling see the button +MDC system. +

    + + + + + diff --git a/hmon/doc/mdc-temp.htt b/hmon/doc/mdc-temp.htt new file mode 100644 index 0000000..8004260 --- /dev/null +++ b/hmon/doc/mdc-temp.htt @@ -0,0 +1,12 @@ +

    MDC Temperature

    +

    +This button shows the temperatures of the four MDC planes. For more detailed temperature distributions in the single MDC sectors, watch +here. +

    +

    Error Handling

    +If there is an over-temperature error, check the power consumption of boards (6.8V should not be above 190A). Restart DAQ to see if power-consumption goes down. A power shutdown of MDC may be required. + + + + + diff --git a/hmon/doc/mdc-token.htt b/hmon/doc/mdc-token.htt new file mode 100644 index 0000000..38ace47 --- /dev/null +++ b/hmon/doc/mdc-token.htt @@ -0,0 +1,10 @@ +

    MDC Token

    +

    +This button shows the number of automatically corrected motherboard errors. The number shouldn't be too high since any re-initialisation needs time. For very high rates, consider a power cycle of the corresponding chamber. +

    +
    + + + + + diff --git a/hmon/doc/mdc-voltage.htt b/hmon/doc/mdc-voltage.htt new file mode 100644 index 0000000..eb2e963 --- /dev/null +++ b/hmon/doc/mdc-voltage.htt @@ -0,0 +1,7 @@ +

    MDC Voltages

    +

    Voltages for all main components are measured on the MDC OEP front-ends continuosly. + + +

    Error Handling

    +

    Any error can only be solved by direct access to the MDC chamber were the problem exists. Thus: No immediate error handling is required. If you notice something strange, a logbook entry describing the problem is sufficient. +Voltages which are far off (should not happen after the system is commissioned for the beam-time) may cause problems with the DAQ, but boards are quite tolerant here. Data quality might be affected earlier. \ No newline at end of file diff --git a/hmon/doc/other-magnet.htt b/hmon/doc/other-magnet.htt new file mode 100644 index 0000000..05186f5 --- /dev/null +++ b/hmon/doc/other-magnet.htt @@ -0,0 +1,16 @@ +

    Magnet

    +

    +This button shows the status of the Magnet systems. +

    +

    Error Handling in case it is not Green for > 2 min.

    + +Call Torsten Heinz (mobile: 0175 388 4066 or home: 06162 982292 or work: 2781
    +and Wolfgang Koenig (mobile: 0172 877 50 49 or home: 06071 35998 or work: 2720)! + + +

    If no ssh connection to the magnet PC is possible (hadesp28), check if the machine is still running (upstairs, next to cryo) + + + + + diff --git a/hmon/doc/other-shower.htt b/hmon/doc/other-shower.htt new file mode 100644 index 0000000..24fed3f --- /dev/null +++ b/hmon/doc/other-shower.htt @@ -0,0 +1,16 @@ +

    SHower status

    +

    +This button shows if there is nothing wrong with general data rates generated by Shower sectors. +

    +

    Error Handling if the button is not Green

    +
    +
    +YELLOW - Message about currents:
    No need to restart DAQ or stop data taking but immediately contact Shower expert. The voltage on the detector has to be changed.
    DAQ restart not required.
    +RED - Message about configuration:
    Try to restart DAQ and if this doesn't help contact Shower expert.
    +YELLOW:
    Usually one front end board on sector 4 starts to generate much noise for no reason, but will also stop by itself. +If it's sector 4 then nothing can be done, if it's a different one you can ask the nearest Shower expert if it should be like this. +Restarting DAQ, which will reload pedestals can help
    +
    +
    + + diff --git a/hmon/doc/other-speech.htt b/hmon/doc/other-speech.htt new file mode 100644 index 0000000..b0a88fb --- /dev/null +++ b/hmon/doc/other-speech.htt @@ -0,0 +1,11 @@ +

    Speech Output

    +

    +This button shows the status of the speech deamon which gives you accustic informations in case of critical problems +with any subsystem. + +

    Error Handling if the button is not Green

    + +It can only be switched off. If that is the case, turn it on. + + + diff --git a/hmon/doc/restartEBguideline.htm b/hmon/doc/restartEBguideline.htm new file mode 100644 index 0000000..ec76330 --- /dev/null +++ b/hmon/doc/restartEBguideline.htm @@ -0,0 +1,16 @@ + + + + +Tactical Overview Documentation + + + + + +
     back 
    +

    Restart EB Guideline

    +

    In case EB has to be restarted

    + + \ No newline at end of file diff --git a/hmon/doc/restartdaqguideline.htm b/hmon/doc/restartdaqguideline.htm new file mode 100644 index 0000000..0ad1fb8 --- /dev/null +++ b/hmon/doc/restartdaqguideline.htm @@ -0,0 +1,45 @@ + + + + +Tactical Overview Documentation + + + + + +
     back 
    +

    Restart DAQ Guideline

    +

    In case DAQ has to be restarted

    +

    First, check the QA monitor and user guide to see if there is a more appropriate solution to the problem you experience. + +

    The DAQ-Control provides the necessary operations for a DAQ restart.: + +

    1. Press "Start DAQ" to restart DAQ. An orange window appears and +should disappear after 30s-40s if the restart was successful. +An unsuccessful attempt is indicated by an error message in +the orange window. Try a second DAQ restart, if the first +one failed. + +
    2. In the case of an unsuccessful DAQ restart a MDC Power Cycle +has to be performed. The steps of a MDC Power Cycle are described +in the Operator Guide Chapter 34.2. After this operation the DAQ +has to be restarted. Follow the instructions given in step "1. )". + +
    3. In the Case "2. )" failed, the "RebootMDCHub" icon should be used. +After pressing "RebootMDCHub" and waiting 30 seconds, the DAQ has to be +restarted which is described in "1. )". + +
    4. In the case step "3. )" was not successful, a "Full Power Cycle" has to be +performed. This procedure is described in the "Operator Guide Chapter 33.1" +Restart DAQ following the steps in "1.)" . + +
    5. The DAQ expert has to be called if the DAQ is still not working. +
    + + +

    All DAQ-Control Tools will open a orange window with their output which disappears +after they finished. Make sure that no two orange windows are open at the same time. + + \ No newline at end of file diff --git a/hmon/doc/server-cpu.htt b/hmon/doc/server-cpu.htt new file mode 100644 index 0000000..5316b15 --- /dev/null +++ b/hmon/doc/server-cpu.htt @@ -0,0 +1,18 @@ +

    Server CPU

    +

    +This number gives you the server cpu with the highest load, which should not be exceeding ##%. A high server cpu leads to discarded events.
    +See a list of the CPU loads here. +

    +

    Error Handling if the button is not Green

    + +
    +
    You should have a look if there is some error in the status of the Eventbuilder-buttons.
    If not, ignore the error. +
    If there is a problem, restart Eventbuilders (see restart-instructions for +Eventbuilders)
    +
    +
+ + + + + diff --git a/hmon/doc/server-etrax.htt b/hmon/doc/server-etrax.htt new file mode 100644 index 0000000..2f6da1b --- /dev/null +++ b/hmon/doc/server-etrax.htt @@ -0,0 +1,13 @@ +

Status of the TRB

+ +This field shows if the TRB is up and checks its status. + + +

Error Handling

+ +

+In case of an error (red field), please take a look to +the Etrax tactical overview. + +

An overview of the different servers and services monitored is given in the HADES Wiki + diff --git a/hmon/doc/server-fill.htt b/hmon/doc/server-fill.htt new file mode 100644 index 0000000..f2deb41 --- /dev/null +++ b/hmon/doc/server-fill.htt @@ -0,0 +1,16 @@ +

Disk fill level

+

+This button gives the disk fill level. +

+

Error Handling if the button is not Green

+ +
+A detailled view of the fill level of every single disk can be seen here. The DAQ expert (!) should delete +files, that have already been copied to lustre or on tape. +
+ + + + + + diff --git a/hmon/doc/server-icinga.htt b/hmon/doc/server-icinga.htt new file mode 100644 index 0000000..ca22f67 --- /dev/null +++ b/hmon/doc/server-icinga.htt @@ -0,0 +1,14 @@ +

Status of the Icinga Server

+ +This field shows if the Icinga Server is up and checks its status. + + +

Error Handling

+ +

+In case of an error (red field), please take a look to +the Icinga tactical overview. An eMail is automatically sent to a DAQ-expert, +who should know how to proceed. + +

An overview of the different servers and services monitored is given in the HADES Wiki. + diff --git a/hmon/doc/server-pwrsup.htt b/hmon/doc/server-pwrsup.htt new file mode 100644 index 0000000..7fc3684 --- /dev/null +++ b/hmon/doc/server-pwrsup.htt @@ -0,0 +1,15 @@ +

Status of the Power Supply

+ +This field shows if the Power Supply is okay and checks its status. + + +

Error Handling

+ +

+In case of an error (red field), please take a look to +the Icinga tactical overview. +

+ +If nothing helps, call a DAQ expert. + +

diff --git a/hmon/doc/trg-accepted.htt b/hmon/doc/trg-accepted.htt new file mode 100644 index 0000000..a2106d1 --- /dev/null +++ b/hmon/doc/trg-accepted.htt @@ -0,0 +1,16 @@ +

Trigger accepted

+

+This button shows in percentage of available triggers accepted by the CTS to read out the front-end boards. +Typical value should be around 50% in total. +The first value shows the percentage of accepted triggers in the last second, the second value is the integral number for the last spill. +

+

Error Handling if the button is not Green

+ +
+The beam quality could be bad. The shift leader has to decide whether to call the control room. +
+ + + + + diff --git a/hmon/doc/trg-ptrate.htt b/hmon/doc/trg-ptrate.htt new file mode 100644 index 0000000..d3e5978 --- /dev/null +++ b/hmon/doc/trg-ptrate.htt @@ -0,0 +1,9 @@ +

PT3 Rate

+

+This button shows the triggered high multiplicity events per second compared to the countrate in the Start-detector. +The second number should be around 0.7% during beam time since the interaction rate is around 1%. The first value is the rate +of PT3 triggers provided to the CTS. +
+If something goes wrong, ask your shift leader. + + diff --git a/hmon/doc/trg-source.htt b/hmon/doc/trg-source.htt new file mode 100644 index 0000000..e9bcd7d --- /dev/null +++ b/hmon/doc/trg-source.htt @@ -0,0 +1,17 @@ +

Trigger sources

+

+This button displays the used Trigger source. It is yellow if there is a trigger input error to CTS. +

+If the button is green-yellow, the pulser is switched on. + + +

How to deal with problems:

+ + + + + diff --git a/hmon/doc/trg-spill.htt b/hmon/doc/trg-spill.htt new file mode 100644 index 0000000..6fc2272 --- /dev/null +++ b/hmon/doc/trg-spill.htt @@ -0,0 +1,5 @@ +

CTS Spill Rate

+The number of accepted triggers per spill is calculated based on the event counter, and spill start/stop information provided by the CTS. Spill start is a signal we get from the accelerator, spill stop is generated by the CTS after the spill length given in the CTS settings (see CTS monitor / settings overview). Additionally, the 10-spill and 50-spill average are calculated. + + +

Error Handling

diff --git a/hmon/doc/trg-start.htt b/hmon/doc/trg-start.htt new file mode 100644 index 0000000..47316a4 --- /dev/null +++ b/hmon/doc/trg-start.htt @@ -0,0 +1,8 @@ +

Trigger Start Counter

+

+This button gives you the number of counts per second in the start-detector of the last spill (second value). The first one is the trigger count for the last second. +
+In case of problems, ask your shift leader. + + +