HV for the RSSC's comes from the Bertan Supplies (red panels) in the NIM bin above the LeCroy HV Mainframes. There are six NIM modules each having two channels of HV and each channel has two sectors worth of chambers on it.

a) An alarm will sound. Reset the alarm.

b) Find the RSSC that tripped by looking for the red panel with a red led that is OFF.

c) Note the value of the pot (setpoint). And turn the pot down, counter-clockwise to zero.

d) Toggle the reset switch from on to off to on. Light should come back on. If not, it may be necessary to wait a minute or so for the HV to ramp down before it can be reset.

Do NOT leave the switch down in the "Auto Reset" position. This can damage the chambers.

e) There is a brownish multimeter (DVM) located at the red panels. Turn the DVM to read DC Voltage. Plug it's input to the output of the tripped RSSC channel. This requires removing a lemo-cable.

f) There is yellow tape above or below the red panels. Note the value of the tripped channel.

g) Turn the pot up until the value on the DVM is the value on the tape. The conversion is 1kV on RSSC = 1V on multimeter.

h) Make a note in logbook.

5. UTC trip

HV for the UTC comes from the Bertan Supplies (red panels) in the NIM bin above the LeCroy HV Mainframes.

a) An alarm will sound. Reset the alarm.

b) Find the UTC channels that have tripped by looking for the red leds that are not on.

c) Call the expert. Appendix-H

Do not proceed with out an experts advice, the UTC is very delicate! Current expert is Toshio Numao - TRIUMF - (604)222-7345 toshio@triumf.ca, Former expert is George Redlinger - BNL - x3056

d) Other trips/alarms...

Many things can happen. However most of the electronics have steps on what to do. Just look around the area of interest, most likely an expert has taped the steps onto the readout panel, monitor, etc.

B. Rare problems. At least we hope they are rare.

1. This manual is not complete and mostly covers only minor problems during the collection of data. Check the Table of Contents to determine if the manual can help you solve the problem occurring.

2. Solutions elsewhere

a) Look in the small black binder that is label "E949 Shift?".

b) Check the "E787 Trouble Shooting Guide" for somewhat old but sometimes helpful information on about everything.

c) If V.1-V.2.b, does not contain the information or you are untrained in the details of this information, i.e. the problem is not solved, CALL AN EXPERT. Do not be shy, especially if we have beam. Look in Appendix-H for areas of expertise.

VI. Before you leave

A. Fill out Shift summary. {Toolchest}: <Shift summary> -> <Last 8 hours>

1. Fill out information in table of why the DAQ was not running while beam was on. Instructions are above table.

2. Under comments write down anything of major importance that happen during your shift. Such as lots of errors in DAQ (trigger hangs, Cleanups...), Beam hours, changes to hardware. Basically, summarize problems here.

3. Glitches: Note any problems that occurred during standard mix runs. Follow the table's format.

B. Inform the new guy or gal of anything unusual the person may encounter.

C. Say "bye" to the new shifter.

D. Go have a beer and think maybe there was a pnn event during your shift!

Appendix A. Menus and Windows

**********************************************************************************************

* used operations in {Toolchest}

*----------------------------------------------------------------------------------

*<DAQ> -starts a production version of data acquisition.

*<DAQ new> -starts a "beta" version of the data acquisition.

*<Cleanup DAQ> -kills (most/all) programs DAQ is running

*<PPC> -Power PCs

* <Reboot PPCs>

* <PPC Windows> -creates ppc01, ppc02, ppc03, ppc04

*<High Voltage>

* <DeMon> -Starts DeMon, the high voltage controling program

* <CsI HV>

* <status> -Pops up a window stating if the CsI HV is on or off

* <ON> -Turns CsI on

* <OFF> -Turns CsI off

*<QOD> -Quality Of Data

* <DAQ production>

* <Run QOD> -Pops up a QOD window, for use during a normal run

* <Run QOD (cosmic)> -Pops up a QOD window, for use during a cosmic run

* <REPLAY on QOD>

* <REPLAY QOD with Print> -Prints QOD file

*<Photo>

