Stripping FMSS data files

To strip out of data files events selected from ntuples (or by RECON info), do following:

• 1 - selection by Ntuple list. Create by Paw list of events from ntuples (format "run event"), using sample kumac file 'nt_list.kumac' and function 'nt_list.for'. Kumac shows you example with 3 ntuples processing, function 'nt_list.for' is called in 'nt/loop' first with argument=1 for first ntuple to open list file, with argument=-1 after last ntuple to close list file, and with argument=0 for any intermediate ntuple. List will be written to the file which name you have to define in 'nt_list.for' as 'file_name'.
  
  
• 2 - selection by RECON info. Look into user routine 'event_from_recon.F' and create your own list of cuts in accord with example given there (name of list file should be given as env.variable $EVENT_LIST -- see 'event_from_recon.F'). Modify routine if you need something extra. Sample list see here.
  
  
• Process files from FMSS by script 'select_from_fmss'. This script is available from SELEX_TOOLS, so do 'setup -d selex_tools' first.

• To run it you have to prepare in your working directory following stuff:

  • 'soap.exe' executable. Script will generate by itself appropriate cmd-files for SOAP.

  • list of events to select, created at a first step

• After that run script 'select_from_fmss'. If you would invoke it without arguments, it will show you examples and usage information:

  • 1st argument - file with list of events to select

  • 2nd argument - FMSS directory with input data files (like 'mss:e781/pz001/out1'). To get this directory check out file $CALIBRATION_DIR/fmss/e781.mss with list of our files in FMSS

  • 3rd argument - header of file name before run number (like 'pz001_charm_run0'). Script supposes it will give UNIQUE access to each data file (or use more sophisticated 'egrep' syntax).

  • 4th argument (optional) - '-recon' for selection by recon info.

  • 5th argument (optional) - '-rep' for repairing data files by 'add_ufort'. Order of arguments 4,5 is not important.

  This script could be run both in interactive or Fbatch modes. You may use simple script like this one. Results you will see in your working directory as files

  • sel_*run-min_run-max* - resulting files with selected events produced from each 'HS*' FMSS tape

  • process_HS*.log - log files for each FMSS tape HS* processing (some FMSS messages suppressed there)

  • HS*/ - copy of temporary working directories - only for double check, could be deleted (contain *.soap_log files for each run, statistics, etc)

  • total_stat - file with total processing statistics

  • runs_selected - input list of runs to process for given selected events

Tip for Fbatch. You may watch current job results by following way. Look on 'fbatch_peek job-id' output and find line like "Job will be executed in Fbatch using /tmp/spacall.pid2178 directory for data files". After that you may use 'ls' command

ls /tmp/spacall.pid2178

to access info on a temporary disk - only during the job execution, only from the same host.