FWD Software

["Jindal, Nicholas" <jindal.78 AT buckeyemail.osu.edu>]

Hi All, As discussed in our meeting today, here are full instructions for running my QA scripts: Run the command 'get_file_list. pl -keys -cond production=P25ib,trgsetupname=production_pp500_2022,filetype=daq_reco_picodst,storage=local’ to return

ZjQcmQRYFpfptBannerStart

This Message Is From an External Sender

This message came from outside your organization.

 

ZjQcmQRYFpfptBannerEnd

Hi All,

As discussed in our meeting today, here are full instructions for running my QA scripts:

1. Run the command 'get_file_list.pl -keys -cond production=P25ib,trgsetupname=production_pp500_2022,filetype=daq_reco_picodst,storage=local’ to return all picoDsts from the Run22 pp500 production. You can write this output to a .list file and sort or split however you like to choose the files you’d like to run over. 
2. Located at ‘/gpfs01/star/pwg/nickjindal14/fwd_lambda/star-sw-fwd/StRoot/StFwdTrackMaker/macro/pico’  are files called ‘qa_master.C’ and ’submit_qa.xml’.  I recommend cloning the dev branch of star-sw-fwd in your directory of choice and copying over these two files and the .hpp files specified in the sandbox of the .xml file into your macro/pico subfolder. 
3. Create the output and log directories specified in the .xml file and update the paths to yours.
4. If you’d like to run over the full dataset, keep the input line in the .xml file to the one that starts with ‘catalog:star.bnl.gov’ to automatically run over the whole production. If you’d like to run over a specific subset, use the commented out input line and point it to your file list you’d like to use.
5. In the .xml file, the line ‘root -l -b -q qa_master.C+\(1,\”input.list\”\) takes an integer. Change this integer to reflect the track type you want to use. 0 is Global tracks, 1 is BLC, 2 is primaries, 3 is tracks fit with a forward vertex. 
6. After modifying the .xml to reflect the desired track type (and naming the jobs appropriately so you don’t forget), run ’star-submit submit_qa.xml’ and the output files with relevant histograms will be written to your output directory. 

If you attempt to run any of this and run into issues, please reach out and I can help you troubleshoot. Please also reach out if you have questions about doing run-by-run qa or producing slides like the ones I’ve shown in previous meetings and I can point you to some other code I run locally to handle this. 

Best,

-- 

Nicholas Jindal

PhD Candidate

The Ohio State University Department of Physics

jindal.78 AT osu.edu