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.
  • (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. 
  • (7/16) 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. 
  • (8/13) 
    • IPR12 is underway and going well so far. Thank you to everyone for your efforts!
    • Reminder to all L2s to send Leslie any updates on COVID-19 related work to be included in the report by end of this week. 
  • (8/27)
    • IPR12 submitted on time, accepted by NSF, and posted to IDEALS/the reporting wiki page. Enjoy the reporting break until November! 

Discussion:

Decisions:

 

3. Update on terminology task force (Linda Akli ) 

Previously:

  • (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 DahanLinda Akli
  • (7/16) 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. 
  • (8/13) 
    • The group met Monday. Found some industry lists with terminology of concern. If you run across any concerning words, please inform a member of the task force.
    • John to send Linda a list from NCSA.

Discussion:

  • Session at Quarterly meeting next week for the committee to discuss their work. 

Decisions:


4. Interconnections Diagrams (Tim Boerner )

Previously:

  • (8/13) Added to agenda.

    • Reference:  REC-249 - Getting issue details... STATUS
    • connection between scientific impact, workforce development, and contributions made by the XSEDE 2.0 project
    • Interconnections diagrams could help address this. Need to get diagrams to a place that they work together. 
    • Will pull together L2s to discuss.
    • Would be useful as part of big picture/XSEDE overview presentations. Would also be helpful as we respond to future solicitations. 

Discussion:

  • No update. There will be a meeting during the quarterly next week to discuss this.  

Decisions:




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) - 
    • Met with Bob & Al today. Proposal acceptance on new platforms: new systems will not be full to 100% immediately. Will take a few cycles to get there. Bob understands this.
    • C19HPC consortium: Haven't added many projects to XSEDE resources lately. Working on defining phase 2 work. Leaning to therapeutics & patient care related proposals. Will get sticky with NSF since that is a domain they typically aren't involved with. Not sure if XSEDE will continue involvement or back off to respect those boundaries. Would like to continue to help address the crisis (which would mean no change), but waiting for guidance from NSF on this.
      • Drug design & specific patient care & outcomes. Not outside NSF scope. As long as it's not clinical only and involves research aspect, then within NSF scope. Question is how much is research vs. applied. In some cases no real research but applying models to data. Getting close to the line so need guidance from NSF. Amy Freelander has brought up this issue, so clear that they're talking about this internally.      
  • Tim
  • CEE (Kelly) - 
    • No update
  • ECSS (Bob S/Phil/Sergiu) - 
    •  Tomorrow holding ECSS all-hands meeting
      • discussing training on new resources
    • Represented ECSS & campus champions at XPERT network meeting
  • XCI (Dave L/Craig) - 
    • Victor is now taking on campus research computing/HPC at UTK. Tabitha Samuels will be doing SP coordination for XCI moving forward. Will be meetings about this during Quarterly meeting. 

  • Ops (Greg/Victor) -   
    • Victor will remain deputy director for Ops despite above-mentioned new role. 
    • Security issues with Liferay will be discussed during Quarterly next week.
    • Acceptable Use Policy changes will be brought to SMT soon.
  • RAS (Dave H/Ken/Nathan) - 
    • XRAC meeting Monday. 

    • Working on update to allocations policy doc. Running past SP Forum and then will bring back to the leadership team
    • Ready for Expanse & Bridges2 to come online when ready. 
  • Program Office (Ron/Leslie) - 
  • SP Forum (Ruth) -  
    • Discussing Open On Demand. JP & team meeting with OnDemand folks to explore tech details re. potential integration

    • Happy to have Tabitha joining as SP coordinator!
  • UAC (Emre) -  
    • No update
       
  • NSF (Bob C) - No update


Next Meeting:     SMT - September 10, 2020


  • No labels