August 2016 - Allocations-admins - mailman3.cels.anl.gov

New LCRC report submitted for Lanthanide_FF
by support＠lcrc.anl.gov 08 Aug '16

08 Aug '16

Full project report at https://accounts.lcrc.anl.gov/reporting/project/2016/?project=Lanthanide_FF

1 0

New LCRC report submitted for DMDOHEMA_1
by support＠lcrc.anl.gov 08 Aug '16

08 Aug '16

Full project report at https://accounts.lcrc.anl.gov/reporting/project/2016/?project=DMDOHEMA_1

1 0

[LCRC Accounts] Yearly Allocation Request for ATLAS
by accounts＠lcrc.anl.gov 08 Aug '16

08 Aug '16

Hello, A yearly allocation for the LCRC cluster has been requested with the following updated information: Submitter/PI: Thomas LeCompte Project Name: ATLAS Division: HEP Project title: Using LCRC Resources for Analysis of ATLAS LHC Data Associated funding: DOE Office of High Energy Physics Other Systems: Local cluster, 15 machines 240 cores (2M hours) ALCF, 60M hours NERSC, 16M hours Science: We would like to use Blues for the final analysis phase - mostly limit setting - for data from the ATLAS experiment at the Large Hadron Collider. ATLAS has published 432 papers since 2009, generating just under 40,000 citations. About half of these papers are searches for new phenomena (and would have one or more exclusion curves) and the ANL group plays a major role in perhaps 20% of those. The scientific impact is quite large. Project description: In general, this kind of limit setting uses "Toy Monte Carlos" - a model with a given set of parameters is run many times, the fraction of times the run "looks like the data" is recorded, and the parameter set accepted or rejected because of this. Then the next set is tested, and so on. We have done similar things before at ALCF, but this code performs well at the scale of hundreds of ranks, but not thousands: it's really not optimal for the leadership-class computers. Typically each core will take one model (and its associated set of parameters) and test its compatibility with the data. Based on these outcomes, an exclusion curve is created and ultimately published. We have done one of these last year at LCRC, and based on this and other similar calculations at ALCF, an average one takes 40K CPU hours. This includes rerunning the jobs because of upstream hours. A good goal is four of these per year, hence the request for 50K per quarter. Industry partnership: Project URL: Current FY Hours Used: undetermined amount New FY Requested allocation: 200000 Q1: 50000 Q2: 50000 Q3: 50000 Q4: 50000 Justification: Storage requirements: 1 TB is fine; if this is not true in the future, we will be in touch. Thank You, The LCRC Accounts System

1 0

[LCRC Accounts] Yearly Allocation Request for CSE-nodes
by accounts＠lcrc.anl.gov 04 Aug '16

04 Aug '16

Hello, A yearly allocation for the LCRC cluster has been requested with the following updated information: Submitter/PI: John Blaas Project Name: CSE-nodes Division: CSE Project title: Users of CSE purchased nodes Associated funding: Other Systems: Science: See description. Project description: Just used for the CSE nodes Industry partnership: Project URL: Current FY Hours Used: undetermined amount New FY Requested allocation: 4 Q1: 1 Q2: 1 Q3: 1 Q4: 1 Justification: Storage requirements: Thank You, The LCRC Accounts System

1 0

New LCRC report submitted for ATLAS
by support＠lcrc.anl.gov 03 Aug '16

03 Aug '16

Full project report at https://accounts.lcrc.anl.gov/reporting/project/2016/?project=ATLAS

1 0