Difference between revisions of "MySQL database"

From Hall A Wiki
Jump to: navigation, search
(New page: == Insert analysis information into MySQL database of QuasiFamily == # Find the script setAnalysisInfo.pl in directory: /adaqfs/home/adaq/e05102/scripts # Call command ./setAnalysisInfo.pl...)
 
(Insert analysis information into MySQL database of QuasiFamily)
 
(9 intermediate revisions by the same user not shown)
Line 1: Line 1:
 
== Insert analysis information into MySQL database of QuasiFamily ==
 
== Insert analysis information into MySQL database of QuasiFamily ==
# Find the script setAnalysisInfo.pl in directory: /adaqfs/home/adaq/e05102/scripts
+
* Find the script setAnalysisInfo.pl in directory:  
# Call command ./setAnalysisInfo.pl to run this script
+
  /adaqfs/home/adaq/e05102/script
#* You will see this:
+
* Call command  
## Connection successful: handle: DBI::db=HASH(0x8ffdd34)
+
  ./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.
 +
*insert analysis information into database
 +
    Here is an example:
 +
    ./setAnalysisInfo.pl -r 20522 -u yawei -t test -p 0 -h 90.3% -c "test run"
  
##Need some run numbers, dude!
 
  
##Usage:
+
* You can find the QuasiFamily MySQL database here: [http://hallaweb.jlab.org/experiment/E05-102/db_QuasiFamily/index.php], check the analysis information which you insert
##      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"
+
# Analyzing the RHRS using do_all(run#) will analyze the neutron detector data
+
# 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"
+
# In general,
+
#* the ADCs should look like this:[[Image:ADCs.png]]
+
#* and the TDCs should look this: [[Image:TDCs.png]]
+
#* If they don't, make a [http://www.jlab.org/~adaq/halog/html/logdir.html HAlog] entry about it
+

Latest revision as of 03:34, 29 April 2009

Insert analysis information into MySQL database of QuasiFamily

  • Find the script setAnalysisInfo.pl in directory:
  /adaqfs/home/adaq/e05102/script
  • 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.
  • insert analysis information into database
   Here is an example:
   ./setAnalysisInfo.pl -r 20522 -u yawei -t test -p 0 -h 90.3% -c "test run"


  • You can find the QuasiFamily MySQL database here: [1], check the analysis information which you insert