deploy: e30004f

feed.xml

@@ -1 +1 @@
-<?xml version="1.0" encoding="utf-8"?><feed xmlns="http://www.w3.org/2005/Atom" ><generator uri="https://jekyllrb.com/" version="4.2.2">Jekyll</generator><link href="/feed.xml" rel="self" type="application/atom+xml" /><link href="/" rel="alternate" type="text/html" /><updated>2023-09-06T18:37:50+00:00</updated><id>/feed.xml</id></feed>
+<?xml version="1.0" encoding="utf-8"?><feed xmlns="http://www.w3.org/2005/Atom" ><generator uri="https://jekyllrb.com/" version="4.2.2">Jekyll</generator><link href="/feed.xml" rel="self" type="application/atom+xml" /><link href="/" rel="alternate" type="text/html" /><updated>2023-11-06T14:30:41+00:00</updated><id>/feed.xml</id></feed>

postdocs/kmohrman.html

@@ -90,7 +90,7 @@
         <br>
         <h3>Project: Deploying GPU algorithms through SONIC</h3>
 
-        The goal of the project is to demonstrate at a sufficiently large scale the reconstruction algorithm workflow within CMSSW to be processed, where the client jobs are running on one site, while the Line Segment Tracking (LST) algorithm will be executed on GPUs on computing nodes at another site connected through SONIC (Services for Optimized Network Inference on Co-processors) framework.
+        The goal of the project is to demonstrate at a sufficiently large scale the reconstruction algorithm workflow within CMSSW to be processed, where the client jobs are running on one site, while the Line Segment Tracking (LST) algorithm will be executed on GPUs on computing nodes at another site connected through SONIC (Services for Optimized Network Inference on Co-processors) framework. LST is a tracking algorithm that takes advantage of double-layer design of the HL-LHC outer tracker in order to perform hit correlations in a parallel way with GPUs. SONIC is a framework that provides GPUs as a service to clients running at different sites.  Combining the LST algorithm with the SONIC framework is the goal of the project, in which we aim to to demonstrate the execution of the LST algorithm on GPUs at an external site (apart from the site where the client jobs are run) via the SONIC framework.
 
         <br>
         <br>
@@ -164,7 +164,7 @@ <h3>Project: Deploying GPU algorithms through SONIC</h3>
 
 
 
-            <p>Philip Chang - (University of Florida)&gt;</p>
+            <p>Philip Chang - (University of Florida)</p>
 
 
           </li>
@@ -176,12 +176,16 @@ <h3>Project: Deploying GPU algorithms through SONIC</h3>
         <b>Presentations</b>
         <ul>
 
+
+          <li>23 Oct 2023 - <a href="<https://indico.cern.ch/event/1337451/contributions/5630393/attachments/2738948/4763938/kmohrman_sonic_lst_intro_oct23_2023.pdf>">"Project introduction and plans: LST with the SONIC framework"</a>, Kelci Mohrman, <a href="<https://indico.cern.ch/event/1337451/>"><Tracking POG Meeting></a>
+
+
         </ul>
         <hr>
 
         <b>Current Status</b>
         <br>
-
+        The project is in progress - Learned to run the LST workflow in order to reproduce LST plots from Philip Chang's LST CHEP presentation - Have gotten set up at Purdue and run the test SONIC workflow (MAOD workflow) and successfully ran the setup where the cmsRun script runs on the login node, and the cmsTriton script runs on a different node - Have gotten the workflow (same one we got running at Purdue) running at UF (with cmsRun on one node without any GPUs and cmsTriton on a different node) - Tested with cmsRun at Purdue and cmsTriton at UF, but hit issue with nodes not being able to talk to each other, paused this direction for now - Currently working to adapt the LST workflow with SONIC (starting with the client side i.e. reworking the producer with SONIC)
         <br>
         <br>