Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

NAME
PRESENT (tick)/(error)
XAB Members
Lisa Arafune (Chair)

(tick)Image Added

Leah Bendavid

(tick)Image Added

Ken Bloom

(tick)Image Added 

Elizabeth Cherry

(tick)Image Added

Rylan Chong

(tick)Image Added

Peter Couvares

(tick)Image Added

Rudi Eigenmann

(tick)Image Added 

Ana Carmen Gonzales(error)
Ruby Mendenhall

(tick)Image Added

Brook Milligan

(tick)Image Added

Russell Poldrack(error)
Jennifer Schopf

(tick)Image Added

Ani Ural(error)
Service Provider Forum

Ruth Marinshaw

(tick)Image Added

Dan Stanzione

(error)
David Hancock

(tick)Image Added

User Advisory Committee

(tick)Image Added

XSEDE Staff

(tick)Image Added

(error)

(tick)Image Added

(tick)Image Added

(error)

(tick)Image Added

(error)

(tick)Image Added

(tick)Image Added

(tick)Image Added

(tick)Image Added

Sergiu Sanielevici

(tick)Image Added

(tick)Image Added

Draft Agenda

Friday, June 24

Time (CST)

DurationTopic (w/links to presentation materials)
1:00 pm5 mins

Welcome

Approval of

June

April XAB meeting summary

  • Emre/Peter move to accept. Approved.
1:05 pm50 mins

Status on transition from XSEDE to ACCESS

  • XSEDE on good path to close down at end of August. No cost extension through Aug 23 to close financials & complete final reporting. Will also support a number of students' attendance at SC22 & PEARC23 to utilize unspent funds. 
  • A lot of questions from community re. what comes next, how to do various things. Have been getting communications going out regularly to Service/Resource Providers. 
  • Yesterday got our first broad communication out to community re. transition. Using XSEDE mechanisms/channels for these. 50,000 individuals that have signed up for XSEDE comms, so using that for transition comms. Will continue to provide weekly communications with updates coming from all parts of ACCESS. Have provided a way for community to ask questions. 
  • Sept. 1 - ACCESS will handle these communications. ACCESS will inherit much of XSEDE online identity (Twitter, Facebook, etc.) to make the transition easier. 
  • SSO hub will NOT continue under ACCESS. This has generated concerns, but not within ACCESS budget scope. Informing community about this so they know how to authenticate. While SSO hub won't continue, we are passing along XSEDE identity so people won't have to establish new identities. 
  • All allocations will continue to be available. One final XRAC later in August. Those allocations will be supported under ACCESS. 
  • People asking how to get a new allocation. If allocation expiring, there will be an opportunity in December on same schedule/parameters that we've used for XSEDE. Then changes will be implemented next calendar year. RAMPS has interesting ideas for improving the allocations process. They have responded well to difficulty for community members to get allocations/high expectations for proposals. Have created a process that is far less painful–especially for those seeking smaller allocations.  
  • Some concerns/questions from community, but nothing really serious. Lots of conversations during PEARC. 
  • Questions re. education accounts as we head into fall semester. Working to address those currently. 

XAB questions/comments:

  • Ken: Metrics on user take-up as we head into ACCESS? 
    • Will be hard to measure until we get to Sept. 1. Will be responsibility of ACCESS teams to determine that. 
    • SPs are partners in this & working hard to communicate with users on their systems to inform them of changes & assure them their allocations are fine. 
    • Expect things to be smooth
    • Will probably best know this when ACCESS does its first community survey and starts to get feedback from community about their experience.
  • Peter: Response from community about end of ECSS? 
    • NSF has indicated there will be other mechanisms/opportunities related to this. NSF had a townhall meeting and shared info on solicitations that will be coming to fund ECSS style support in the future. Not clear how much support there will be. Could result in level of aggregate effort that comes close to what is being provided by ECSS today–remains to be seen. 
    • In a few cases, ECSS staff have arranged with PIs they've worked with to continue being funded directly by the PI. 
    • Pool of talent will start to evaporate without continued funding. 
    • ACCESS User Services offers an option to secure ECSS type of expertise, but researcher must fund it. 
    • NSF cybertraining program offers 3-4 cyber professional awards.  Link to the CyberTraining solicitation, which includes the effort that the CI Professionals will dedicate to the ACCESS Computational Science Support Network: https://www.nsf.gov/pubs/2022/nsf22574/nsf22574.htm
    • ECSS hasn't been getting over-run with emails/concerns about it ending. 
    • These concerns have been expressed to NSF many times. 
  • Ruth: SP Forum has had each of the four ACCESS tracks plus coordination office visit SPF meetings to share plans/allow time for questions & concerns. Everyone on all sides want this to be as smooth as possible with little/no disruption to community. Expect things to evolve  over the years of the ACCESS awards. 
  • Rudi: How are you documenting best practices? 
    • XSEDE staff has been documenting best practices & lessons learned over the last 1 1/2 years or so. Staff has been documenting processes/procedures/policies-- will find these posted in the UIUC IDEALS document repository. Includes many things from projects over the 11 years of XSEDE (reports, policy docs, evaluation docs, process docs, etc.). They have persistent IDs so will be available perpetually. A big piece of final report will be lessons learned/best practices. Will be formally submitted with final report and made available separately in IDEALS. Detailed transition plan doc continues to evolve and will be submitted as part of final report and posted in IDEALS. Good idea to have a record of how we did things that others (and we) can refer back to in the future. If new ideas under ACCESS don't work out, we might want to revisit some of these.  
1:55 pm5 mins

Wrap up/Close Meeting

Thank you for your service to XSEDE!

  • Has been so important to XSEDE to have advice, reviews of docs & plans. This has been critical to XSEDE's success. We have taken your suggestions & recommendations very seriously & helped us improve over time. I hope other projects can learn from how we interacted with XAB. Feels more engaged than many other advisory boards. The regular meeting schedule has allowed us to get feedback more regularly than if we only met once or twice per year. 
  • Legacy of bringing in social scientists to the community. XSEDE impacted this community. 

Wrap up/Close Meeting

Notes