Forward Angle Database To-Do List

Abstract

This is a dynamically updated list of database specific items that must be performed in support of the G0 forward angle analysis goals.

To-Do List

Color Key

• Headings
• Completed items
• High priority items
• Low priority items

List

• Server Setup
  • Move primary server off Hall C machine (cdaql3) - Done.
    1. Stop all slaves.
    2. Copy databases from cdaql3 to mary-pc and disable cdaql3 database accounts.
    3. Set up appropriate accounts on mary-pc.
    4. Move g0dbserver DNS alias from cdaql3 to mary-pc.
    5. "RESET MASTER" on mary-pc and record log file and position.
    6. Update slave server configuration for new primary.
    7. Restart slaves.
  • Set up offsite slave servers for institutions that desire one.
    • Grenoble - Done
    • Caltech - Done
• Tape Backup
  • Fix automated script to deal with file sizes in excess of 2 GB - Done.
  • Acquire larger hard drive for backup server.
  • Remove password info from backup script.
• "good_for" and "data_quality"
  • Create script to move "junk" designation to "data_quality". - Done
  • Eliminate "junk" option from "good_for" column of good_for GUI. - Done
  • Eliminate "junk" as an option in "good_for" field of "run" table
    • No alterations to current databases.
    • DB creation scripts altered to eliminate the "junk" option in new databases. - Done
    • Scripts and analyzer must be updated.
  • Create script to set the "spiky" bit in "data_quality". - Done
  • Update spiky info in current databases. Need a good list of spiky runs.
• Polarimetry
  • Create script to populate run, polarimetry, and polarized source tables with data from "summarygzero.dat" (Moller analysis output file). - Done
  • Run script and populate existing database.
  • Correct "sign_in_neg" info for polarimetry runs.
• Franco-American Electronics
  • Alter database generation scripts so that new databases will be able to handle FrAM results (add entries to detectors table with "make = fr" for NA octants). - Done
  • Update scripts and analyzers to deal with changes.
• PID Cuts
  • Alter or add to cuts defined in "particles" table.
    • Current cuts: proton, pion, background, inelastics, total
    • Desired new cuts: cut0, cut1, cut2, cut3
    • Proposal: cut0, pion, cut1, cut2, elastic1, elastic2, elastic3, cut3, total, background, inelastics, proton
      • Maintains backward compatibility: background, proton, and inelastic left empty in new databases.
      • Allows for up to three elastic cuts in one detector (looking ahead to detector 15).
  • Treatment of cut0 in "measurement" table
    • Problem: cut0 = sum of first seven detectors in Fr octants and database only designed to store results from individual detectors
    • Possible Solution:
      • Use "cut0" particle discussed above in "timebin_id".
      • Add "detector_id" of "detectors" table to use as a summed detectors surrogate (make="fr" and octant=detector=0).
• Linear Regression
  • Add "monitor_slopes" and "monitor_slope_types" tables to new databases.
• YO Differences
  • Add necessary tables/fields.