Updating L1 calibrations

Sometimes the instrument specialists give us new calibrations. Usually just a dead strip list for TKR, 3 (asym, MeV/DAC, peds) at a time for CAL. They need to be put in a standard place, registered in the calibration DB, and set active. This requires picking a time when validity switches from the previous set to the new one. We want this to happen between runs. The gaps between non-SAA runs are short, and CALDB doesn't do leap seconds, so I put the transitions near the middle of an SAA passage - the first one after the last run that we have data for.

Step-by-step guide

1. Make sure your environment is setup correctly:  
   1. Log into a SLAC machine.  You will need to have X11 forwarding enabled (the -X or -Y option if not enabled by default).
      
   2. If one is not already sourced in your .bashrc or .cshrc then:
      
      1. bash: source /afs/slac.stanford.edu/g/glast/ground/scripts/group.sh
      2. (t)csh: source /afs/slac.stanford.edu/g/glast/ground/scripts/group.cshrc
   3. This will set environment variables like $GLASTROOT and the path to the GUI you will use below.
   4. Make sure that you have write permissions to the $LATCalibRoot directory.
      1. If not, ask Tom Glanzman .
2. Copy files to the "normal" place (if the instrument people haven't already):
   1. TKR: $LATCalibRoot/TKR
   2. CAL: $LATCalibRoot/CAL/p7repro
3. Figure out the transition time:
   1. Go to the data processing page.
      
      1. Find the most recent run. It will be at the top, unless deliveries have arrived out of order.
      2. Click on the run number.
      3. Note the start time.
   2. Go to the mission planning timeline
      1. Find the first SAA passage that is still in the future processing wise.
      2. Pick a time that is in the middle of the SAA passage. That is when we will start the new calibration.
4. Start the rdbGUI.
5. Go to the File menu and select 'Open DB Schema'.
6. Navigate to the directory /afs/slac/g/glast/applications/dbSchemas/calib
   1. You can paste this into the File Name box.
   2. You can bookmark this location for future session by clicking on the flag icon.
7. Open the calib.xml file and click on metadata_v2r1 under the Tables box.
8. Under the Session menu, click on Open connection.  This will open a pop up box.
9. Fill in the box like the image below.   The profile name and profile description boxes can be anything.  The password is "calibr8tor".
   
10. Once connected, click on the drop down where is says "ser_no" (serial number) and set it to "instrument".  It will fill in "LAT" in the box on the right.
11. Click on the "More" button at the bottom of the upper box.  This will add another drop down menu row.
12. Select "flavor".
13. In the right hand box (that may say "vanilla"), type in "L1current".
14. Click on the "More" button again.
15. Select "calib_type" (calibration type).
16. In the right hand box, select the type, e.g., 'TKR_DeadChan'.
17. Then click "Send".
18. You will get something that looks like this:
    
19. Select the last row in the bottom box.
20. Add in the new calibration file.
    
    1. Right-click and select "Copy Latest" from the menu.
    2. In the pop-up box that comes up, change the time to the middle of the SAA passage chosen earlier.
    3. Change "data_ident" field to the file name for the XML file.
    4. Click "Send" and the pop-up will disappear.
       
    5. Click the "Send" button on the right hand middle of the box.
21. There should be a new last line.  Scroll over and check that the "vstart" time is correct and that the "vend" field of the previous line is the same.
    
22. Later check that the new calibration has been used.
    
    1. Go to data processing page and pick a run after the change should take effect.
    2. Go to the "Substreams" in the middle of the page.
    3. Click on one of the streams for the "doChunk" task.
    4. Go down to the "doCrumb" Substreams and click on any one.
    5. Click on the log file link for the "recon" process.
    6. Search in the log for appropriate XML file.
23. Send a message to the data monitor list to let them know when the calibration will took effect.