Difference between revisions of "SRO RTDP Nov. 18, 2024"
(Created page with "The current weekly meeting time is every other Monday at 10:00 US/Eastern === Connection Info: === <div class="toccolours mw-collapsible mw-collapsed"> You can connect using...") |
|||
Line 73: | Line 73: | ||
=== Minutes === | === Minutes === | ||
+ | |||
+ | Attendees: David L., Mike G., Jeng T. | ||
+ | |||
+ | * Vardan and Cissie were away at SC24 this week | ||
+ | |||
+ | * We briefly discussed the CLAS12 packet capture data | ||
+ | ** Processing of that data is still stalled. We need to gain heavy momentum there so we can demonstrate a physics signal from the data. (e.g. pi0 peak) | ||
+ | ** David will discuss with Nathan how to move this forward | ||
+ | |||
+ | * Discussion of milestones M16-M18 that create proxy components for an effects-based simulation | ||
+ | ** Mike will start working on a stand-alone CPU component. | ||
+ | *** This will require an initial list of configuration parameters (e.g. Nthreads, latency, etc...) | ||
+ | *** Data ingress/egress may be controlled via reading/writing a socket | ||
+ | *** Work on GPU and FPGA components will follow once a working CPU component is established | ||
+ | |||
+ | * Jeng reported on work to get a cycl workflow running on slurm with 3 processes (iperf3 server+client and prometheus DB server) | ||
+ | ** A cycl configuration and a fireworks configuration file were shown. We discussed again how the system would work with DPOL as a master configuration and translators to generate either cycle or fireworks configurations from it | ||
+ | ** David expressed concerns that progress on the framework itself and component development has not commenced due to focus on the configurations. | ||
+ | *** Jeng will focus on milestone M15 "Establish general framework for RTDP simulation" that will be capable of utilizing Mike's CPU component | ||
+ | ** Cissie will focus on the monitoring infrastructure | ||
=== Action Items === | === Action Items === |
Revision as of 16:03, 18 November 2024
The current weekly meeting time is every other Monday at 10:00 US/Eastern
Connection Info:
You can connect using ZOOM Video conferencing (ID: 160 248 4178). (Click "Expand" to the right for details -->):
One tap mobile: US: +16692545252,,1602484178# or +16468287666,,1602484178#
Meeting URL: https://jlab-org.zoomgov.com/j/1602484178?pwd=UFViZUpyODYrZmsxdkVNbWZTMUR1Zz09&from=addon
Meeting ID: 160 248 4178
Passcode: 104412
Join by Telephone
For higher quality, dial a number based on your current location.
Dial: +1 669 254 5252 US (San Jose)
+1 646 828 7666 US (New York)
+1 646 964 1167 US (US Spanish Line)
+1 551 285 1373 US (New Jersey)
+1 669 216 1590 US (San Jose)
+1 415 449 4000 US (US Spanish Line)
833 568 8864 US Toll-free
Meeting ID: 160 248 4178
International numbers
Join from an H.323/SIP room system
H.323: 161.199.138.10 (US West)
161.199.136.10 (US East)
Meeting ID: 160 248 4178
Passcode: 104412
SIP: 1602484178@sip.zoomgov.com
Passcode: 104412
One tap mobile: US: +16692545252,,1601987443# or +16468287666,,1601987443#
Meeting URL: https://jlab-org.zoomgov.com/j/1601987443?pwd=bUVPV3puTHJPU0Fub2Q2Z1dsV0JjQT09&from=addon
Meeting ID: 160 198 7443
Passcode: 607906
Agenda:
- Previous Meeting
- Announcements:
- Project Progress: (Github Project)
- May 2024 Packet Capture Analysis
- JANA2 configuration - Nathan (github issue)
- RTDP workflow monitoring
- Prometheus server - Cissie (github issue)
- Prometheus + ePIC - Cissie (github issue)
- RTDP Configuration
- DPUX format spec. - Vardan
- Graphical editor - Vardan (github issue)
- DPUX example config. - Jeng (github issue)
- May 2024 Packet Capture Analysis
- BDX Status + R&D
- AOT
Milestones
- Full Milestones and Objectives (revised for year 2)
Minutes
Attendees: David L., Mike G., Jeng T.
- Vardan and Cissie were away at SC24 this week
- We briefly discussed the CLAS12 packet capture data
- Processing of that data is still stalled. We need to gain heavy momentum there so we can demonstrate a physics signal from the data. (e.g. pi0 peak)
- David will discuss with Nathan how to move this forward
- Discussion of milestones M16-M18 that create proxy components for an effects-based simulation
- Mike will start working on a stand-alone CPU component.
- This will require an initial list of configuration parameters (e.g. Nthreads, latency, etc...)
- Data ingress/egress may be controlled via reading/writing a socket
- Work on GPU and FPGA components will follow once a working CPU component is established
- Mike will start working on a stand-alone CPU component.
- Jeng reported on work to get a cycl workflow running on slurm with 3 processes (iperf3 server+client and prometheus DB server)
- A cycl configuration and a fireworks configuration file were shown. We discussed again how the system would work with DPOL as a master configuration and translators to generate either cycle or fireworks configurations from it
- David expressed concerns that progress on the framework itself and component development has not commenced due to focus on the configurations.
- Jeng will focus on milestone M15 "Establish general framework for RTDP simulation" that will be capable of utilizing Mike's CPU component
- Cissie will focus on the monitoring infrastructure