These are the major Run Periods used by oscillation analysis groups. There are a plethora of short special Run Periods for testing, systematic studies, etc. not noted here. See the Run Coordinator page for these.
It is intended that this table be used as a handy
reference, not a definitive source. If you are going to write code to
determine what runs are processed, please trace back the references and make
sure you understand what's going on. However, in general, it should be ok to
include more files than are necessary in an analysis, since events
recorded when the beam is off get cut time because variables like
good_beam are false. This is why, in
several places below, the start or end times are given deep within beam-off
||Main features||1st far subrun||Last far subrun||1st near subrun||Last near subrun||Start time (UTC)||End time (UTC)||Source/
||Dates: Alec; I used database for subrun numbers. Alec confirmed starting run.|
||Dates: Alec, saying of start, "From logbook, 6/11 13:55 CDT" & end, "From Cat, 8/13 15:30 CDT". I used database to find subruns.|
||Alec gave dates & subrun numbers. I confirmed with database.|
|III||2||He in beam pipe now & ff||39965/
||Alec gave starting date. I used database to find subruns. Not sure about 1st subrun: Alec's range includes 39965/10, but comment in log that goes with 39968/0 says that it's 1st with beam. Difference is only 1 subrun. End: Rashid.|
||Start: E-mail from Greg & doc-6953. End: doc-6953 & conversation with Justin. End time is by definition. End points aren't all at exactly the same time but are all safely inside beam-off period.|
||Start: E-mail by Greg & conversation with Justin.
Start time is by definition. Start points aren't all at the
same time, but are all safely inside beam-off period.
End time, FD run: E-mail/
||Start: E-mail from Rashid. Time is beginning of ND subrun given. End: E-mail from Chris; CRL.|
||Start: Phil's logbook entry (103304). I looked up the start times of the subruns in the database; the time given is the beginning of the far detector subrun, which started first. End: CVS commit from Justin, e-mail from Robert. Time is at end of near detector subrun. The beam actually went down at about 4:40am CST on 2011 Feb 24 (log entry 107109 by Hugh).|
||2011-07-11 23:00:00||Start: ND run is in a note from Art relayed by Justin. FD run was in an email from Andy referencing this data validation page. I got the time from the database. It is the start of the near detector subrun, which started first. End: Time and ND run from Rashid via e-mail. Time is a round number safely after the last spill. I found FD run in the database to be the one containing this time. Note: This is a very short Run Period, only ∼0.12×1020POT.|
||2011-07-30 02:44:00||2011-09-15 15:50:00||Start: Log entry 108881 by Mhair. End far+time: Log entry 110288 by Art. Time should be safely after end of beam. End near: Log entry 110284 by Cat shows near detector to be off when beam went down. This is the last run in the early morning of the same day, derived by me from the database.|
||2011-10-06 14:28:11||30 April 2012, "midnight"||Start: E-mail from Andy. Start time is for FD subrun, which is earlier than the start of the ND subrun. The first good beam is somewhere in the middle of that subrun. End: Log entry 113693 by Stephen. End of this Run Period is the end of "MINOS", where any further MINOS data is called "MINOS+".|
|XI||Medium energy||(future)||(future)||(future)||(future)||May 2013?||?||MINOS+ proposal for running in the NOνA era; This is speculative. Might shut MINOS down before this. Might call this Run I of MINOS+.|
Note −2: UTC = CST+6 = CDT+5.
Note −1: Send corrections/updates by e-mail to physics.umn.edu, user name strait.
Note 0 — philosophy:
0.0; Numbers: It's really nice for Run Period numbers to be integers so they can be easily looped through in code. This becomes more apparent the more Run Periods one has. We settled on integers after a tussle over whether the running starting in March 2010 should be called "IV FHC" or "V". We're stuck with the non-integer IpHE since too much had been written about it already.
0.1; Run Period boundaries: We change Run Period numbers at points where the beam spectrum changes (or, in theory, where the detector conditions change discontinuously). The idea is that you get a good fit by putting each Run Period into a separate histogram.
0.2; "Run": Please, the next time we design an experiment, let's not use the word "run" to mean two very different things. On this page, I attempt to be consistent in the pedantic use of "Run Period" or "Run" followed by a roman numeral to mean a many-day stretch with constant beam and detector conditions and "run" to mean the day-long stretches that our data files are organized into. However, off this page, "run" might mean either "Run Period" or "run" in my language. ("Subrun" always means the hour-long stretches within runs and has no confounding usage.)
Note 1: Some code uses the term Run IIpHE instead of Run IpHE. This is because this running was closer in time to Run II than to Run I (1 month vs. 3). However, since it shares a target with Run I, the designation here is more appropriate.
Note 2: When unspecified or marked "standard", Run Periods are LE and neutrinos (FHC).
Note 3: No data taken with targets 4 or 6 fall in any of the analysis Run Periods.
Note 4: Data subruns can't be >2 digits, so I use the compact notation popular in the log book. For file names, translate 1234/7 to 01234_0007.