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

Compare with Current View Page History

« Previous Version 12 Next »

Select a current version of L1Proc

  • The PROD versions of the L1Proc xml configuration files can be found at this location:
    /afs/slac.stanford.edu/g/glast/ground/PipelineConfig/Level1/X.Y/xml/L1Proc-X.Y.xml
    where X.Y is the version number.
  • It is recommended to select a recent version of L1Proc (the current PROD version can be found via the CCB page).

Upload the L1Proc xml to TEST

  • /afs/slac.stanford.edu/g/glast/ground/bin/pipeline load -m TEST /afs/slac.stanford.edu/g/glast/ground/PipelineConfig/Level1/X.Y/xml/L1Proc-X.Y.xml
    where X.Y is the version number.
  • Make absolutely sure that the xml configuration is being uploaded to TEST (the default goes to PROD and we definitely don't want that).
  • In case we get the following message: java.sql.SQLException: ORA-20001: A Task exists with specified name, version numbers, and parent,
    it might be necessary to delete the current task version from the TEST pipeline (this should never be a problem because it's TEST).

Prepare a set of input data and install it into a specific location

  • A test file containing one single chunk can be downloaded from here.
  • Install, unzip, un-tar the file in a known location. This operation must be done as glastraw and the containing folder must have write permissions for glastraw.
  • Example location: /nfs/farm/g/glast/u28/scratchSpace/120225001/
  • Warning: the input chunks will be deleted at the beginning of the job. If you need to roll-back, you will need to re-download them.

Create the L1Proc stream

  • This can either be done from command-line or from the web interface. Example from command-line:
    /afs/slac.stanford.edu/g/glast/ground/bin/pipeline createStream -m TEST --stream 120225001 --define "DOWNLINK_ID=120225001, DOWNLINK_RAWDIR=/nfs/farm/g/glast/u28/scratchSpace/120225001" L1Proc
  • The stream progress can be monitored through the TEST pipeline interface

Cleanup warnings

  • Because the test input delivery is a single file and not a complete run, cleanup will be suppressed.
  • This may cause failures in the checkRun task (still working on that).
  • No labels