* <production>

* <Photo (1sec duration)> -Allows users monitor the events visually

*<Shift summary>

* <Last 8 hours > -An emacs window appears, for user comments

* <Last 4 hours > after his/her shift

* <Last 24 hours>

*<EOS-MON> -End-of-Spill Monitor of Scalars

**********************************************************************************************

* {E787 Data Acquisition System} or {DAQ}

*-----------------------------------------------------------------------------------------

*<Control> <Processes> <Messages> <Help>

* | | | |

* V V V V

*<Control Panel> <data input > <Clear > <about>

*<run limits > <data reducer > <beep on update > <help >

*<set music > <scaler monitor> *<output to log file>

* <verbose >

* <event builer > -> <dd.eb >

* <e787daq>

* <fifo monitor > -> <dd.eb >

* <e787daq>

* <PPC consoles > -> <e787ppc01>

* <e787ppc02>

* <e787ppc03>

* <e787ppc04>

*-----------------------------------------------------------------------------------------

* run status date

* ------------------------------------------------------------

* Run number Spill number kbytes/event

* Events in run Events in spill Event limit

* Mbytes in run kbytes in spill Volume limit (tape limit)

* Running time Spill time Spill timeout

* DI state :

* Output volume:

* SSP init stat:

* TRIGintt stat:

*-----------------------------------------------------------------------------------------

*(The 3 rows of < ... > below are in the same location,)

*(but are different at different stages of the run )

* <hardware> <begin run> < exit > -before a run

* <comment > < pause > <end run > -duringa run

* <comment.> <continue > <end run > -during a pause

*-----------------------------------------------------------------------------------------

* Updated information every ~2 seconds.

**********************************************************************************************

* {hardware initialization}

*-----------------------------------------------------------------------------------------

* <setup> <pedestals> <CAMAC> <tests> <help>

* | | | |

* V V V V

*<SSP init > <feraped> <fera > <tdctest>

*<SSP config > <fbped > <predet >

*<trig > <ccd ped> <cfd >

*<reboot PPCs> <tddac > <scf >

* <flash >

* <level 1.2>

* <all >

*-----------------------------------------------------------------------------------------

* <clear> <OK>

**********************************************************************************************

* {dp0}

*-------------------------------------------------------------------------------------------

* Defined Streams

*-------------------------------------------------------------------------------------------

* stream device status label triggers

*-------------------------------------------------------------------------------------------

*C_stdmix /dev/mx0nrv open 30076.2.1 ALL

*C_stdmix /dev/mx1nrv open 30076.2.2 ALL

*-------------------------------------------------------------------------------------------

*status file close /dev/mx2nrv 0 -an example of what

*device /dev/mx2nrv now closed is here

*Cycling down the cycle info; dp0_idx = 2, pid = 18469

*stream # 0 deleted

*-------------------------------------------------------------------------------------------

* Configure Streams Open/Close Streams

* --------------------------------------- -------------------------------------------

* | --------------- ---------------- | | ------------------- ---------------- |

* | --------------- ---------------- | | ------------------- ---------------- |

* | --------------- ---------------- | | ------------------- ---------------- |

* --------------------------------------- -------------------------------------------

* ------------- ------------------------- -----------

* | | | | | |

* | | | | | |

* ------------- ------------------------- -----------

**********************************************************************************************

*********************************************************

* {Change Stream Configuration} *

*-------------------------------------------------------*

* *

* ------------------------- *

* | | *

* | Add Stream | *

* | | *

* ------------------------- *

* *

* ------------------------- *

* | | *

* | Delete Stream | *

* | | *

* ------------------------- *

* *

* ------------------------- *

* | | *

* | Delete All Streams | *

* | | *

* ------------------------- *

* *

* ----------------- --------------------- *

* | Save || Read | *

* | Configuration || Configuration file| *

* ----------------- --------------------- *

* | Enable | | Disable | *

* | Stream | | Stream | *

* ----------------- --------------------- *

* *

* ------------------------------------------*

* | OK | *

* ------------------------------------------*

*********************************************************

****************************************************************************************************

