[Halld-offline] Preliminary analysis run lists

[Justin Stevens]

Hi All,

As a followup, I've added an input to the monitoring webpages to specify MYSQL queries to the monitoring DB:

https://halldweb1.jlab.org/cgi-bin/data_monitoring/monitoring/plotBrowser.py
https://halldweb1.jlab.org/cgi-bin/data_monitoring/monitoring/timeSeries.py

Now by adding the MYSQL query requirements (like in my previous message below) you can select specific running conditions to view the time series or run-by-run monitoring plots.  From this, I did some preliminary run QA to reject a few runs where the multiplicities in certain detectors were significantly different from other runs with similar conditions.  The run lists posted as txt files have been updated at:

https://halldsvn.jlab.org/repos/trunk/home/jrsteven/scripts/batch_detcom/

If you identify runs which should be removed from (or added to) the "good" run lists, let me know so we can keep these lists updated.  

Thanks,
Justin

On Jan 15, 2015, at 12:48 PM, Justin Stevens wrote:

> Hi All,
> 
> At yesterday's calibration meeting I was asked to send out a list of the runs I was using for my bump hunting analysis.  The run lists are posted as txt files at
> https://halldsvn.jlab.org/repos/trunk/home/jrsteven/scripts/batch_detcom/runlist_FCAL.txt
> https://halldsvn.jlab.org/repos/trunk/home/jrsteven/scripts/batch_detcom/runlist_BCAL.txt
> https://halldsvn.jlab.org/repos/trunk/home/jrsteven/scripts/batch_detcom/runlist_FCAL_BCAL.txt
> 
> I haven't done a detailed run-by-run QA so I wouldn't claim this is a "golden" run list, but hopefully its a place to start.  If there are problems observed for specific runs or I'm missing some other good runs we can subtract from or add to these lists.  
> 
> The lists were generated with some simple mysql queries to the monitoring database that Sean put together and we used for the offline monitoring webpages.  Below are example queries to generate these lists, so you can simply modify them to generate a new runlist that might better fit your needs.
> 
> FCAL trigger:
> mysql -u datmon -h hallddb.jlab.org -e "select run_num, num_files from run_info where run_num>1500 and solenoid_current>1190 and beam_current>20 and num_events>50000 and (trigger_config_file='fcal_m8.conf' || trigger_config_file='fcal_all_m8.conf') and run_num>1500 and run_num<1530;" data_monitoring
> 
> BCAL trigger: (I saw some issues with TAGM/H timing for 1790-1799 which is why I excluded them)
> mysql -u datmon -h hallddb.jlab.org -e "select run_num, num_files from run_info where run_num>1500 and solenoid_current>1190 and beam_current>20 and num_events>50000 and (trigger_config_file='bcal_m8.conf' || trigger_config_file='bcal_all_m8.conf') and run_num>1540 and run_num<1810 && (run_num<1790 || run_num>1799);" data_monitoring
> 
> FCAL-BCAL trigger:
> mysql -u datmon -h hallddb.jlab.org -e "select run_num, num_files from run_info where run_num>1500 and solenoid_current>1190 and beam_current>20 and num_events>50000 and trigger_config_file='fcal_bcal_m8.conf' and run_num>2139 and run_num<2500;" data_monitoring
> 
> If you're interested I also put a python script in svn (https://halldsvn.jlab.org/repos/trunk/home/jrsteven/scripts/batch_detcom/subTemplate.py) which I'm using to submit jobs for the files in each of these runs using the same mysql queries.  It's not the most elegant setup, but you're free to strip out the pieces you like for your own scripts.
> 
> -Justin
> _______________________________________________
> Halld-offline mailing list
> Halld-offline at jlab.org
> https://mailman.jlab.org/mailman/listinfo/halld-offline