PRIMEX database, tables introduced:

1
PRIMEX database, tables introduced

• LMSref filter_pos default value 0 (
  unknown)
• Values from Sam are loaded (1, 2 or 3)
• crystal, glass pi0_gain runs 4829-5059 and
  5115-5330 are covered by two tables from carbon
  production runs
• crystal, glass mc_gain gains to be used for MC
• crystal, glass gk_mc_gain gain corrections to be
  used
• with gk MC, pi0 calibration was simulated with
  pi0 angular/energy spectrum close to observed
  one.
• PRIMEX database, tables updated
• hycal_timing offset, sigma
• PRIMEX database, tables to be introduced
• Timing offset and a,b coef. for en. Resolution
  adc status
• For channels which were not working well

2
Recn. program issues

• Hycal algorithm, can we switch to old one
• (in principle)
• Fastbus errors are counted and event is not
  rejected.
• Nhit max and min elements in cluster cuts are
  changed?
• Island algorithm could be introduced (we have
  clusters profiles)
• Coordinate correction is known from the MC
• Depth correction has to be increased by 1.1 as
  follows from detailed MC studies and data
  confirms with statement

3
Skim files

• Pi0 pass 2a
• Compton for double compton runs and for
  production runs