* {DeMon}

*---------------------------------------------------------------------------------------------------

* <File> <Help>

* |

* V

* <Quit>

*---------------------------------------------------------------------------------------------------

* ------------ DeMon Event Log

* Enter channel name: | | ---------------------------------

* ------------ |... |

* |Mainframe 7 loaded ... |

* Subsystem Viewer |... |

* <Error><RS><BV><BL><TT><BM><UV<RV><CV>AD><CO><MC><IC><VC> | |

* ---------------------------------

*----------------------------------------------------------------------------------------------------

* Mainframe Control Panels

* ------------------------

* Mainframe 1 ... ... ... ... ... ... Mainframe 8

* ----------- -----------

* <Power> ...

* [ON/OFF] ----- ON (Red background) ...

* <View > OFF (Green background) ...

* Channels

* in use:

* ---------

* | 256 |

* ---------

* Channels

* in error:

* ---------

* | 0 |

* ---------

******************************************************************************************************

Appendix B. DAQ

I. How to do a standard run in DAQ

A. Starting a run

Usually the DAQ is up and running (in some form-or-fashion) when one arrives on shift. So you most likely start at step I.i.4. TO SAVE TIME - step (9) can be done while step (5) completes.

B. If terminal(s) are off.

Connect to bnlku9.phy.bnl.gov

open an bnlonl account on bnlku9 and type

>toolchest

C. Load PPCs

{TC}: <PPC> -> <PPC Windows> -wait for the prompts in the ppcs before going to step D.

1. Start DAQ

{TC}: <DAQ> -this will create the {dp0} and

{DAQ}: <start> {E787 Data Acquisition System} ({DAQ} from now on).

D. High Voltage

1. Start DeMon -DeMon needs to be on otherwise DeToX will raise hell.

{TC}: <High Voltage> -> <DeMon>

2. Turn ON HV crates if OFF. -See Appendix-E on how to use DeMon

E. CsI HV

1. Check CsI HV status.

{TC}: <High Voltage> -> <CsI> -> <status>

2. If CsI is OFF turn it ON

{TC}: <High Voltage> -> <CsI> -> <ON>

F. Load SSP.

{DAQ}: <hardware> -this will pop-up the {hardware} window.

{hardware}: <setup> -> <SSP init> -select the desired SSP file, click <OK>

Load trigger.

{DAQ}: <hardware> -window should be open from step (5)

{hardware}: <setup> -> <trigger> -select the desired SSP file, click <OK>

G. "Do a CAMAC."

{DAQ}: <hardware> -hardware window open from steps above

{hardware}: <CAMAC> -> <all> -Look for errors shown in the output (on screen)

H. {hardware}: <ok>

I. Data Streams

1. Check to see if the current devices (tape drives) for the data streams in the {dp0} screen are the tape drives with the tape(s) in them. If not, consult "How to run dp0".

2. Open data streams

If they are already open go to step (10).

{dp0}: <open closed streams> -A pop-up menu will appear {tape labels}

{tape labels} -Erase ALL of the field's content.

Type the tape number (only 5 numbers)

{tape labels}: <change all> -Another pop-up window will appear Click on <append>.

3. The results of (a) should have the something similar to the following in {dp0}:

Before going on to step (10) be sure the status of all the streams are open (like example below).

C_stdmix /dev/mx0nrv open 30076.2.1 ALL

C_stdmix /dev/mx1nrv open 30076.2.2 ALL

4. If problems occur loading the tapes, consult "How to run dp0" in this manual.

Start the run.

J. Start the run.

{DAQ}: <begin run>

K. QOD (Quality of Data)

1. Open QOD

{TC}: <QOD> -> <QOD (DAQ Production)>

-> <Run QOD> -for a standard run

-> <Run QOD (cosmic)> -for a cosmic run

2. Start QOD

KOFIA>an # -type "an" with # = to a few thousand

L. Photo -Pretty pictures to watch while collecting data.

1. Open Photo.

{TC}: <Photo> -> <production> -> <Photo (1 sec duration)>

2. Start Photo.

