Skip to end of metadata
Go to start of metadata


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)


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


2. XSEDE2 Reporting (Leslie Froeschl


  • 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.
  • (6/18) Enjoy the break from reporting. We'll be back at it with IPR12 beginning Aug 1.
    • Panel report should be received next week. 


  • Thanks to everyone for your work on the response to the panel report. John submitted our response yesterday. Recommendations have been created based on the items mentioned in the report. Appropriate folks were assigned those recommendations. Please be sure to go in and address them promptly.
  • The next reporting cycle begins in two short weeks on Aug. 1. Your area PM will be in touch about collecting all of the inputs for your area. L3 text will be due Tuesday, August 4. L2 text will be due Thursday, Aug. 6. Please be prompt and get your part done on time so we can keep on-track with our schedule!
  • Risk review is underway. Please 



3. Cancer Computer L2 Service Provider Request (Ron Payne


  • (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. 
  • (6/18) Approved pending answers to the following questions:
    • Amount of time that will be allocated through XSEDE 
    • magnitude of hardware that will be available. 
    • NSF approval given that CC is based in Canada 


  • Need to get note off to Bob to explain relationship between CC & XSEDE. Concern about whether foreign entity is drawing substantive/inappropriate resources from XSEDE. CC wants visibility. Secondary benefit would be peer review for things placed on that resource. They have been held up in deployments. 100 nodes deployed at 3 locations in Canada. 8-10 nodes at UT, WI, IN. 300 deployed at IL. John doesn't expect this will be a problem, but we need to document what is happening carefully. 
  • Ron Payne to follow up with Roy about amount of time to be allocated.
  • HT Condor based. 
  • Victor will follow up for kickoff meeting once approved. 


4. Code of Conduct (Linda Akli ) 


  • (6/18) Added to agenda.

    • 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. 
    • 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


  • Susan Lindsey & Susan Mehringer co-leading. All areas of XSEDE except Ops & XCI have representation on committee. Great participation so far. 
    • Lizanne to assign an eval person to participate
  • Get list of terminology
  • Workplan, schedule set up.
  • Web pages, training materials in the mix. 
  • Tools: do we need PIF for ECSS staff to provide some AI for the process. 
  • Potential guidelines going out to make sure we don't collect new materials that might be considered offensive. 
  • If anyone can participate in hunting for offensive terms, or if your org has any lists, please reach out to the team. 
  • Google folder set up for documents etc. 
  • Believe we may be in the lead on doing this work in the community. ACM has addressed some parts with facial recognition, AI, but not this issue in particular. ACM diversity/inclusivity council was going to look into this as well. Will be difficult for them due to extensive ACM library. 
  • NCSA has done some work generating a list of terms & alternative language. John will share this list. 
  • Need to include why a term is offensive and what an alternate could be. Context is very important. 


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) - 
    • NSF has provided Approval To Spend for PY10. 
    • 1 year extension request has not been fully processed yet. Unofficial approval but working through the approval process. 
    • XSEDE Response to Panel Review Report has been submitted and accepted by NSF. Bob has acknowledged it and filed in the e-jacket at NSF.
    • Still no word on follow-on to XSEDE. They are working on it, but no indication that solicitation will be out soon. 
      • Any likelihood about another extension year after PY11? They're trying to avoid it if possible. 
      • No indication of whether it will be a single award or multiple awards. 
  • Tim
    • No update
  • CEE (Kelly) - 
    • In middle of student season. Advanced computing for social change & faculty component coming up. 
    • What has happening in recent climate has sparked people to be more aware of language/behavior. Important that this dialogue is happening and change is happening as a result. 
      • Something that is offensive to someone in one part of the country may not be to someone in another part of the country. 
      • Hope people feel comfortable asking questions and engaging in conversations to learn. 
    • Tapia conference is the celebration of diversity in computing. Has become a huge hiring fair. Will be virtual this year. We can adjust sponsorship. Can post job opps, interview in XSEDE booth for job opps. Good opportunity to encourage more diversity in hiring, expose people to career opportunities at our centers. 
    • Request to give access to non-XSEDE staff to be able to make changes to XSEDE training calendar. Uncomfortable with non-XSEDE staff changing XSEDE web pages. Want to mitigate any possible exposure. Planning to create a policy that states who can add things to the training calendar to make clear that non-XSEDE staff will not be able to.
      • 2 people at SDSC who handle scheduling/logistics for all training events. Can continue to go through existing XSEDE staff to accomplish this.    
  • ECSS (Bob S/Phil/Sergiu) - 
    • Will reach out to all ECSS staff to help track down potential offensive content. 
    • Preparing for next wave of NSF compute resources and how the team will get up to speed on those resources. 
  • XCI (Dave L/Craig) - 
    • People preparing for PEARC.  

  • Ops (Greg/Victor) -   
    • Discussing implications of new SPs and what needs to happen to get them all integrated
    • AUP  
  • RAS (Dave H/Ken/Nathan) - 
    • Deadline for next XRAC was yesterday. 224 requests 
    • Expanse & Bridges2 allocations will be included in this review. Ken planning training for reviewers about these systems. 
    • Rolling out new fields of science to be included in allocation submissions going forward 
    • Getting close to rollout of new AMIE rest API for new SPs coming on.
  • Program Office (Ron/Leslie) - 
  • SP Forum (Ruth) -  
    • Have to drop off to meet with the Boss

    • Have had presentations on the five newly awarded systems
    • not SP Forum related, but thanks for XSEDE for being a PEARC20 exhibitor. As of this morning, 654 registrants (56 of whom are students)
  • UAC (Emre) -  
    • UAC meeting this afternoon. 
  • NSF (Bob C) - No update

Next Meeting:     SMT - August 13, 2020 (no meeting July 30 due to PEARC)

  • No labels