Difference between revisions of "MySQL database"

From Hall A Wiki
Jump to: navigation, search
Line 3: Line 3:
 
# Call command ./setAnalysisInfo.pl to run this script
 
# Call command ./setAnalysisInfo.pl to run this script
 
#* You will see this:
 
#* You will see this:
= Connection successful: handle: DBI::db=HASH(0x8ffdd34)
+
Connection successful: handle: DBI::db=HASH(0x8ffdd34)
  
=Need some run numbers, dude!
+
Need some run numbers, dude!
  
=Usage:
+
Usage:
==      setAnalysisInfo.pl [OPTION]
+
      setAnalysisInfo.pl [OPTION]
  
=Command-line options:
+
Command-line options:
==  -r, --runnum [LOW NUMBER]-[HIGH NUMBER]
+
  -r, --runnum [LOW NUMBER]-[HIGH NUMBER]
==      Specify the range of runnumbers to modify.  One number will work
+
      Specify the range of runnumbers to modify.  One number will work
==      for single run modifications.
+
      for single run modifications.
  
==  -u, --username [USERNAME]
+
  -u, --username [USERNAME]
==      Specify the name of the person making the modification
+
      Specify the name of the person making the modification
  
==  -t, --type [RUNTYPE]
+
  -t, --type [RUNTYPE]
==      Specify the type of run (calibration, scan, junk)
+
      Specify the type of run (calibration, scan, junk)
  
==  -k, --kinematic [KINEMATIC]
+
  -k, --kinematic [KINEMATIC]
==      Specify the kinematic name.
+
      Specify the kinematic name.
  
==  -p, --production [0,1]
+
  -p, --production [0,1]
==      Specify if the run is production (1) or not (0)
+
      Specify if the run is production (1) or not (0)
  
==  -b, --beampol [BEAM POLARIZATION]
+
  -b, --beampol [BEAM POLARIZATION]
==      Specify the beam polarization
+
      Specify the beam polarization
  
==  -h, --heTargpol [TARGET POLARIZATION]
+
  -h, --heTargpol [TARGET POLARIZATION]
==      Specify the target polarization
+
      Specify the target polarization
  
==  -c, --comment "[COMMENT]"
+
  -c, --comment "[COMMENT]"
==      Add a comment.  For best results, put the entire comment in  
+
      Add a comment.  For best results, put the entire comment in  
==      quotation marks.
+
      quotation marks.
  
==  -v, --verbose
+
  -v, --verbose
==      Be verbose.
+
      Be verbose.
  
 
* If a High Voltage Alarm sounds, turn the channel off and then back on
 
* If a High Voltage Alarm sounds, turn the channel off and then back on

Revision as of 03:01, 29 April 2009

Insert analysis information into MySQL database of QuasiFamily

  1. Find the script setAnalysisInfo.pl in directory: /adaqfs/home/adaq/e05102/scripts
  2. Call command ./setAnalysisInfo.pl to run this script
    • You will see this:

Connection successful: handle: DBI::db=HASH(0x8ffdd34)

Need some run numbers, dude!

Usage:

      setAnalysisInfo.pl [OPTION]

Command-line options:

  -r, --runnum [LOW NUMBER]-[HIGH NUMBER]
      Specify the range of runnumbers to modify.  One number will work
      for single run modifications.
  -u, --username [USERNAME]
      Specify the name of the person making the modification
  -t, --type [RUNTYPE]
      Specify the type of run (calibration, scan, junk)
  -k, --kinematic [KINEMATIC]
      Specify the kinematic name.
  -p, --production [0,1]
      Specify if the run is production (1) or not (0)
  -b, --beampol [BEAM POLARIZATION]
      Specify the beam polarization
  -h, --heTargpol [TARGET POLARIZATION]
      Specify the target polarization
  -c, --comment "[COMMENT]"
      Add a comment.  For best results, put the entire comment in 
      quotation marks.
  -v, --verbose
      Be verbose.
  • If a High Voltage Alarm sounds, turn the channel off and then back on
Run the RHRS CODA with the setting "RightHrs"
  1. Analyzing the RHRS using do_all(run#) will analyze the neutron detector data
  2. To view just the HAND data once replayed, use the command show_all(run#)
    • It's the window where every group of histograms has labels that start with "ND"
  3. In general,
    • the ADCs should look like this:ADCs.png
    • and the TDCs should look this: TDCs.png
    • If they don't, make a HAlog entry about it