Feature #6627
better sam interface to run_periods/playlists
0%
Description
https://cdcvs.fnal.gov/redmine/projects/mnvproso/wiki/Runperioddefiner
has a first pass at the idea for how this will work.
Use run_period_tools (and MC equivalent) as a base and put info into sam metadata.
History
#1 Updated by Heidi Schellman over 5 years ago
1. What we need is a simple interface that given a RUN SUBRUN pair (or just a run) and MC vs data, returns the playlist name for that period.
2. What we also need is something that, given a playlist name, returns the run ranges that correspond to that playlist.
Syntax might be
Python API
playlistName(type=data, run=0, subrun=0)
shell syntax
playlistName mc 10201
playlistName data 2060 3
should return the playlist name or nosuchsubrun or unknown
The run periods for LE are documented at https://cdcvs.fnal.gov/redmine/projects/minerva-sw/wiki/Data_Run_Periods
$PRODUCTIONSCRIPTSROOT/production_tools/RunPeriodTools.py codes in the data run periods
MC run periods are coded in the run number - and documented at
https://cdcvs.fnal.gov/redmine/projects/minerva-sw/wiki/Monte_Carlo_Production_Run_Numbers
it would be good to be able to have the same run period designations (eg. minerva1) for these as for data.