Upgrading the Beam Test Pipeline

Use this procedure when upgrading to a newer version of the Beam Test Pipeline.

Note: Currently, Beam Test Pipeline code resides at:

/afs/slac.stanford.edu/g/glast/ground/PipelineConfig/BeamTest-tasks/beamtestPipeline

There you will find two symbolic links labeled:

• Current - which points to the currently installed version of the code

• test - which points to the test pipeline version

Procedure

1. From CVS, checkout the HEAD build into a new directory; be sure to increment the version number when you create a new tag.

Make your edits in the new version.

2. In addition to any edits you may make, you will also have to change the following:

• Versions in the svacPlSetup.cshrc file (in the setup subdirectory)
  • BeamtestRelease
  • Pipeline
  • beamtest06
  • BeamTestTuple
  • Em2Version (Gleam; in the digitization section)
  • sasLocation (where the BeamtestRelease is installed; at the time this was written, it was located in:

/afs/slac.stanford.edu/g/glast/ground/releases/volume10/BeamtestRelease-vXrYpZ

Note: There are two versions maintained here; normally, you will want to select the oldest version.

Important: When any change has been made to the svacPLSetup.cshrc file, the genXml.pl script must be run as detailed in step 3, below.

• Uncomment the line containing "setenv elogTestOnly1" to disable updating of ElogBook while testing.

  Note: This line is uncommented for testing purposes only, and must be commented out before cutting over to (prod)uction.

2. Define an environment variable named beamtestPLRoot that points to the actual version you are updating. For example:

/afs/slac.stanford.edu/g/glast/ground/PipelineConfig/BeamTest-tasks/beamtestPipeline/v1r030603p7

3. Run $beamtestPlRoot/*/genXml.pl for each of the subdirectories listed below.

Tip: This perl script creates several xml files in the current directory, and the beamtestPlRoot directory has proven to be a good choice in which to run it.)

• configReport
• digitization
• digiReport
• recon
• eLogUpdate
• reconReport
• svacTuple
• tkrReport

4. Upload the xml files created above to the test pipeline using the web interface at:

   http://glast-ground.slac.stanford.edu/Pipeline/

Caution! Be sure to select Test in the upper right corner before uploading the configuration files.

5. At the following location, redefine the symbolic link "test" to point to the one you are updating:

/afs/slac.stanford.edu/g/glast/ground/PipelineConfig/BeamTest-tasks/beamtestPipeline

6. Test on an existing run.

For example:

$beamtestPlRoot/online/BeamTestLaunch.pl 700001121

Note: The pipeline will generated the corresponding files, but will not update the links on the database.

7. Look at the test pipeline and verify that everything is correct.

Update the (prod)uction pipeline:

Caution: Before proceeding, be sure to check in with the Change Control Board and email the beamlist. Then,wait for the pipeline to empty. (This could take hours.)

8. To turn off the pipeline, create the "halted" sentinel file in:

   /afs/slac.stanford.edu/g/glast/ground/PipelineConfig/BeamTest-tasks

using the following commands:

echo Manual disable by `whoami` at `date` > halted
chmod g+w halted

9. Upload the xml files created in step 3 above to the (prod)uction pipeline using the web interface at:

   http://glast-ground.slac.stanford.edu/Pipeline/

Be sure to select prod in the upper right corner before uploading the configuration files.

10. In the svacPlSetup.cshrc file (in the setup subdirectory), comment out the line containing "setenv elogTestOnly1" to enable updating of ElogBook.

11. At the following location, redefine the symbolic link "current" to point to the one you are updating:

/afs/slac.stanford.edu/g/glast/ground/PipelineConfig/BeamTest-tasks/beamtestPipeline

12. Remove the "halted" sentinel file in:

    /afs/slac.stanford.edu/g/glast/ground/PipelineConfig/BeamTest-tasks

End of procedure.

13. To launch a new run, enter:

$beamtestP1Root/online/BeamTestLaunch.pl $run

Note: If you have to reprocess a run, delete links inserted by a previous run by first entering:

$beamtestPlRoot/lib/deleteLinks.sch $run

then launch the run you are reprocessing.

Also See:

• Beam Test Pipeline Application and Processing Chain