Skip to end of metadata
Go to start of metadata

Attendees:

Canonical Meeting Template (as a reminder):

1. Review of meeting agenda
2. Addressing issues

  • Description/Status of issue
  • Review of action items from previous meetings if any
  • Recommended actions and discussion of same
  • Close issue or identify next action items

3. Status updates from SMT members

  • Status update on significant activities
  • Review of prior open issues if any (and not addressed earlier in agenda)
  • Identification of new issues if any (and not addressed earlier in agenda)

Agenda/Notes

1. Review of Meeting Agenda: Any comments/additions? 

 

2. XSEDE2 Reporting (Leslie Froeschl

Previously:

  • Previous discussion archived: SMT Meeting - April 9, 2020
  • (4/23) RY4 annual reporting will begin on May 1. 
      • Tuesday 5/5/2020: L3 text due to PMs; PMs give L3 text to L2s

      • Thursday 5/7/2020: All L2 text (including L3 text) due to PMs

    • Supplement doc
      • Holly working on prelim budget (should have it tomorrow)
        • Can repurpose unspent funds for year 6 (e.g., participant support funds)
        • Need to project funds we can't spend due to COVID-19 crisis
      • Should have draft to John early next week for his review.
      • All subaward partners so far have indicated interest in participating an additional year. 
  • (5/7) All text due to your PM TODAY for the annual report. Please get your inputs in today to keep us on schedule!
  • (5/21) Supplement request was submitted on Tuesday. Annual report was submitted late yesterday (on time). Thank you to all for your efforts! We won't need to worry about reporting again until August.

Discussion:

  • Enjoy the break from reporting. We'll be back at it with IPR12 beginning Aug 1.
  • Panel report should be received in another week or so. 

Decisions:

 

3. Cancer Computer L2 Service Provider Request (Ron Payne

Previously:

  • (5/27) SPF L2 Request Letter sent to L2 for consideration.
  • (5/28) Questions posed from Bob S & Dave H:
    • (1) What is the hardware they are providing. Their website says “We are computing the cure in our 6 supercomputing clusters in Ottawa, Montreal, Kitchener, Bloomington, Minneapolis, Salt lake City, and Urbana-Champaign.” Beyond that, it’s pretty vague.

      • Donations of hardware that they repurpose in an HT condor environment/high throughput. Find sites willing to host, and site gets access to some percentage of equipment in exchange for hosting. Equipment is retired after a period of time, but should be similar to OSG. 
    • (2) Are these resources that are used solely by Cancer Computer or do they just provide spare cycles like OSG?

      • All except those used by hosting site are allocated by CC. They will delegate that to XSEDE in this case. 
      • What work host sites allow on the machines has to be in support of cancer research. 
    • (3) What fraction of the time will be allocated through XSEDE?

      • John will have to find out. Non trivial amount. 
    • (4) Do they have any special capabilities for dealing with sensitive data? That would be a big plus and offer something XSEDE doesn’t currently have. Not necessarily at the level of HIPAA compliance, but maybe ability to work with dbGaP data

      • Not at this time. It's complicated for them as an org with an intl footprint as different nations have different requirements. 
    • (5) Do we need to be concerned at all with the fact that Cancer Computer is based in Canada? Some of its hardware is based in the US, but the SP itself is Canada-based.

      • A lot of resources are at US institutions. IN, IL, UT & others. Could provide some level of support to Canadian researchers, but see this similar to OSG. Need to be careful we're not giving away resources across international boundaries. John will bring this up with Bob to see if he can provide guidance. 
      • We wouldn't change allocations process–would still need to be US researcher. 

Discussion:

  • See above for responses to questions from John. 

Decisions:

  • Bob: approve, but would like response from CC re. time that will be allocated through XSEDE and magnitude of hardware that will be available. 
  • Dave H: They will need to know how to answer this question. Approve pending NSF approval 
  • Greg: Approve pending NSF approval 
  • Phil: Approve
  • Emre: Approve
  • Dave L: Approve
  • Linda: Approve
  • John: Abstain
  • Approved pending issues raised above. 

4. Code of Conduct (Linda Akli

Previously:

  • (6/18) Added to agenda.

Discussion:

  • Received multiple complaints about offensive language used in XSEDE bootcamp/parallel MPI. Linda talked to John Urbanic, Susan Mehringer, and Ken Hackworth. Have done a good job promoting code of conduct. They use wording/terminology that refers to "master slave." 2 people sent emails about how offensive this was. That terminology is not controlled by us. There are alternative terms out there, but Open MPI has not done so. They are working on this, however. Don't want to guide people to use non-offensive terms if that creates problems coding. 
  • Recommendation: slide for trainers. Code of conduct acknowledges that there are offensive, but this is not controlled by XSEDE but by outside entities. That will help trainers as they are uncomfortable as they don't endorse the terminology. Allows participants to know XSEDE does not condone. Talked about how me might influence developers of Open MP, MPI (friends on steering committee), GIT, spark, tensorflow
  • John: Language is used to describe programming model. Language used in official standard for MPI. MPI standards body has recognized this is a problem and is working to rectify it. Expectation of vote on change to standard at SC20. Proposed language is "manager worker." Didn't realize Open MP has similar issue. Linda to ask training team to dig deeper to find a contact with Open MP. John Townswill send communication to Open MP organization (CEO, chair of language committee) to address this issue of use of "master" in their documentation. 
  • Linda could not find anything on ACM site regarding this, which was a surprise. Linda Akli to reach out to John West at TACC (ACM diversity chair) to ask about this. 
  • Linda Akli to forward complaints to John. 

Decisions:

John: Appoint task force to review all online content/documentation including wiki to look for such offensive terms.  CEE will take the lead in pulling this together. Maytal Dahan Linda Akli

5. International COVID-19 HPC Knowledge Exchange (Robert Sinkovits

Previously:

  • (6/18) Added to agenda.

Discussion:

  • Can XSEDE put up a webpage to host slides/ recordings from this group modeled after ECSS symposium page (https://www.xsede.org/for-users/ecss/ecss-symposium). 
  • European counterpart to stand up similar page as well. 
  • Also like to add to collective list of supported projects that is searchable so people can better see what's going on and connect with one another. 

Decisions:

  • John: Stand this up off submission page. Discussion about pages targeted to researchers that would compliment this. Robert Sinkovits to reach out to Maytal's team about getting the page stood up. 

Around the call up

Follow this basic outline:

  • Status update on significant activities
  • Review of prior open issues if any (and not addressed earlier in agenda)
  • Identification of new issues if any (and not addressed earlier in agenda)
  • Identification of recent improvements implemented

Updates from SMT members:

  • PI (John/Ron) - 
    • Bob said we can expect panel report over the weekend or early next week. He indicated we should be pleased with the report. We will need to provide written response to all recommendations. 
    • We will have a review of RY5 next year at about the same time. Will adjust reporting schedule to adjust and add RY6. Will have to submit RY5 annual report.   
    • Globus subscription for extension: John concerned that nature of our agreement indicates we'll have priority in requests & fixes that we submit to them. John asked for summary of what that looked like for Globus and got no answer. Agreed to renegotiate contract and eliminate much of the overhead costs. Reserved right to make changes based on review of their response. 
  • Tim
    • No update
  • CEE (Kelly) - 
    • Doing a lot of training
    • On Monday did a consultation with Robin Scibek at PSC. Bridges2 award has wording from NSF about expectations for diversity/inclusion. Gave her some recommendations. Questions about staffing/equal opportunity, outreach to broaden communities. Encouraged her to plug into work XSEDE is already doing. SPs are all welcome to come to BP team for review on things of this nature.   
  • ECSS (Bob S/Phil/Sergiu) - 
    •  In process of selecting next batch of campus champion fellows. 14 applicants. Need to know how many fellows we can accept. Ron Payneto look at the budget and let Bob know if we need to stay at 5 or be able to increase to 6. Note that there will be less travel in the upcoming year. 
  • XCI (Dave L/Craig) - 
    • No update 

  • Ops (Greg/Victor) -   
    • PCR for Dave Wheeler as DTS L3 has been submitted.  
  • RAS (Dave H/Ken/Nathan) - 
    • Working with Holly to get ORCID membership renewed. 
    • Looking into what it would take for XRAS to become ORCID certified service provider. 
    • Talking with DOE about potential collaboration
    • June awards were posted last week. 
  • Program Office (Ron/Leslie) - 
    • Reminder: Enter Publications in XUP and documents in IDEALS
    • Reminder: Reference collaborations in tracking worksheet: https://docs.google.com/spreadsheets/d/19YRAPeAForh5I9Xvhj8nKjROe3-JN7a1caLYbNamPaw
    • Reminder: Address recommendations (Jira) 
    • Staff allocation renewal request submitted. Have to identify which users should be carried over.  None of the current users logged in, so Ron only put John, Ron, Leslie on the allocation. If there are teams/individuals that need to use it Ron needs to be informed. 
      • Linda: her team puts in education requests for training. Never use the main staff allocation
      • John: if not being used, don't need to carry forward. Not sure which are being used and which aren't. Ron Paynewill send out usage data. Important to check login as well as usage. Some are used to login and check things. 
      • Ops and  XCI are owned by Victor and used to login and check things. 
      • When people offboard from the staff, need to clean up those users in those projects. This is done as part of the offboarding process as long as the project is indicated on the offboarding form.  
    • Holly Highland took another position at NCSA so moving off XSEDE as of June 26. Any business office communications should be sent to xsede-admin@ncsa.illinois.edu
    • XSEDE advisory board meeting next Tuesday
    • If you haven't done so, complete doodle poll for your availability for August XSEDE all-staff
  • SP Forum (Ruth) -  
    • No update

  • UAC (Emre) -  
    • available to provide user feedback/perspective. Contact Emre or Sergiu. 
    • Will have a post-review summary meeting soon. 
    • When will extension be approved? Will need to rotate some new members on. 
      • John: haven't gotten official notice yet, but can start thinking about this for UAC and XAB. Shouldn't solicit yet, but can start thinking about possibilities. 
  • NSF (Bob C) - No update


Next Meeting:     SMT - July 2, 2020 


  • No labels