Skip to content

Commit d3cc02b

Browse files
authored
Merge pull request #103 from kmohrman/kmohrman-update-spring2024
Updating progress spring 2024
2 parents aefb4d6 + 12d2aa8 commit d3cc02b

File tree

1 file changed

+11
-6
lines changed

1 file changed

+11
-6
lines changed

pages/postdocs/kmohrman.md

+11-6
Original file line numberDiff line numberDiff line change
@@ -30,11 +30,16 @@ presentations:
3030
meeting: <Tracking POG Meeting>
3131
meetingurl: <https://indico.cern.ch/event/1337451/>
3232

33+
- title: "Project status update: LST with the SONIC framework"
34+
date: "February 12, 2023"
35+
url: <https://indico.cern.ch/event/1374894/contributions/5778400/attachments/2799411/4883360/sonic_lst_update_feb12_2024.pdf>
36+
meeting: <Tracking POG Meeting>
37+
meetingurl: <https://indico.cern.ch/event/1374894/>
38+
39+
3340
current_status:
34-
- The project is in progress
35-
- Learned to run the LST workflow in order to reproduce LST plots from Philip Chang's LST CHEP presentation
36-
- 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
37-
- 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)
38-
- 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
39-
- Currently working to adapt the LST workflow with SONIC (starting with the client side i.e. reworking the producer with SONIC)
41+
- Preliminary work: First learned to run the LST workflow in order to reproduce LST plots from Philip Chang's LST CHEP presentation. Set up at Purdue and ran 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 same workflow 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.
42+
- Setting up LST backend: Successfully set up and ran example Patatrack as a service example at Purdue and at UF. Produced a draft version of SONIC compatible LST producer. Removed ROOT dependencies from LST in order to enable the successful compilation and running of the standalone TrackLooper LST within the server singularity environment from the SONIC PatatrackAAS example. Created a backend (modeled after the PatatrackAAS identity_backend example) that can compile and run LST (though currently the inputs to the evaluation are already hard coded within the backend) using the PatatrackAAS client as a standin to trigger the backend code to be run.
43+
- Next steps: Work on connecting the LST client side with the server side to enable the transfer LST inputs from the client to the backend, and to return the results back to the client
44+
4045
---

0 commit comments

Comments
 (0)