CESER LIGO / UCSD UChicago call

Tuesday 30 Jul 2019, 13:00 → 14:00 US/Central

http://bit.ly/rwg-zoom

Edgar Fajardo Hernandez (UCSD), Frank Wuerthwein (UCSD), Igor Sfiligoi (University of California San Diego), James Clark (Georgia Institute of Technology), John Hicks (Internet2), Pascal Paschos (University of Chicago), Robert Gardner (University of Chicago)

Google drive folder, https://drive.google.com/drive/folders/1OaDZ6OPE6On8Bt2byuoAWr5kKH7XwmUZ

Meeting notes in:

https://docs.google.com/document/d/146OP2zqQC7BB4SAmgLuv-TeYLTTesiPs_NfCttdwliA/edit#heading=h.i2ed2c4usz4v

document https://docs.google.com/document/d/1nqRA0XSwFqBh6SfOPH3OQrh6NRVMFW5b3QTH24Msknc/edit?pli=1#heading=h.5leu34h1e5vu

2019.07.30 UC-UCSD OSG-LIGO CESER

 

Attendeeds: 

Indico Call details: https://indico.fnal.gov/event/21295/

Agenda: 

1. Review Frank’s NSF report for items to add:

https://docs.google.com/document/d/1nqRA0XSwFqBh6SfOPH3OQrh6NRVMFW5b3QTH24Msknc/edit#

Focus on the next steps beyond the automation tools currently in place. 

2. Can we add osg.Ceser in the RSV autojobs for tracking the usage on Gracc? Any other way for jobs to show up in reporting? Tentatively yes. Edgar will add this to the ‘submit’ scripts and Pascal will create the graphs in Gracc. 

3. SAND - Data collections. Kibana/UNL reported VO name should be the filter. We will look into checking what’s stored based on the VO. Allegedly the relevant information is there. We need to check on the applications as well. See below:

4. We can use the LigoSearchTag to filter out the applications (James/Edgar)

 Example: prod.o3.burst.paramest.bayeswave

RIFT: dev.o3.cbc.pe.lalinferencerapid  (the name RIFT is relatively new)


Condor-8.8 ----now supports GPU hours as well. Work done on the PRP will need some additional details as it reports GPU time. It should be the same as CPU time. We will reprocess all the classAd files with ligosearchtag to bucket them into application categories based on input.