20200417-Analyzer-Mtg

From PREX Wiki
Jump to: navigation, search

Back to Main Page >> Analyzer_Meeting

previous meeting << >> following meeting

Logistic information

Meeting room at JLab: No meeting room at JLab

 BlueJeans calling instructions:
 Toll-Free Number (U.S.&  Canada):  888-240-2560
 International toll number:         408-740-7256
 Bluejeans CODE:                  385 600 867
 Bluejeans link: https://bluejeans.com/385600867

Agenda

Old issues

  1. Issue 275: Change of EPICS variables for the IHWP state
    • This was pulled into operations, but we need to verify it doesn't break PREX-2 analysis before this gets pulled to develop.
  2. Issue 271: Confusing error messages during channel publication
    • Probably a left-over diagnostic, and these error messages can probably be removed
  3. Issue 269: diff* variables are missing in burst and muls trees
    • Fix has been committed, and should be able to be merged into develop, and to have operations merged.
  4. Issue 245: Burp / stability cuts adversely affect Beam Mod
    • Quinn's changes are simply to expland the cut limits for the burp cut. An expansion of a factor of 2-3 from what was initially set seems to allow all BMOD data to pass. The impact on data quality is to be investigated.

Preparations for new respins

  1. PREX-2 respin2: We want to start this in a week or two from now
    • Paul: Create a comboBCM to be (2*bcm_an_us + bcm_an_ds)/3 except for runs 3594-3573, for which we would use bcm_dg_ds; use this as the normalizing BCM
    • Cameron: Add certain BPM combinations such as the average of 11 and 12 as combined objects, and use them in regression/dithering. Use run-ranging on this combined object to allow us to have a consistent name for the BPMs we use in regression/dithering even as we change the "best choice".
      • This also needs us to collect the "best choice" into run-rnaged lists.
    • Robert: Pedestal re-evaluation
    • Paul: Merge operations & prex-respin1 back to develop and create a prex-respin2 branch
    • What else do we need?
  2. CREX respin1: Start shortly after PREX-2 respin2 completes. Estimate about 4 weeks
    • Dithering correction map updates
    • Run list updates
    • What else? I missed this week's WAC meeting, so could we have a brief update

Respins and ifarm storage

  1. Status of missing output files from PREX-2 respin1
    • Devi had sent the list of runs that he had found missing output files to Robert. It seems like one or two runs in each slug.
    • Robert, Tao, and Sakib have been looking into this: the missing rootfiles may have been due to insufficient volatile space during the early respin period; the missing plots were because the sorting script would get confused if more than one run was being processed at once. The script has been changed to only process the specified run.
  2. Respin of PREX-2 AT dataset
    • The web directory had been set-up. What is the status on doing this respin?
      • The AT respin has been complete. Sakib has put the prompt and respin plots up on the dedicated transverse web pages. There is a little issue with the aggregation though.
        • Cameron suggests that we may want to refactor the aggregation to use the output summary trees as we move forward for the respin. He and Sakib will coordinate on developing this for the AT dataset as the test case.
        • Cameron also suggests that if we're going to use JAPAN regression, we should better document the LRB regression outputs to make it easier for folks to use in the same way as they can work with postpan outputs
  3. Cleanup of the web directory for plots
    • We should also be able to get rid of the files like "run####_###_all.pdf" that are in the individual run subdirectories under the prex2/summary folder, as those PDF files are the concatenation of the other files in the directory.
      • Robert will set up a script to check that the individual PDFs are present and then remove the "all" PDFs


Other issues

Present

Phone: Paul K., Bob M., Siyu, Tao, Weibin, Cameron, Devi, Robert R., Sakib


Excused