<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title></title>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type"/>
</head>
<body style="height: 100% !important; width: 100% !important; background-color: #F7F9FA; margin: 0; padding: 0;">
<!-- Preheader -->
<table border="0" cellpadding="0" cellspacing="0" align="center" style="font-family:Arial,Helvetica,sans-serif;font-size: 13px;color:#131619;background-color: #F7F9FA; width: 100%; height: 100%;padding-bottom: 10px;">
<tr>
<td style="vertical-align: top">
<table border="0" cellpadding="0" cellspacing="0" align="center" style="width:700px;">
<tr>
<td style="vertical-align: top;padding: 0px; background-color: #f4f5f9">
<table border="0" cellpadding="0" cellspacing="0" align="center"
style="margin-left: 0px;margin-right: 0px;width: 100%;background-color: #ffffff;padding-bottom: 37px;">
<!-- email header -->
<tr>
<td style="padding-top: 28px;padding-bottom: 28px;padding-left:32px;background-color:#0B5CFF;text-align: left;">
<a href= "https://zoom.com">
<img src="https://click.zoom.us/l/84442/2022-12-29/c4ns1t/84442/1672332921RKagdau8/Logo_white_2022.png" style="border-style: solid;" width="110" height="25" border="0"/>
</a>
</td>
</tr>
<!-- email body -->
<tr>
<td style="padding-left: 32px;padding-right: 32px;">
<table border="0" cellpadding="0" cellspacing="0" align="center"
style="width: 100%;font-size: 16px;color:#131619;">
</table>
<table border="0" cellpadding="0" cellspacing="0" style="width: 100%; height: 100%;">
<tbody>
<tr style="height: 24px;"></tr>
<tr>
<td colspan="2">
<table border="0" cellpadding="0" cellspacing="0" align="left" style="padding-top: 5px;padding-bottom: 5px;width: 100%;font-size: 13px;color: #39394d;font-family: Arial;background: #F2F2F4;">
<tr>
<td align="left" width="55" style="width: 55px;mso-line-height-rule: exactly; line-height: 30px;vertical-align:top;padding: 7px 12px 10px 12px">
<img width="55" height="25" src="https://st3.zoom.us/static/6.3.31180/image/summary/summary_new_logo_v2.png" style="width: 55px; height: 25px; border-width: 0; border-style: solid;vertical-align: bottom;" />
</td>
<td align="left" style="text-align: left; font-size: 13px;color: #39394d;font-family: Arial,Helvetica,sans-serif;vertical-align: middle;">
Meeting summary with AI Companion now supports additional languages in preview. </td>
<td align="left" width="80" style="width: 80px;text-align: left; font-size: 13px;color: #39394d;font-family: Arial,Helvetica,sans-serif;vertical-align: middle;">
<a style="display: inline-block;color: #0B5CFF;text-decoration: none;font-weight: 600" href="https://support.zoom.com/hc/en/article?id=zm_kb&sysparm_article=KB0058013#languages">Learn More</a>
</td>
</tr>
</table>
</td>
</tr>
<tr style="height: 24px;"></tr>
<tr>
<td colspan="2" style="font-size: 19px;color: #131619;font-family: Arial,Helvetica,sans-serif;line-height: 25px;font-weight: 700;">
<table border="0" cellpadding="0" cellspacing="0" align="center" style="width: 100%;font-size: 19px;color: #39394d;font-family: Arial;">
<tr>
<td align="left" style="padding-right: 24px;mso-line-height-rule: exactly; line-height: 25px;text-align:left;font-size:19px;color:#39394d;font-family:Arial,Helvetica,sans-serif;vertical-align:top">
<strong>Meeting summary for DesignSafe Release/Management Meeting (02/10/2025)</strong>
</td>
</tr>
</table>
</td>
</tr>
<tr style="height: 32px;"></tr>
<tr>
<td colspan="2" style="font-size: 16px;color: #39394d;font-family: Arial,Helvetica,sans-serif;vertical-align: top;line-height: 20px;">
<strong>Quick recap</strong>
</td>
</tr>
<tr style="height: 6px;"></tr>
<tr>
<td colspan="2" style="font-size: 16px;color: #39394d;font-family: Arial,Helvetica,sans-serif;vertical-align: top;line-height: 20px;">
The meeting covered various aspects of DesignSafe's operations and future plans, including recent events, data management, and training initiatives. Discussions centered on improving data repositories, organizing training materials, and planning upcoming workshops and symposiums. The team also addressed technical considerations such as GPU usage and potential budget constraints, while emphasizing the importance of community engagement and user-driven development.
</td>
</tr>
<tr style="height: 32px;"></tr>
<tr>
<td colspan="2" style="font-size: 16px;color: #39394d;font-family: Arial,Helvetica,sans-serif;vertical-align: top;line-height: 20px;">
<strong>Next steps</strong>
</td>
</tr>
<tr style="height: 6px;"></tr>
<tr>
<td colspan="2" style="font-size: 16px;color: #39394d;font-family: Arial,Helvetica,sans-serif;vertical-align: top;line-height: 20px;">
• Scott to coordinate with Charlie on scheduling and preparing materials for the scientific computing with Python webinar
</td>
</tr>
<tr>
<td colspan="2" style="font-size: 16px;color: #39394d;font-family: Arial,Helvetica,sans-serif;vertical-align: top;line-height: 20px;">
• Krishna to prepare and record a demo video on using Jupyter GPU instances on TACC resources
</td>
</tr>
<tr>
<td colspan="2" style="font-size: 16px;color: #39394d;font-family: Arial,Helvetica,sans-serif;vertical-align: top;line-height: 20px;">
• Scott to follow up with the other data set award winner from last year about doing a webinar
</td>
</tr>
<tr>
<td colspan="2" style="font-size: 16px;color: #39394d;font-family: Arial,Helvetica,sans-serif;vertical-align: top;line-height: 20px;">
• Ellen to follow up with Clint about potentially using Irik for summer training events
</td>
</tr>
<tr>
<td colspan="2" style="font-size: 16px;color: #39394d;font-family: Arial,Helvetica,sans-serif;vertical-align: top;line-height: 20px;">
• Tim, Scott, and Krishna to create a description and application form for the planned research workshop
</td>
</tr>
<tr>
<td colspan="2" style="font-size: 16px;color: #39394d;font-family: Arial,Helvetica,sans-serif;vertical-align: top;line-height: 20px;">
• Ellen and Tim to prepare an outline of the user workshop plans by Thursday for the NHERI 3.0 meeting
</td>
</tr>
<tr>
<td colspan="2" style="font-size: 16px;color: #39394d;font-family: Arial,Helvetica,sans-serif;vertical-align: top;line-height: 20px;">
• Ellen and Tim to develop a plan for gathering Summer Institute participants' interests in the additional training day
</td>
</tr>
<tr>
<td colspan="2" style="font-size: 16px;color: #39394d;font-family: Arial,Helvetica,sans-serif;vertical-align: top;line-height: 20px;">
• Tim to ensure SIM Center is included in planning for the research workshop and Summer Institute training
</td>
</tr>
<tr>
<td colspan="2" style="font-size: 16px;color: #39394d;font-family: Arial,Helvetica,sans-serif;vertical-align: top;line-height: 20px;">
• Natalie to confirm room reservation details for the summer events
</td>
</tr>
<tr>
<td colspan="2" style="font-size: 16px;color: #39394d;font-family: Arial,Helvetica,sans-serif;vertical-align: top;line-height: 20px;">
• Ellen to download and share the group picture from the symposium
</td>
</tr>
<tr>
<td colspan="2" style="font-size:14px;line-height:32px;color:#dedede;border-bottom: 1px solid #dedede;padding-top:22px;">
</td>
</tr>
<tr>
<td colspan="2" style="font-size:14px;line-height:32px;padding-top: 22px;">
</td>
</tr>
<tr>
<td colspan="2" style="font-size: 16px;color: #39394d;font-family: Arial,Helvetica,sans-serif;vertical-align: top;line-height: 20px;">
<strong>Summary</strong>
</td>
</tr>
<tr style="height: 6px;"></tr>
<tr>
<td colspan="2" style="font-size: 16px;color: #39394d;font-family: Arial,Helvetica,sans-serif;vertical-align: top;line-height: 20px;">
<strong>Travel Experiences and Flight Issue</strong>
</td>
</tr>
<tr>
<td colspan="2" style="font-size: 16px;color: #39394d;font-family: Arial,Helvetica,sans-serif;vertical-align: top;line-height: 20px;">
Ellen, Scott, Natalie, Maria, Tim, and Jamie convened for a meeting. Scott and Tim shared their travel experiences, with Scott arriving early for his flight and Tim recounting a tight connection in Dallas. The team also discussed a potential issue with a flight, but it was resolved as Tim was able to get off and back on the same plane. The conversation ended with Jamie joining and the possibility of starting the main discussion.
</td>
</tr>
<tr style="height: 20px;"></tr>
<tr>
<td colspan="2" style="font-size: 16px;color: #39394d;font-family: Arial,Helvetica,sans-serif;vertical-align: top;line-height: 20px;">
<strong>DesignSafe Symposium and Fire Research</strong>
</td>
</tr>
<tr>
<td colspan="2" style="font-size: 16px;color: #39394d;font-family: Arial,Helvetica,sans-serif;vertical-align: top;line-height: 20px;">
Ellen, Tim, and Scott discussed the recent Symposium event, highlighting the contributions of DesignSafe and SIM Center. Tim expressed his struggle to find a central meeting point for the Fire Research community and suggested the possibility of organizing meetings or events with Et's help. Ellen proposed the idea of hosting workshops related to other hazards, such as wildfires, in the upcoming DesignSafe 3.0. Scott recalled that fire was not allowed in the time of DesignSafe 2.0 due to NSF restrictions. Maria and Jamie participated in the discussion but did not contribute significantly.
</td>
</tr>
<tr style="height: 20px;"></tr>
<tr>
<td colspan="2" style="font-size: 16px;color: #39394d;font-family: Arial,Helvetica,sans-serif;vertical-align: top;line-height: 20px;">
<strong>Creating Categories for Test Beds</strong>
</td>
</tr>
<tr>
<td colspan="2" style="font-size: 16px;color: #39394d;font-family: Arial,Helvetica,sans-serif;vertical-align: top;line-height: 20px;">
Jamie proposed the idea of creating a separate category for test beds in their data set types, considering the discussions about designsafe SIM center partnership and calibration studies. Ellen agreed, suggesting that the community should drive the definition of benchmarks and test beds. Maria proposed creating a catalog of external data sets and APIs, and Scott suggested creating a searchable inventory of user-contributed apps. The team also discussed the challenges of vetting and supporting community-contributed apps. The conversation ended with a positive impression of the increased focus on data reuse and technical depth compared to previous meetings.
</td>
</tr>
<tr style="height: 20px;"></tr>
<tr>
<td colspan="2" style="font-size: 16px;color: #39394d;font-family: Arial,Helvetica,sans-serif;vertical-align: top;line-height: 20px;">
<strong>Data Set Nominations and Webinars</strong>
</td>
</tr>
<tr>
<td colspan="2" style="font-size: 16px;color: #39394d;font-family: Arial,Helvetica,sans-serif;vertical-align: top;line-height: 20px;">
The team discussed the progress of data set nominations, with a significant increase in the number of nominations. They also discussed the involvement of students in future computational symposiums and the potential for more structured data sets. There was a discussion about the use of Amazon Web Services for hosting databases, with a suggestion to consider file-based databases for simplicity. The team also discussed the upcoming webinars, with one confirmed for the spring, and the possibility of more webinars in the future.
</td>
</tr>
<tr style="height: 20px;"></tr>
<tr>
<td colspan="2" style="font-size: 16px;color: #39394d;font-family: Arial,Helvetica,sans-serif;vertical-align: top;line-height: 20px;">
<strong>Creating Training Repository in Github</strong>
</td>
</tr>
<tr>
<td colspan="2" style="font-size: 16px;color: #39394d;font-family: Arial,Helvetica,sans-serif;vertical-align: top;line-height: 20px;">
Ellen proposed the idea of having a training repository in Github to record materials from webinars, which Scott and Krishna agreed to. The repository would be linked to the learning center for easy access. Tim suggested that each training event should have its own repository under the 'designsafe ci' prefix. Scott agreed to work with Charlie to create a repository for their training session. Tim also mentioned that Sylvia and Carlos should contribute to the repository. Krishna offered to create a template for the repository.
</td>
</tr>
<tr style="height: 20px;"></tr>
<tr>
<td colspan="2" style="font-size: 16px;color: #39394d;font-family: Arial,Helvetica,sans-serif;vertical-align: top;line-height: 20px;">
<strong>Training Catalog and Material Organization</strong>
</td>
</tr>
<tr>
<td colspan="2" style="font-size: 16px;color: #39394d;font-family: Arial,Helvetica,sans-serif;vertical-align: top;line-height: 20px;">
The team discussed the organization and presentation of training materials. They considered naming it a "Training Catalog" to emphasize its active and accessible nature. The idea of having a condensed template was also discussed to make it easier for users to navigate. The team agreed that the catalog should include a list of all pages, with each page linking to a webinar and its supplementary materials, rather than directing users straight to the YouTube channel. They also discussed the need for a table with essential information such as title, presenters, date, and links to materials.
</td>
</tr>
<tr style="height: 20px;"></tr>
<tr>
<td colspan="2" style="font-size: 16px;color: #39394d;font-family: Arial,Helvetica,sans-serif;vertical-align: top;line-height: 20px;">
<strong>Updating Data Repository and Webinar Topics</strong>
</td>
</tr>
<tr>
<td colspan="2" style="font-size: 16px;color: #39394d;font-family: Arial,Helvetica,sans-serif;vertical-align: top;line-height: 20px;">
The team discusses updating their data repository, removing outdated links, and adding a training catalog. They also consider potential webinar topics, including one on DEM (Discrete Element Method). Krishna suggests that while a DEM webinar might be useful, it may not attract many attendees. Instead, they propose first implementing "lights" (a related feature) and then conducting a webinar to demonstrate its usage. The conversation concludes with a mention of a potential machine learning GPU webinar.
</td>
</tr>
<tr style="height: 20px;"></tr>
<tr>
<td colspan="2" style="font-size: 16px;color: #39394d;font-family: Arial,Helvetica,sans-serif;vertical-align: top;line-height: 20px;">
<strong>GPU Versions and Resource Sharing</strong>
</td>
</tr>
<tr>
<td colspan="2" style="font-size: 16px;color: #39394d;font-family: Arial,Helvetica,sans-serif;vertical-align: top;line-height: 20px;">
Krishna, Ellen, and Dan discussed the use of GPU versions of Jupiter for their system. They considered the possibility of using the native GPU version, but were unsure of its implementation. They also discussed the potential of sharing GPU resources, which Dan emphasized as crucial for their future plans due to the high cost of new hardware. The team agreed to continue using the current GPU instances for training, but decided to further discuss the path forward for their system.
</td>
</tr>
<tr style="height: 20px;"></tr>
<tr>
<td colspan="2" style="font-size: 16px;color: #39394d;font-family: Arial,Helvetica,sans-serif;vertical-align: top;line-height: 20px;">
<strong>HPC Jupiter Training and Transition</strong>
</td>
</tr>
<tr>
<td colspan="2" style="font-size: 16px;color: #39394d;font-family: Arial,Helvetica,sans-serif;vertical-align: top;line-height: 20px;">
The team discussed the need for a hands-on training session on using the HPC Jupiter, with a focus on the GPU nodes. They agreed on the importance of creating a containerized solution for production use. The training session was planned to be recorded and made available for future reference. The team also discussed the potential transition to the Vista platform, but noted the challenges associated with it. The decision was made to create a demo video showcasing the use of the containerized HPC GPU, with the aim of making it available for those who couldn't participate in the hands-on session.
</td>
</tr>
<tr style="height: 20px;"></tr>
<tr>
<td colspan="2" style="font-size: 16px;color: #39394d;font-family: Arial,Helvetica,sans-serif;vertical-align: top;line-height: 20px;">
<strong>Training Events and Budget Concerns</strong>
</td>
</tr>
<tr>
<td colspan="2" style="font-size: 16px;color: #39394d;font-family: Arial,Helvetica,sans-serif;vertical-align: top;line-height: 20px;">
The team discussed plans for upcoming training events, particularly focusing on the Summer Institute and user workshops. They acknowledged the departure of Carlos, who was a key figure in these events, and discussed potential replacements, including Eric. The team also discussed the need for a clear description of the training events to attract participants. They agreed to create an application form for the Summer Institute, which would require participants to describe their research objectives, current use of DesignSafe, and what they hope to achieve with the training. The team also discussed the potential for senior PhD students or postdocs to assist with the training. The budget for the next fiscal year was also a topic of discussion, with concerns raised about potential cuts to NSF funding.
</td>
</tr>
<tr style="height: 20px;"></tr>
<tr>
<td colspan="2" style="font-size: 16px;color: #39394d;font-family: Arial,Helvetica,sans-serif;vertical-align: top;line-height: 20px;">
<strong>User Workshop and Summer Institute Planning</strong>
</td>
</tr>
<tr>
<td colspan="2" style="font-size: 16px;color: #39394d;font-family: Arial,Helvetica,sans-serif;vertical-align: top;line-height: 20px;">
Ellen, Tim, Scott, Natalie, Jamie, and Maria discussed the planning and logistics of a user workshop and the Summer Institute. They agreed to have funding available for the user workshop and to reserve a seminar room for the event. They also decided to bring the topic to a broader meeting involving the Summer Institute. The team agreed to outline the user workshop and the Summer Institute by the next meeting. They also discussed the possibility of adding a training day to the Summer Institute. The team ended the conversation on a positive note, with plans to be in touch soon.
</td>
</tr>
<tr style="height: 32px;"></tr>
<tr>
<td colspan="2" style="font-style: italic;font-size: 16px;color: #39394d;font-family: Arial,Helvetica,sans-serif;vertical-align: top;line-height: 20px;">
AI-generated content may be inaccurate or misleading. Always check for accuracy. </td>
</tr>
<tr style="height: 32px;"></tr>
<tr>
<td>
<a href="https://DesignSafe-ci.zoom.us/user/meeting/summary?meetingId=LJiDl94vRr%2Bbrdm7ZSkKfA%3D%3D&summaryId=mss_eNJRRLK5RXCqh3pwWHQ0dA&fileId=S_HC4g37T2yAZcGFy_V3iA" style="border: 1px solid #DFE3E8; padding: 6px 16px;border-radius:6px;color:#131619;text-decoration:none;font-weight: bold;">Edit</a>
</td>
<td style="text-align: right; font-size: 16px;color: #39394d;font-family: Arial,Helvetica,sans-serif;vertical-align: top">
<table border="0" cellpadding="0" cellspacing="0" align="center"
style="width: 100%;font-size: 13px;color: #39394d;font-family: Arial;">
<tr>
<td align="right"
style="mso-line-height-rule: exactly; line-height: 30px;text-align:right;font-size:16px;color:#39394d;font-family:Arial,Helvetica,sans-serif;vertical-align:top;">
Please rate the accuracy of this summary. </td>
<td align="left"
style="text-align: left; font-size: 16px;color: #39394d;font-family: Arial,Helvetica,sans-serif;vertical-align: middle;">
<a style="text-decoration:none;display: inline-block"
href="https://DesignSafe-ci.zoom.us/meeting/summary/feedback?meetingId=LJiDl94vRr%2Bbrdm7ZSkKfA%3D%3D&email=aG9zdDEwQGRlc2lnbnNhZmUtY2kub3Jn&feedback=good"> <img height="30" width="30"
src="https://st2.zoom.us/static/6.3.31180/image/summary/feedback_good.png"
style="width: 30px; height: 30px; border-width: 0; border-style: solid;"/> </a>
<a style="text-decoration:none;display: inline-block" href="https://DesignSafe-ci.zoom.us/meeting/summary/feedback?meetingId=LJiDl94vRr%2Bbrdm7ZSkKfA%3D%3D&email=aG9zdDEwQGRlc2lnbnNhZmUtY2kub3Jn&feedback=bad"> <img
height="30" width="30" src="https://st1.zoom.us/static/6.3.31180/image/summary/feedback_bad.png"
style="width: 30px; height: 30px; border-width: 0; border-style: solid;"/> </a>
</td>
</tr>
</table>
</td>
</tr>
</tbody>
</table>
<table>
<tr>
<td style="padding-top: 32px;font-size: 16px;line-height: 20px;">
Best,
</td>
</tr>
<tr>
<td style="font-size: 16px;line-height: 20px;padding-top: 10px;">
Zoom
</td>
</tr>
</table>
</td>
</tr>
<!-- email footer -->
<tr>
<td style="padding-top: 56px;background-color: #FFFFFF;">
<table align="center" border="0" cellpadding="0" cellspacing="0">
<tbody>
<tr>
<td>
<a href="https://twitter.com/zoom" style="text-decoration: none;display: inline-block;">
<img alt="Twitter" border="0" height="32" src="https://click.zoom.us/l/84442/2019-12-26/bfs1bv/84442/140021/Social_Twitter_2020.png"
style="width: 32px; height: 32px; border-width: 0px; border-style: solid;"
/>
</a>
</td>
<td style="padding-left:16px; padding-right: 16px;">
<a href="https://www.linkedin.com/company/zoom-video-communications/"
style="text-decoration: none;display: inline-block;">
<img alt="LinkedIn" border="0" height="32" src="https://click.zoom.us/l/84442/2019-12-26/bfs1bs/84442/140023/Social_LinkedIn_2020.png"
style="width: 32px; height: 32px; border-width: 0px; border-style: solid;"
/>
</a>
</td>
<td>
<a href="https://blog.zoom.us/" style="text-decoration: none;display: inline-block;">
<img alt="Blog" border="0" height="32" src="https://click.zoom.us/l/84442/2019-12-26/bfs1bx/84442/140025/Social_Blog_2020.png"
style="width: 32px; height: 32px; border-width: 0px; border-style: solid;"
/>
</a>
</td>
</tr>
</tbody>
</table>
<table align="center" border="0" cellpadding="0" cellspacing="0" width="100%">
<tbody>
<tr>
<td style="font-size:12px; line-height:16px; color:#6E7680; text-align:center;padding-top: 16px;">+1.888.799.9666</td>
</tr>
<tr>
<td style="font-size:12px; line-height:16px; color:#6E7680; text-align:center;padding-top: 10px;">
©2025 Zoom Communications, Inc.
</td>
</tr>
<tr>
<td align="center" style="padding: 16px 0 0;font-size:12px;line-height:16px;color:#6E7680;" valign="top">
Visit <a href= "https://zoom.com" style="color:#6E7680" target="_blank">zoom.com</a>
</td>
</tr>
<tr>
<td align="center" style="padding: 4px 0 32px;font-size:12px;line-height:16px;color:#6E7680;" valign="top">
<a href="https://www.google.com/maps/place/55+Almaden+Blvd,+San+Jose,+CA+95113/@37.3328541,-121.897097,17z/data=!3m1!4b1!4m5!3m4!1s0x808fcca40adf3cb7:0x5a2d33d3593e0a33!8m2!3d37.3328541!4d-121.8949083" style="color:#969AA1; text-decoration: none;" target="_blank">
55 Almaden Blvd<br/>San Jose, CA 95113 </a>
</td>
</tr>
</tbody>
</table>
</td>
</tr>
</table>
</td>
</tr>
</table>
</td>
</tr>
</table>
</body>
</html>