Difference between revisions of "SRO RTDP Oct. 9, 2023"
| (One intermediate revision by the same user not shown) | |||
| Line 1: | Line 1: | ||
| − | The current weekly meeting time is | + | The current weekly meeting time is Mondays at 14:00 US/Eastern |
=== Connection Info: === | === Connection Info: === | ||
| Line 57: | Line 57: | ||
''TBD'' | ''TBD'' | ||
==== Action Items ==== | ==== Action Items ==== | ||
| − | + | The action items were pre-determined in slides shown at the meeting and are copied here for convenience. | |
| + | |||
| + | M01: Ayan + Vardan | ||
| + | * Vardan should consult and guide, but Ayan needs to be able to create and understand ERSAP configurations on his own | ||
| + | * Be able to explain an ERSAP configuration. (e.g. one file, many files. Format, …) | ||
| + | |||
| + | M02: Ayan + Vardan + Fabio + Sergey B. | ||
| + | * Sergey B. will do most of the heavy lifting, but Ayan and Fabio should be able to run the DAQ and know how to access the data later | ||
| + | * Find target date(s) for data capture. File naming scheme. Location files will be stored in Computer Center. Specification for file format. | ||
| + | |||
| + | M03: Jeng + Cissie | ||
| + | * Many processes will need to run on specialized, remote hardware that is not managed by a scheduling system. (ssh?) | ||
| + | * Report on plan for launching or checking processes needed for configuration. | ||
| + | ** This does not need to be a completely implemented solution. Just what types of servers need to be running etc. | ||
| + | |||
| + | M04: Ayan + Jeng | ||
| + | * Code for project needs to be on Github in JeffersonLab organization. Relevant links on EPSCI wiki page. Skeleton documentation. | ||
| + | * RTDP repository created (linked to RTDP wiki page). Skeleton documentation in place with access permissions set to allow edit privileges for team members. | ||
Latest revision as of 01:55, 23 October 2023
The current weekly meeting time is Mondays at 14: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: (slides)
- Previous Meeting
- Introductions
- Meeting schedule (move to European-friendly time)
- Review project goals and timeline
- Y1Q1 milestones and task assignments
- AOT
Minutes
TBD
Action Items
The action items were pre-determined in slides shown at the meeting and are copied here for convenience.
M01: Ayan + Vardan
- Vardan should consult and guide, but Ayan needs to be able to create and understand ERSAP configurations on his own
- Be able to explain an ERSAP configuration. (e.g. one file, many files. Format, …)
M02: Ayan + Vardan + Fabio + Sergey B.
- Sergey B. will do most of the heavy lifting, but Ayan and Fabio should be able to run the DAQ and know how to access the data later
- Find target date(s) for data capture. File naming scheme. Location files will be stored in Computer Center. Specification for file format.
M03: Jeng + Cissie
- Many processes will need to run on specialized, remote hardware that is not managed by a scheduling system. (ssh?)
- Report on plan for launching or checking processes needed for configuration.
- This does not need to be a completely implemented solution. Just what types of servers need to be running etc.
M04: Ayan + Jeng
- Code for project needs to be on Github in JeffersonLab organization. Relevant links on EPSCI wiki page. Skeleton documentation.
- RTDP repository created (linked to RTDP wiki page). Skeleton documentation in place with access permissions set to allow edit privileges for team members.