Difference between revisions of "SRC/CT Good Run Selection"

From GlueXWiki
Jump to: navigation, search
Line 1: Line 1:
 +
[https://halldweb.jlab.org/wiki/index.php/SRC/CT_Analysis_Page Back to previous page]
 
=RCDB=
 
=RCDB=
 
*The run condition parameters are stored in the Run Conditions DataBase (RCDB). It is part of the Hall D software package.
 
*The run condition parameters are stored in the Run Conditions DataBase (RCDB). It is part of the Hall D software package.

Revision as of 12:37, 21 September 2022

Back to previous page

RCDB

  • The run condition parameters are stored in the Run Conditions DataBase (RCDB). It is part of the Hall D software package.
  • Connection to the database
    • Main MySQL database: mysql://rcdb@hallddb/rcdb
    • Local SQLite database: sqlite:///path.to.file.db
  • Different interfaces we can use.
    • Python interface
import rcdb
 
db = rcdb.RCDBProvider("mysql://rcdb@hallddb/rcdb")
good_runs = db.select_runs(RCDB_QUERY, MINRUN, MAXRUN)
 
#Get the list of selected runs
for run in good_runs:
    print(run.number)
 
#Check whether one specific run is in the selected list
run = db.get_run(NUMBER)
if run not in good_runs:
    continue
    • Command line interface
# Connected to the main RCDB by default
rcnd  # list all the conditions
rcnd NUMBER  # list all the condition values of one specific run
rcnd NUMBER CONDITION # return the value of some condition of one specific run
    • Web interface
      • Link to the website
      • The runs can be selected with RCDB_QUERY, MINRUN and MAXRUN. But the @is_src_production alias can not be used for now. The full query needs to be filled in (See the monitoring runs section below).
      • The "Conditions" tab lists all the conditions available in RCDB.
    • Job submission
      • Run python launch script with the command 'python launch.py MINRUN MAXRUN'
      • Specify the RCDB_QUERY in the configuration file (.config)
  • More detailed documentation can be found here: wiki, GitHub
  • Contact Sean Dobbs if the information needs to be edited in RCDB.

All runs

  • 90001 to 90662 in Run Period 2021-11
  • Liquid deuterium: 90207 to 90253, 90548 to 90602
  • Liquid He-4: 90001 to 90206, 90603 to 90662
  • Multi-foil C-12: 90254 to 90547

Monitoring runs

  • Runs that should be included in the monitoring launches. These runs are calibrated. Relatively loose selection is used so that some test runs and junk runs are also included.
  • RCDB query: "@is_src_production" (alias of "daq_run=='PHYSICS_SRC' and beam_current > 2. and event_count > 5000000 and solenoid_current > 100 and collimator_diameter != 'Blocking'")
  • List of monitoring runs

Approved runs

  • Runs that should be included in the reconstruction and analysis launches. Approved to be used in analysis after checking the calibration and data quality
  • RCDB query: "@is_src_production and @status_approved"
  • List of approved runs
  • List of excluded runs

More selections

  • Run conditions
    • Raw mode: "daq_config=='FCAL_BCAL_PS_SRC_m10.conf'"
    • Compton trigger: "daq_config=='CCAL_FCAL_PS_m9.conf'"
    • Empty target: "target_type == 'EMPTY & Ready'" (all carbon runs and 90602 need to be edited)
    • Low intensity: "daq_config == 'FCAL_BCAL_PS_SRC_m9.conf' and beam_on_current < 55.0" (90246 needs to be edited)
    • Production: "daq_config == 'FCAL_BCAL_PS_SRC_m9.conf' and beam_on_current > 55.0 and target_type != 'EMPTY & Ready'"
  • Photon polarization
    • Diamond: "polarization_angle > 0"
      • 0/90 PARA: "polarization_angle == 0.0"
      • 0/90 PERP: "polarization_angle == 90.0"
      • 45/135 PARA: "polarization_angle == 135.0"
      • 45/135 PERP: "polarization_angle == 45.0"
    • Amorphous: "polarization_angle == -1.0" (90140 90481 90615 90616 need to be edited)