MAINTAINING AND UPDATING CCON FILES A ROUGH GUIDE Mary Bishai, MAR 26TH 1997 Naresh Menon Dec 18th 1997 (This file is lns111:/ccon/bank/instructions.txt) I.INTRODUCTION -------------- There are 11 constants files : The standard set is (zfiles format) : cc.zfx, cd.zfx, cg.zfx, de.zfx, mu.zfx sv.zfx, tf.zfx, tr.zfx The beam position and crossing angle (direct-access) : runinf.dac and xang.dac And the crate constants database (direct-access) : C3L.FIL There are 3 different versions of the standard set for different ranges of the CLEO datasets (see /cleo/doc/dataset.summary) Version Platform Work Area Comment ------- -------- --------- ------- 1) ONLINE LNSON1:/onl/ccon /onl/ccon/send (4sH->) /onl/ccon/send/update LNSON1:/onl/ccon/cal --- Temp. calib. files updated by ECAL. LNS309:[CCON.PASS1]C3L.FIL Crate constants database 2) CLEO II.5 DECS and ALPHAS: LNS111:/ccon/bank (4sH->) /ccon/ccon. LNS717:/ccon/bank 3) CLEO II RECOMPRESS ALPHAs only: /ccon/recon/kumac (3s1-4sG) /ccon/recon Note that the ONLINE and CLEO II.5 sets should always be identical unless a temporary change is being tested before propagating to /ccon/ccon. Passwords: ********* To be able to remote login from your personal account without typing in the CCON passwords every time add your workstation and login ID to the .rhosts file in the home directory of the respective CCON account on each platform. Follow the syntax already entered in the .rhosts file. Notation: ********* xxxxx = run number yy = devname (e.g. cc, dr, ms, mu, pt, sv, tf, vd or all) zz = constants file name (e.g. cc, cd, mu, sv or tf) II.MAINTAINING THE ONLINE CONSTANTS (BIGCALS) ------------------------------------------ To install a BIGCAL xxxxx: 1) Log into LNSON1 as CLEO21 type: lnson1% cd $CALCON/../send/update lnson1% update yy xxxxx [nocopy] (where xxxxx is the calibration number) use the option nocopy if you are doing multiple updates at the same time. You will be prompted for a begin run number and end run number. The default is begin run = xxxxx and end run = 99999. Just type enter at the prompt to select the defaults other wise enter the run numbers you wish. Check the log file to see installation was OK. It may be necessary sometimes to install by hand if zfiles won't let you overwrite the exisiting set. In that case use the kumacs in $CALCON/../send/update as a guide and run zfiles interactively. 2) Copy the file to lns101,lns717 and PASS1 lnson1% distribute zz 3) Now update the crate constants database C3L.FIL on LNSON1: lnson1% cd $CALCON/../send Copy the file over from LNS309 lnson1% c3imp Update the file: lnson1% c3update yy xxxxx Check that there are no major changes in constants by running c3dump and doing a diff between the old and new files, runc3dump is a script that does that lnson1% runc3dump Copy the file to LNS62 lnson1% c3exp Login to LNS62 as CCON and fix the record lenght: $ c3fix Then finally move it to LNS307 to be used by the next run: $ c3move SPECIAL CASES: ------------- For cc updates do 4) before 1), 2) and 3). For sv, first cp /onl/ccon/cal/calsv.zfx to ./temp area. Then make a soft link to /cdat/tem/jae/ccon/sv.zfx and call that calsv.zfx. The begin run number has to be the run currently in progress (or the very next one). After the crate constants have been generated and copied to lns309, go back and remove the softllink. Move the calsv.zfx file from the temp area to the /onl/ccon/cal/ area. III. MAINTAINING THE CLEO II.5 CONSTANTS ---------------------------------------- CLEO II.5 constants are automatically updated whenever a BIGCAL is installed as explained above. The PASS2 constants are still in a state of flux but here is an outline: 1) Copy the file to be updated from /ccon/ccon to the work area associated with that file and update by running the scripts or Zfiles MACROS outlined below: File Work Area Key scripts or programs to run ---- --------- ------------------------------ cc.zfx lns111: /ccon/bank/cc install_cc_.kumac, install_og_.kumac REIHLE submits the above scripts with his request. Copy them to the work area and run zfiles interactivly: % zfiles zfiles> exec install_cc_ % zfiles zfiles> exec install_og_ cd.zfx lns111: /ccon/bank/cd cdtocd This script copies the current PASS2 constants from (given to you by PIH), to for the run range -. As an intermediate step it dumps them out to ASCII files. This is the proposed plan that PIH and I agreed on, we haven't tried it yet. cg.zfx ?? No plan yet, but if an ASCII file is submitted just use /ccon/bin/astozf script. The script will prompt you for info. de.zfx lns111: /ccon/bank/de astozf Wire-to-wire and run-to-run constants are installed directly into the current de.zfx by HINSON. All CCON does is install the file in the official areas. The PASS2 constants from JROY are submitted as an ASCII file that should be installed in entity= CLEO/CD/DEDR/MAP3_CORR mu.zfx lns111: /ccon/bank/mu update_mu.kumac When MUDET submits a new request modify the above kumac and run interactive zfiles: % zfiles zfiles> exec update_mu sv.zfx lns111: /ccon/bank/sv insert_convfac.kumac So far the only entitiy I know updated regularly offline is CLEO/SV/CALIB/CONV_FAC copy the file conv_fact.submit from where HILL tells you it is. Modify the run numbers in the above kumac and run interactive zfiles: % zfiles zfiles> exec insert_convfac tf.zfx lns111: /ccon/bank/tf updatetf GODANG should submit a file called input_.txt that should be copied to the work area before running the above scripts. The philosophy is input.txt will contain a list of directories and run ranges that will be converted by a perl script create_tf_kumac.perl to kumacs that will then be run in zfiles (in the updatetf script). The bunch constants must first be put in correct ASCII format. Modify the fixbunch.scr according to the directory structure in input.txt and have ROMULUS run it in his area. The 4sk directory contains the 4sk constants. The script runs in this area and works fine. For the 4sK dataset I had to fix the formats of ALL the ASCII files 1st. Jorge Rodriguez has fixed the TOF programs so that should be unecessary for any upcoming installs. tr.zfx ?? These are MC trigger constants and I have no idea what I am going to do for CLEO II.5 but probably the same philosophy as tf. runinf lns717: /ccon/bank updateinf xang lns717: /ccon/bank updatexang ------------------------------------------------------------------------------- 2) After the files are updated in the work areas, distribute them to the different platforms by typing: % distribute zz Make sure the zz.zfx file is in the current directory before you run distribute. NOTE: The runinf and xang files don't need to be distributed; the update scripts take care of that automatically. IV. MAINTAINING THE CLEO II RECOMPRESS CONSTANTS ------------------------------------------------ 1) File Work Area Key scripts, kumacs, programs to run ---- --------- ------------------------------------ cc.zfx lns111: /ccon/recon/ kumac/cc install_cc_.kumac, install_og_.kumac i) Copy /ccon/recon/cc.zfx to the work area ii) REIHLE submits the above scripts with his request. Copy them to the work area and run zfiles interactively: % zfiles zfiles> exec install_cc_ % zfiles zfiles> exec install_og_ cd.zfx lns111: and /ccon/recon/ cg.zfx kumac/cd_cg updatecd RENE submits an input.txt. file. Copy this file to the work area and run the updatecd script. : % updatecd de.zfx lns111: /ccon/recon/ astozf kumac/de Wire-to-wire and run-to-run constants are installed directly into the current de.zfx by HINSON. All CCON does is install the file in the official areas. The PASS2 constants from JROY are submitted as an ASCII file that should be installed in entity= CLEO/CD/DEDR/MAP3_COR Copy /ccon/recon/de.zfx file to the work area and run the generic script astozf to copy an ASCII file into a given entity in a given file: % astozf mu.zfx ?? We are using the old constants for recompress there should be no need to change this file tf.zfx lns111: /ccon/recon/ kumac/tf tftotf GODANG submits on the VAX for a run-range - . Ftp the zfile from the VAX as binary. should be a copy of the current /ccon/recon/tf.zfx in the work area. -------------------------------------------------------------------------- 2) After the files are updated in the work areas, first back up the /ccon/recon/zz.zfx % mv /ccon/recon/zz.zfx /ccon/recon/oldzf/zz_mmddyy.zfx where mmddyy = month day year Now install the file from the current directory to /ccon/recon % mv zz.zfx /ccon/recon V. DOCUMENTATION AND LOGFILES ------------------------------ An online logfile is maintained in lns717:/home/ccon/public_html/change.history. This file must be maintained as well email in lns717 (PINE) sent to 'maillst'. The month of october 96 is missing in /home/ds/ccon/public_html/change.history but all changes were logged in log book 11. This is the procudure to use: 1) logon to LNS717 as CCON: lns717|/home/ccon> pine type 'I' to enter the Index Folder type 'C' to compose mail at the To prompt type 'maillst' carriage return to the Suject prompt and enter the appropriate subject. carriage return to the 'Message Text' region and type '^T' this prompts you to 'File to insert from home directory: ' enter template edit this file within pine. type '^X' to send the mail. wait a few minutes untill you get a copy of the mail in the index folder. Save it in the folder 'arch' (you will be prompted if you want to create the folder, answer yes) quit pine. lns717|/home/ccon> marchive this will archive the mail on the web. VI. SOME USEFUL GENERAL PURPOSE SCRIPTS --------------------------------------- There are a set of some useful general purpose scripts in /home/ccon/bin on the alphas (some are soft links on the DECs) that can be used for extra checking and special installations: Script Purpose ------ ------- astozf Script to update entities in xx.zfx constants files from ASCII files for a given run range c3dump Dump the contents of C3L.FIL (alpha executable) cleanup Clean up sets of files with shared names keeping the 3 most recent create_kumac.perl perl script used by zftozf to make kumacs distribute Distributes *.zfx files in current directory to other platforms extendzf Extend the range of a run number in a zfiles entity getlistvalid.perl perl script used by validzf. Makes kumacs link_ccon Create link files to CLEO constant files i.e. to redefine alternative constant files listzf List contents of a whole zfx file in an ASCII file. newzf Create a new ZF t0zf Program to install TF T0's in tf.zfx (alpha executable only) validzf Script to list valid constants in a given run range zftozf Script to extract constants from an entity in one zfile and install into another ============================================================