Run Periods

From GlueXWiki
Jump to: navigation, search

Summary information about current Run Periods

Name Run Range Date Range beam Data on Tape Total Events Notes
RunPeriod-2016-10 20000 – 9 Sept. 2016 – 12 GeV e-
RunPeriod-2016-02 10000 – 12109 28 Jan. 2016 – 8 Sept. 2016 570 TB 39.8B Commissioning, 12 GeV e-
RunPeriod-2015-12 3939 – 4807 1 Dec. 2015 – 28 Jan. 2016 9TB Commissioning, 12 GeV e-, Cosmics
RunPeriod-2015-06 3386 – 3938 29 May 2015 – 1 Dec 2015 53TB Cosmics
RunPeriod-2015-03 2607 – 3385 11 Mar. 2015 – 29 May 2015 74TB 1285M Commissioning, 5.5 GeV e-
RunPeriod-2015-01 2440 – 2606 6 Feb. 2015 – 11 Mar. 2015 11TB 225M Cosmics
RunPeriod-2014-10 630 – 2439 28 Oct. 2014 – 21 Dec. 2014 120TB 932M* Commissioning, 10 GeV e-

*The total size of the data from tape does not match that from the hd_runlog.sqlite DB (120TB vs. 50TB). The validity of the 932M events is therefore unclear.


Notes:

  • Data on tape is obtained from the Scicomp Tape Library Usage Web page. One needs to select the start and end dates, "Data Written" for the data type, and then "halld". Hover the mouse over the far right side of the resulting plot to obtain total tape usage for run period.
  • Number of events was obtained from the SQLite file: /gluonraid1/monitoring/hd_runlog.sqlite on the gluon cluster. A query such as the following is done:
    SELECT SUM(Nevents) FROM runs WHERE run>=2607 AND run<=3385 AND Nevents<1000000000;
    n.b. the Nevents<1000000000 clause is because there was one early run with Nevents=2^32, an obviously incorrect value.