Disk File Information

Both Vanderbilt and Colorado copy SKIM1 data files over to disks on fdei01 at Fermilab. Not all SKIM1 data can be guaranteed to be copied this way though a large percentage of files do make it across.

The SKIM1 data files reside on disk on FDEI01 for 18 hours before they get deleted. The files that make it to FDEI01 are copied to DD831 at Wideband and to FMSS. The DD831 files stay on disk for 12 hours while they stay on FMSS for 5 days before deletion. Note that FMSS has not been so reliable so not all files make it to FMSS sometimes.

In addition, Golden and Silver modes (Kpi,K2pi,K3pi, KKpi and pKpi) are subskimmed from Superstream 6 (SEZSKM with SEZDEE blocks) and put onto FMSS. (These do not have the SEZLST purged. These files are typically 80-90MB and already rather small for FMSS). These Golden and Silver mode files are expected to stay in FMSS permanently.

Given below are the directories where you can find the SKIM1 data files. Files names are [Run number].ss[super stream number], e.g. 10910.ss6

Superstream Description fdei01 disk dd831 disk FMSS area
1 Semileptonic and Dileptons /e831/stream/1 /dot/stage1/stream1 mss:e831/skim1/stream1
2 Global Vertex and Kshort /e831/stream/2 /dot/stage2/stream2 mss:e831/skim1/stream2
3 EM Neutrals and Phi Skims /e831/stream/3 /dot/stage3/stream3 mss:e831/skim1/stream3
4 Baryons and Prescale Triggers /e831/stream/4 /dot/stage4/stream4 mss:e831/skim1/stream4
5 Diffractive, leptonic and out-of-target /e831/stream/5 /dot/stage5/stream5 mss:e831/skim1/stream5
6 SEZDEE Skim with SEZDEE data block /e831/stream/6 /dot/stage6/stream6 mss:e831/skim1/stream6
G+S Modes Golden+Silver Modes with SEZDEE mss:e831/skim1/gmodes2/*
Stays for 18 hours 12 hours 5 days

Locking Disk Data Files

Disk data files on fdei01 and dd831 can be locked for up to three days if you need more time to process them. However locking too many files can cause the disk area to fill up so that no new data gets copied over from Colorado or Vanderbilt. Please use with care and remove your lockfiles after you are done with the data file.

The procedure for locking data files is simple. You basically you create a file for the data file you want locked (not deleted in usual time period). The data file can reside in either of two directories for a particular superstream and must have the name AnythingHere_11206.ss6.lock. (Where the data file name [11206.ss6] and "lock" must be in the name).

e.g. touch Milano_11688.ss6.lock

A utility to do and undo the lock is available on fnalu and the WB cluster:

The commands lock_skim and unlock_skim exist on dd831 and fnalu
Use them to lock and unlock SKIM1 data files.

lock_skim usage :-
 lock_skim 
 lock_skim 9096.ss3 9124.ss3 9126.ss3

unlock_skim usage :-
 unlock_skim 
 unlock_skim 9096.ss3 9124.ss3 9126.ss3
 unlock_skim 9096.ss3.lock 9126.ss3.lock

Unfortunately, wild cards are not allowed, but lists of file names are.

It automatically prepends your user name and puts the lock file
into the appropriate lockfile directory.

Unlock_skim looks in both lockfile directories

The lockfile directories are:

For fnalu:  /e831/stream/#
            ~e831tod/skim1/lockdirs/stream#

For WB:     /dot/stage#/stream# 
            /home/e831/lockdirs.

Last updated on 1/18/99

Send comments to: Harry Cheung