KOFIA>an -short for analyze

M. Sit back and relax you are collecting data!

II. Ending a run

A run ends for various reasons.

In good situations: tape is full, Error: "Tape volume limit"

too many events in run, Error: "Event limit size"

you manually <end run> due to job size, etc.

In bad situations: Some type of DAQ error.

If it is a bad situation, a Cleanup maybe required. Look in Appendix-B.III. "When troubles arise in DAQ."

A. If the person on shift wants to end the run do the following:

{DAQ}: <end run>

Otherwise, DAQ has ended the run on its own accord

B. Ending QOD

1. Save QOD (if it was running). In the QOD window, type the following after the prompt appears.

KOFIA>save -type "save"

Enter save file ID name>{trig}_ -current QOD file format is: 'trigger name'_

For example: trigger used file ID name

smx_v12j "smx_"

km21.ps100 "km21_"

2. If QOD does not return to the KOFIA> prompt at the end of a run, and you want to save the histograms:

open an bnlonl account on bnlku9

$ONLINE_BIN/dd_cleanup

goto B.I.ii.2.a

You will have to do a cleanup after this is done! (B.III.3.a)

3. Exit the QOD window. Otherwise the previous run's events will be added to the next run's events (however you may want to do this for various reasons).

C. How to do pedestal runs in DAQ

It is best to do pedestals when we have NO beam. That way we maximize the pnn data we collect. So if the shift-taker knows that there will be a time during shift when no beam will occur, wait until then (unless told by experts otherwise). If are expecting down time in the AGS (or C-line), go ahead at some point during your shift and do feraped, tdped, ccd ped. But DO NOT DO A TDDAC WITH BEAM ON!

1. feraped

{DAQ}: <hardware>

{hardware}: <pedestals> -> <feraped>

2. tdped

{DAQ}: <hardware>

{hardware}: <pedestals> -> <tdped>

3. ccd ped

{DAQ}: <hardware>

{hardware}: <pedestals> -> <ccd ped> -> "all_crates" <OK>

4. tddac

a) {DAQ}: <hardware>

{hardware}: <pedestals> -> <tddac> -> "all" <OK>

b) If {hardware} screen states "BAD channels" then do the following:

Do II.4.b until the channel/board does not show a "Bad channel". NOTE: a "not-so-bad" channel is acceptable.

>cd $TDDAC_BIN

>do_tddac_ch_board CRATE BOARD -get CRATE address and BOARD number from {hardware} screen.

c) If (4b) always comes back with a BAD channel then note it in the log book and consult an expert.

III. How to deal with DAQ errors

A. DAQ error...

1. If the error made the DAQ end the run, go to (B).

2. If the DAQ is still running, {DAQ}: <end run>.

B. Determine the type of error which occurred.

Requires a: Cleanup ppc-reboot CAMAC

spill count mismatch Fera board off (noticed by an unrecoverable trigger hang)

*DC2 header word wrong

Event count mismatch

Event number mismatch

C. Follow the "Steps for a ..." (below) depending on the type of error. The steps below will refer to steps in Appedix-B.I.i.

1. Steps for a Cleanup

Close data streams.

{dp0}: <close all open streams>

{Toolchest}: <Cleanup DAQ> -this will kill the DAQ programs and reboot ppcs *if ppcs do not reboot, do it manually. Go to step Appedix-B.I.2

2. Steps for a ppc-reboot

Control-x on each {ppc##} window. -Manual reboot

OR {hardware}: <setup> -> <reboot PPCs>

OR {TC}: <PPC> -> <Reboot PPCs>

3. Steps for a CAMAC

Appendix-B.I.7

Appendix C. dp0 & data streams

I. Opening Steam(s)

A. To open one stream

1. Select the desired stream.

2. {dp0}: <Open Selected Stream>

B. To open all streams.

{dp0}: <Open all closed Streams>

II. Closing Stream(s)

A. To close one stream.

1. Select the desired stream.

2. {dp0}: <Close Selected Stream>

B. To close all streams.

{dp0}: <Open all Open Streams>

III. Changing Streams

To modify the streams:

{dp0}: <Change Configuration> -This will popup {Change Stream Configuration} referred to {CSC} from now on.

A. Delete (All) Stream(s)

1. To delete one stream

a) Select the stream by dragging the mouse over a few characters in the desired stream.

