BEGIN:VCALENDAR
VERSION:2.0
PRODID:Linklings LLC
BEGIN:VTIMEZONE
TZID:Europe/Stockholm
X-LIC-LOCATION:Europe/Stockholm
BEGIN:DAYLIGHT
TZOFFSETFROM:+0100
TZOFFSETTO:+0200
TZNAME:CEST
DTSTART:19700308T020000
RRULE:FREQ=YEARLY;BYMONTH=3;BYDAY=-1SU
END:DAYLIGHT
BEGIN:STANDARD
TZOFFSETFROM:+0200
TZOFFSETTO:+0100
TZNAME:CET
DTSTART:19701101T020000
RRULE:FREQ=YEARLY;BYMONTH=10;BYDAY=-1SU
END:STANDARD
END:VTIMEZONE
BEGIN:VEVENT
DTSTAMP:20230831T095754Z
LOCATION:Sanada II
DTSTART;TZID=Europe/Stockholm:20230626T140000
DTEND;TZID=Europe/Stockholm:20230626T160000
UID:submissions.pasc-conference.org_PASC23_sess158@linklings.com
SUMMARY:MS1H - Code as Community
DESCRIPTION:Minisymposium\n\nComputer software, or code, is often seen as 
 a means to an end; which is to say that we create and use code to accompli
 sh an objective — whether the objective is for computational science, musi
 c, performance art, or any number of other applications. That said, Code i
 s an expression of human creativity and ingenuity —and by definition a mea
 ns in which we communicate, and share experiences. In this mini symposium,
  we are interested in how scientific code fosters scientific communities t
 o form, evolve, and/or express themselves in predictable and unpredictable
  ways. We will address the following questions: What are the challenges wi
 th integrating code and teams across distinct communities? What are the ch
 allenges associated with growth by community adoption of code? What are en
 during characteristics of code that survive the test of time in large comm
 unities? When do software developers formally identify as a formal communi
 ty service as in the case of research science engineers? How does code com
 municate? The talks in this session intend to be thought provoking and the
  goal is to encourage developers to have a holistic perspective of communi
 ties in mind when developing their codes.\n\nEnabling Scientific Communiti
 es through ParaView\n\nParaView, an open source scientific visualization f
 ramework, turns 21 years old in 2023. It owes its success and longevity to
  a number of technical factors: its wealth of IO options, plethora of data
  processing filters, client/server architecture, HPC readiness, easy modul
 arity and adaptation and mu...\n\n\nJulien Fausty and François Mazen (Kitw
 are)\n---------------------\nCode and Community: Challenges and Opportunit
 ies\n\nThe last decade of scientific computing has seen increased interdep
 endence between scientific code and scientific communities. Scientific cod
 e provides a shared language for researchers in a scientific community to 
 communicate, explore, collaborate and experiment with complex problems, ne
 w ideas and...\n\n\nRinku Gupta (Argonne National Laboratory) and Elaine R
 aybourn (Sandia National Laboratories)\n---------------------\nScaling a C
 ommunity with over 1,000 Contributors: Bringing Scientists Together with S
 pack\n\nThe Spack package manager centralizes the community knowledge of s
 cientific software installations. Where traditionally cluster sysadmins ma
 intain their own repository of deployment scripts, and developers use thei
 r own tooling for local installations, Spack maintains a single, portable 
 package repo...\n\n\nHarmen Stoppels (Stoppels Consulting)\n--------------
 -------\nDeveloping Services for Scientific Communities: Experiences from 
 the National High Performance Computing Program in Germany\n\nThe academic
  HPC landscape in Germany has become much more service-oriented over the l
 ast decade. Based on the insight that scientists require more than purely 
 technical support to successfully and efficiently work on HPC clusters, st
 ate and federal programs have been instituted that provide consult...\n\n\
 nThorsten Reimann and Christian Bischof (TU Darmstadt)\n\nDomain: Computer
  Science, Machine Learning, and Applied Mathematics &#8232;\n\nSession Chairs: R
 inku Gupta (Argonne National Laboratory) and Elaine M. Raybourn (Sandia Na
 tional Laboratories)
END:VEVENT
END:VCALENDAR
