Check-list for starting a production pass

1. Make sure that all the code is in CVS. make-release.pl can only do CVS snap-shots.
   • Update BatchProc/grid scripts if you want to run a new pass, e.g. 4g instead of 4f.
2. Run make-release.pl from a clean release -- it will import all packages
   • Best way is to create a temporary release directory
     

     newrel -t development tmpRel
     cd tmpRel
     setrel
     make-release.pl # -no-build option will save you time. It's not on by default

3. Build new release, preferably on the architecture of farm nodes
   • The farm nodes are all 64 bit systems. e907ana8 is 32 bit. So far this is not causing any problems.
     

     ssh mippsoft@e907ana1
     mipp-import-rel -rel RYY.MM.DD
     cd releases/RYY.MM.DD
     setrel RYY.MM.DD        # This is VERY important to name the release
     cd $SRT_PUBLIC_CONTEXT  # Double-check that you are in the right directory
     mipp-build-rel -rel RYY.MM.DD  
     

4. Create new table to track pass results. Example for pass2:
   

   psql batchproc -U mippdbwrite
   alter table pass2 rename to pass2r3_2;
   create table pass2 () inherits (bp);
   grant select on pass2 to public;

5. Run make-db-schema.
   New schema name will be rYY_MM_DD
   
6. Create new directory structure in enstore. It has to be writable. Example:
   

   ssh e907ana2
   cd /pnfs/e907/reco3/FNAL
   mkdir pass2
   cd pass2
   enstore pnfs --file-family=mipphisto
   mkdir 1{1,2,3,4,5,6,7}
   chmod g+w . 1?

7. Once release has finished building, create new grid release:
   

   ssh e907ana5   # Whatever machine where you have access to RYY.MM.DD built in step 3
   setrel RYY.MM.DD
   make-grid-rel
   cp RYY.MM.DD_Linux2.X.tar.gz ~mippsoft/web_releases
   

   The link web_releases should point to /afs/fnal.gov/files/expwww/ppd/physical_experiments/e907/html/OfflineSoftware/releases/
   
8. Create new log file directory on the computer where you will be submitting jobs