b) {CSC}: <Delete Stream>

2. To delete all streams

{CSC}: <Delete All Streams>.

B. To add a stream.

{CSC}: <Add Stream>

C. To change to different streams by a file.

1. Delete all streams (C.III.1.b)

2. {CSC}: <Read Configuration file>

{CH_CONF_SR_DS}: select the desired file a click <OK>.

For current running with 2 tapes the files to use are:

std_mix_01_0.1 std_mix_01_1.0 std_mix_01_2.0 std_mix_01_3.0

std_mix_01_0.2 std_mix_01_1.2 std_mix_01_2.1 std_mix_01_3.1

std_mix_01_0.3 std_mix_01_1.3 std_mix_01_2.3 std_mix_01_3.2

The above files are all variations of using 2 tapes. The format is trigger_year_"tape 1's device"."tape 2's device"

3. To make a new configuration file.

Open a bnlonl account on bnlku9

>cd /e787d/bnlonl/online_conffiles

>emacs 'newfile_name' &

Current format for a file is:

C_stdmix /dev/mx2nrv ALL - stream device trigger

C_stdmix /dev/mx3nrv ALL

C_ must be the prefix of the stream

IV. Monitoring tape information

{dp0}: <Monitor> -Big button on bottom-left

These popup windows will show how much tape is used and the rate of transfer to each tape.

V. Problems with dp0

A. Opening/Closing Streams

If the streams are not opening/closing, check to see if the streams in {dp0} match the devices that are being used. If not, change the streams to the correct devices, C.III.

If all else fails, do a cleanup and restart DAQ, thus restarting dp0, see Appendix-B.111

B. ?

Appendix D. DLT tape handling

Do NOT operate the 'handle' on the DLT drive unless the "operate handle light is ON"

I. To unload a DLT

A. Close the any open streams in {dp0} (consult Appendix-C).

When you close the stream a pop-up window will ask if you want to print the label for this tape. Click <yes>. The tape's label will be printed out. If you are writing to two tapes, you will have to click <yes> twice and get 2 tape labels. Cut out the larger label and keep it for step 8.

B. From any account on bnlku9, for each tape type

>mt -t /dev/mx0nrv unload -Substitute the relevant DLT drive name above. The drives names are:

mx0nrv mx2nrv -this is the way they are

mx3nrv mx1nrv geometrically arranged.

C. Wait for the green 'operate handle' light on the front panel of the DLT drive to turn on.

D. Lift the handle. This partially ejects the DLT.

E. Extract tape from drive

1. Gently pull the DLT out of the drive. There are cases where the DLT gets caught on something inside the drive and will not come all the way out. In this case, push the DLT back in, lower the handle, and go back to step 2.

2. If the tape is officially stuck, then consult an expert. In the meantime, load the tapes for the next set of runs in other available tape drives. You will have to change the streams in {dp0} consult Appendix-C.

F. Labels... consult D.III.

1. Place the tape label from print out in the DLT case.

2. Place the tape label in ELOG.

