August People Network and RCD Community Calls

Mark your calendars for these upcoming People Network calls (Zoom details at the end). For handy calendar entries, try the CaRCC Events Calendar. We also highlight other calls from our RCD Ecosystem partners and collaborators, as these events touch many, if not all, in our community.

CaRCC People Network Calls:

Data-Facing Track (first Tuesdays)

There is no call in August. Join us in September!

Researcher-Facing Track (second Thursdays)

Highlights from PEARC22, discussion facilitated by R-F Steering Committee

Thurs, August 11th, 1p ET/ 12p CT/ 11a MT/ 10a PT

Back by popular demand we bring you the Researcher-Facing PEARC recap for our August call! The advanced computing community reunited in Boston for PEARC22 and during this call we will share highlights, explore what we learned, and discover some nuggets that you may have missed! If you were not able to attend the conference, this will be a great opportunity to get caught up. Please join to contribute your favorite PEARC22 moments. Drawing from what we learned at Boston, we will also dialogue around new topics for the R-F track in the coming year. 

Emerging Centers Track (third Wednesdays)

Specialization and Silos, Positioning and Potential:  How should you decide what your RCD team does and doesn’t do? discussion facilitated by Jonathan Dursi  

HPC Leadership Institute overview with Andrew Jones

Linux Clusters Institute Workshops overview with TBD

Wednesday, August 17th, 12p ET/ 11a CT/ 10a MT/ 9a PT/ 7a HT

Like a lot of us, Jonathan started his career doing research, and realized he could have a lot more impact (and fun!) supporting others research instead.  Initially thinking that whole research computing and data (RCD) world was more or less like his large 3D fluid simulations, working at an HPC centre (and then coordinating HPC centres) introduced him to the much broader range of research problems relying on RCD resources and expertise.  He then spent several years in genomics, first helping develop methods and run pipelines, and then running a national platform and software development effort connecting genomics and clinical data in a federated manner across Canada.  Seeing the impact that RCD teams have had across so many fields, he’s become both pretty passionate about their importance in driving science and scholarship forward, and pretty frustrated by the lack of support and training new managers and leaders get when they step up and take on responsibility for these teams.  RCD managers typically already have pretty advanced skills – but nobody shows them the basics of being a manager, or positioning an RCD practice.  Now, in addition to his day job working at NVIDIA, he writes a newsletter for a slowly growing community of current and potential RCD managers and leaders, aiming to help them be more effective and less stressed managing these important teams of experts.

Systems-Facing Track (third Thursdays)

Identifying Requirements for Early Career PT/FT RCD Systems Focused IT, discussion facilitated by Betsy Hillery – Purdue, Brian Haymore – University of Utah

Thu Aug 18th, 12p ET/ 11a CT/ 10a MT/ 9a PT

Recruiting the right people for RCD System’s IT Support is difficult.  What are the minimum entry skills that you are looking for in new hires?  This month we want the community to help define what early career skills are required for individuals to grow and be successful in your organization.  Some points to think about in advance:

  • What skills are required vs preferred?
  • What skills are the hardest to find in candidates or develop in new hires?
  • How does this change between smaller (wear many hats) and larger institutions (specialties)?
  • What additional, lacking or emerging skills should new team members focus on developing next?

Additional community opportunities:

Aug 12 at 2p ET/ 1p CT/ 12p MT/ 11a PT: US Research Software Engineers monthly community call. See for more information.

CaRCC Calls and Zoom:

All calls will take place within the People Network Zoom room, distributed via email for security purposes.