You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 21 Next »

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. 
      1. If you are using ssh, you will need to have X11 forwarding enabled (the -X or -Y option if not enabled by default).
      2. Using the necessary GUI via X11 can be very slow. SLAC has a remote desktop service called FastX that should work better.  It has web and desktop clients. See their web page for setup and usage instructions. 
      3. The GUI does not run on fermilnx01 or fermilnx02.  It will fail with a message like: error while loading shared libraries.  If you get this, try running on a different machine. The rhel6-64 pool machines seem to work fine.
    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.
      3. You may also want to note the start time of the next run after the SAA.  You will want to send that information to the data monitors list (see below) when you inform them of 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 sessions 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 the same as the user name but with an "8" in place of the second "a".  If you click "Save", then the connection information will be stored as a profile that you can load next time from the box on the left instead of typing everything in.
  10. Click "OK".
  11. 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.
  12. Click on the "More" button at the bottom of the upper box.  This will add another drop down menu row.
  13. Select "flavor".
  14. In the right hand box (that may say "vanilla"), type in "L1current".  There is no menu choice for it.
  15. Click on the "More" button again.
  16. Select "calib_type" (calibration type).
  17. In the right hand box, select the type, e.g., 'TKR_DeadChan'.
    1. If you don't know the type that corresponds to the file you have, you can pick an option from the menu and hit "Send" to see what the current/previous calibration files are used for that type. 

    2. For easier reference, here's a table with some example files and the calib_type for them.

      file name examplecalib_type
      fit_gcrhists_lkhd_568m_572m_bigsum.gcr_asym_hist.xmlCAL_Asym
      fit_proton_calib_568m_572m_bigsum.calMPD.xmlCAL_MevPerDac
      pedavr_568m_572m.xml

      CAL_Ped

      LAT_BadStrips_45.xmlTKR_DeadChan
  18. Then click "Send".
  19. You will get something that looks like this:
  20. Add the new calibration file.
    1. Select the last row in the bottom box.
    2. Right-click and select "Copy Latest" from the menu.
    3. In the pop-up box that comes up, change the "vstart" time to the middle of the SAA passage chosen earlier.
    4. Change "data_ident" field to the file name for the XML file.
    5. Click "Send" and the pop-up will disappear.
    6. 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. Do this for each of the calibration files that need to be updated.  You are basically done.
  23. Send an email to whoever created the calibration files and cc the data monitor list (datamonlist@glast2.stanford.edu) to let them know when the calibration should take effect.
    1. Get the ID of the next run by using XTime or similar tool to convert start time of the next run after the SAA pass into MET.
    2. Include the start time and first run in the email, e.g., "vstart is 2018-09-28 03:43. First run should be 559799706."
  24. Later check that the new calibration has been used.
    1. Go to data processing page and click on the L1Proc bar for the run after the change should have happened.
    2. Go to the "Substreams" table in the middle of the page and click on one of the streams for the "doChunk" task.
    3. Go down to the "Substreams" table and click on any one of the "doCrumb" streams.
    4. Click on the log file link for the "recon" process.
    5. Search in the log for appropriate XML file(s).

 

 

 

 

 

 

 

  • No labels