Another small window will appear having three options:
(i)Reboot ROM
(ii)Run Calibration on the ROM
(iii)Validate Calibration

Select option Reboot ROM.

Then select option Run Calibration.
Enter configuration key as

4a2

Check if it runs successfully. If yes, then go to step 4.
If no, then try to fix the errors.

4. Validate Calibration

Select option Validate Calibration.

Quick Key reference

Current Configuration Keys

Is your environment configured correctly?

 cd $BFROOT/detector/dch/DchProto2

where the command prompt appears.Hit return key to complete the command.After this step,you will get the prompt as

 /afs/slac.stanford.edu/g/babar/detector/dch/DchProto2>_

Enter :

source DchTestStand/setup.csh

at the prompt & hit return.
Now let's run the calibrations.

Start Xyplex window

After Configuring your environment, you will get the prompt as

 /afs/slac.stanford.edu/g/babar/detector/dch/DchProto2 >_

Enter:

 startXyplex

at the prompt & hit return.you will get a small GUI on the screen having 3 options ROC26,JAY and close all connections.Click on ROC26.Hit return in the window that opens.
Do not open the Xyplex window unless you are running a calibration. The DAQ system captures all of the ROM output to log files. The Xyplex connections intercept that output before it can be logged, making debugging difficult.

Before you start running a Calibration

Ramp DCH HV to OFF
Check with the DAQ expert (if he/she is around) that our partition is free. This check is not essential: if the DCH is partitioned you will discover it really soon: calibration will just not start at all.

Start Calibration

Go back to the terminal window where you had typed startXyplex & now type

 startCalib

at the prompt.Hit return. After this step,another small GUI will appear on the screen having 3 options Reboot ROM,Run calibration on the ROM & Validate calibration.
Click on reboot.After Reboot is completed,click on Run calibration on the ROM.You will get 2 windows on the screen Proto II event Level & Proto II Control Level.Control Level window will ask you

Enter the configure environment value

Enter the value as

4a2

Check if it runs successfully.Watch out for Control Level to show

 Unconfigure transition successfully completed.Enter the configure environment value

Enter the value as 0 to exit.It will ask you to hit return.Hit return.Then hit return in the Event Level window.If there are any errors,try to fix it.

Warning

Please do not close these GUIs.
Do not play with the green GUI: If you click on Reboot Roms while somebody is taking data and you reboot the ROMs, he/she is not going to be very happy about it...

Validate Calibration

After successfully running the calibration, Click on Validate Calibration.It will ask you

 Do you want to validate this calibration run? (Y/N)

Type N & hit return.This will close the window.The DAQ system captures all of the ROM output to log files. The Xyplex connections intercept that output before it can be logged, making debugging difficult.

Help

Open a help window. It's just a less of a text file, so you can quit typing "q", go forward with the space bar, go backward typing "p"

Run Calibration on the ROMs

Runs the standard DCH calibrations on the ROMs. Standard means:

Dummy meta cycle to sync the system
Noise Floor Calibration (at the moment scanning the discriminator threshold between ~ 120 and 250 mV)
Pedestal Calibration
T0 Calibration
Analog Gain Calibration

What to expect to see on the screen:

opens a xterm from where it disolves the partition (and closes it when done)
opens a xterm for the event level
opens a xterm for control level, and enter configuration information (hex):

4a2, but see the list of keys

when the calibration is done, exit by typing 0
close the xterm when done

Warning: The whole process takes about 1 minute. It it takes more than 1.5 minutes: start to worry. If it takes more than 2 minutes, Ctrl C all the windows, reboot the ROMs and restart the calibraiton.

Validate Calibration

Copies the output of the calibration in new subdirectory

/nfs/bbr-nfs03/detector/dch/DchProto2/calibration/proXXX

where XXX=calibration number

Processes the calibration data just collected correcting them for test bench measurements, comparing them with reference values, etc.

Opens a gv window on bbr-falco so the shifter can take a look at the quality of the data taken.

Page 1: in red: histogram of the quantities measured in the current calibration in cyan: reference histogram from a previous (good) calibration
Page 2: distribution of last measurement - reference measurement for Noise Floor, Pedestal, T0, Analog Gain. The comparison is done channel by channel.

Additional Information

When the calibration is finished

Close the Xyplex window . Just click the "X" in the upper right corner of the window frame, or pull down the window frame menu from the upper left corner and select close. The DAQ system captures all of the ROM output to log files. The Xyplex connections intercept that output before it can be logged, making debugging difficult.

How to decide if it's a good calibration?

compare our ps file with a recent calibration (use it as a reference): $BFROOT/detector/dch/DchProto2/calibration/pro43/calibration.ps
at the moment anywhere from 6 to 20 channels may fail validation. If more than 25 channels fails the validation, do not validate the calibration.

What is the last validated calibration (used in the next data taking run)?

Take a look at the symbolic link in /nfs/bbr-srv02/dataflow/constants/dch/calibration/current/protocalib.out

How to check the list of bad channels:

If bad channels were found in the calibration, their identifier and the problem will be dumped on the screen. The same info is also saved in the file: $BFROOT/detector/dch/DchProto2/calibration/proXXX/calibration.txt

What to do when there is a problem

Check the Current Problem page to see if it is a known problem.
Document EXACTLY what happened in the DCH Online logbook
Send G.Sciolla an email if you think there is a problem either in the code or with the electronics.