On a new entry, place ~bnlonl/online_logfiles/tape_labels/{tape #}_{01 or 02}.ps for Attachment...

For example, your two tapes are 30204.2.1 and 30204.2.2 do the following:

Attachment1: ~bnlonl/online_logfiles/tape_labels/30204_01.ps

Attachment2: ~bnlonl/online_logfiles/tape_labels/30204_02.ps

G. Write-protect the tape. Push a tab on the side with the label, to the left. An orange square will be showing if it is write-protected.

H. Place the tape and its label in its case. Then place with the other run tapes.

II. To load a DLT

A. Place a label on the tape.

1. Remove the appropriate 'sticker' with the next tape number on it.

The label sheet should be near the tape drives.

It will have 4 columns of numbers such as

30078._.1_ 30078._.2_ 30078._.3_ 30078._.4_

If we are still using two tapes during running, the two labels needed would For example: 30078._.1_ 30078._.2_

2. Place the appropriate sticker label on a DLT paper tear-out label and slide it in the tape-label slot (look at a used DLT tape for an example).

B. Inserting the tape

1. Place the 30078._.1_ tape in the drive listed first in the {dp0} streams list and Place the 30078._.2_ tape in the drive listed second in the {dp0} streams list and so on.

2. Raise the handle of the appropriate tape drive.

3. Place the tape in this drive's slot and push it all the way in.

4. Lower the handle of tape drive.

5. A yellow light should start to blink.

III. To print tape labels

A. When there is a "tape volume limit" in the {DAQ}, close the open streams (Appendix-C).

After one closes open streams, a window will pop up and ask if you want to print the tape labels. If you do want to print the tape labels click <yes>, click <yes> after a "tape volume limit". Otherwise, click <no>.

B. Print-out

The print-out will have a large and small summary table. Place the large summary table in the plastic case with the tape. Place the small summary table in the log book.

C. Manually printing tape label

If you don't click <ok> on the popup window OR if you notice a tape without a label:

Open a bnlonl account on bnlku9

>cd ~bnlonl/online_logfiles/tape_labels

>latex {DLT tape #} -creates a .dvi file

>dvips {DLT tape #} -creates a .ps file

>lpr -Pe787lp2r {DLT tape #}.ps -prints the .ps file

IV. Monitor DLTs

A. Every so often an xmessage appears asking

"xxx monitor" -xxx will be the monitor-number used below

mx0nrv mx2nrv mx3nrv mx1nrv

B. Place a monitor sticker-label on the new tape.

1. Remove the appropriate 'sticker' with the monitor number on it. The label sheet should be near the tape drives.

It will have 4 columns of numbers such as

mon01.00081 mon01.00101 mon01.00121 mon01.00141

2. Place the appropriate label on a DLT paper tear-out label and slide it in the tape-label slot (look at a used DLT tape for an example).

C. Lift the handle of an open drive.

D. Place the 'mon01.xxxxx' tape in the slot and push it all the way in and then lower the handle.

E. A yellow light should start to blink.

F. In the xmessage window, click on the drive used for the monitor. 'The monitor' program will do the rest.

G. After some time, another xmessage will appear stating "xxx mon01.xxxxx is done"

H. Go to the drive with the monitor tape in it.

Make sure the 'Operate Handle' light is on.

I. Lift the handle and remove the tape.

J. Monitor tape summary with two identical tables.

Cut out the two tables. Place one in the case with the monitor tape (the other label was placed in the logbook, which we no longer use). So place the tape summary file as an attachment to an ELOG entry (automatically done). Example: Attachment1: /e949d/e787/monitors/backup_new/log/label/mon01_xxx_tex_label.ps

K. Write-protect the tape.

Push a tab on the side with the label, to the left. An orange square will be showing if it is write-protected.

L. Place the tape in its case with the other monitor tapes.

Appendix E. DeMon

DeMon a program that controls and monitors the high voltage to the detector elements (except CsI aka end-caps).

To open Demon: -{TC}: <High Voltage> -> <DeMon>

OR -open a bnlonl account on bnlku9: and >dm

I. Loading a new file

At some point an expert may tell a shift taker to 'load' a new high voltage file. Most likely the expert has made the changes he/she wanted and all they want you to do is to Restart DeMon. Do the following to restart DeMon.

{DeMon}: <File> -> <Quit> -This will exit DeMon

{TC}: <High Voltage> -> <DeMon> -This will startup DeMon

II. Viewing the present voltage

A. A specific channel

Use the "Enter channel name" field. The format of the channels is:

Range Stack (RS), Barrel Veto (BV), Target (TT)

B. A detector region

1. On the left side of {DeMon} there is a "Subsystem Viewer".

2. Click on the subsystem desired from the choices given.

Error - channels that DeMon thinks are out of tolerance

RS-range stack BV - barrel veto BL-veto liner

TT-target BM-

UV- RV-

CV- AD- CO-

MC- IC- VC-

3. This will popup a window with every channel in that subsystem. Use the following to move about:

> move down one channel

< move up one channel

>> move down one page

<< move up one page

>>| move to the bottom

|<< move to the top

C. View an entire mainframe

1. On the bottom half of {DeMon} there is the "Mainframe Control Panel".

2. Click on <View> under the desired Mainframe to view the HVs.

3. Be sure to close the popup window after viewing each separate mainframe. I have crashed the monitor due to using to many colors (or something like that) because I viewed every Mainframe with out closing any of the popup windows.

III. To turn OFF or ON a (all) Mainframe(s)

A. Look in the "Mainframe Control Panels" (bottom half of {DeMon}

B. Click <Power> under the desired Mainframe.

It will take a few minutes to load the files.

IV. To change the high voltage file

A. Open as online on bnlku9.

bnlku9_e787[n]>setup online

bnlku9_e787[n]>cd $DEMON_DATA -this will take you to /e787/local/online/demon/data.2001

B. Make a soft link to the file you desire to hv.{detector subsystem} (hv.rs -range stack, etc.)

For example: you have created a new range stack high voltage file (hv.rs.45447), then do the following:

bnlku9_e787[n]>rm hv.rs

bnlku9_e787[n]>ln -s hv.rs.45447 hv.rs

Make a note in the log book when, why, and to what file.

Restart DeMon. (E.I)

V. Problems with DeMon

A. If DeMon is not communicating with the LeCroy High Voltage Crates:

1. Close {DeMon}

2. On the VT220 -terminal located at the LeCroy HV crates

>set PRIV

Password>system

>logout port n -n = crate number 1 through 8 (9 = CsI)

3. telnet hv787.phy.bnl.gov 3001

4. Reload DeMon.

Appendix F. Elog procedure

Many of the elog entries are now automated. However try to keep an eye on the entries during your shift. It is located at http://bnlku33.phy.bnl.gov:8081/EL/?exp=E949

I. New Elog entries

A. Time

The time of the entry is automatic and is the time at which you hit <submit>.

B. Run number

Automatically enters current run number, but this can be modified.

C. Author

Any person that was involved with the entry is entered here, such as benjil for Benji Lewis.

D. Type

1. Routine

Anything standard during the running

2. Glitch

Something has corrupted the data, i.e. the data is not useable for analysis.

3. Shift Summary

Enter highlights during your shift.

4. Modification

Something has changed to files, electronics, etc.

5. Daq error

When the DAQ crashes, use this type. Even though the DAQ has crashed routinely in the past do not put it under Routine.

6. Run

Used by the online script

E. System

1. General

2. DAQ

Anything dealing with DAQ

3. Detector

If you have modified some sub-detector in the experiment use this system.

4. Electronics

If you have modified some electronics in the experiment use this system.

5. Beamline

Changes/problems in the beamline

6. AGS

If the AGS, has told you something

7. Slow control

F. Subject

Place a summary of the Text field.

G. Text

This is the body of the entry. Place as much detail as to inform other collaborators of what has happen.

H. Attachment (#)

Associated files with the entry.

II. Automated entries into Elog

A. At the begging of a run, online_script writes:

Beginning-of-Run (BOR) time, Run number, SSP file, Trigger file, stored to disk/tape/trash can.

B. At the end of a run write the following:

End-of-Run (EOR) time, Run number, Number of events

C. Tape Labels

Prints the tape label file and stores as an attachment here.

D. Shift Summary

Automatically entered now, however still needs the users input for the highlights, etc.

E. Pedestals

The pedestals feraped, fbped, ccdped, tddac enters into elog that it has been performed. The pedestal also enters the file that is also printed out.

III. Manual entries into Elog

A. Bad stuff

1. Note things that happened during the run in the log book such as:

trips in separator, magnets, high voltage

when you paused a run & why

errors that popup from DeToX, QOD, RSMon, etc.

anything that people do upstairs

etc.

Appendix G. QOD (Quality of Data)

Appendix H. Experts (group contact info.)