JIRIAF Meeting Aug. 31 2023

Connection Info:

You can connect using the following link (Meeting ID: 160 851 8798). (Click "Expand" to the right for details -->):

One tap mobile: US: +16692545252,,1608518798# or +16468287666,,1608518798#
Meeting URL: https://jlab-org.zoomgov.com/j/1608518798?pwd=NnU3cW1ZZFhTTUQ2Y0hIRU5JTWg0UT09&from=addon
Meeting ID: 160 851 8798
Passcode: 205601

Join by Telephone
For higher quality, dial a number based on your current location.
Dial:
US: +1 669 254 5252 or +1 646 828 7666 or +1 551 285 1373 or +1 669 216 1590 or 833 568 8864 (Toll Free)
Meeting ID: 160 851 8798

International numbers
Join by SIP
1608518798@sip.zoomgov.com
Join by H.323
161.199.138.10 (US West)
161.199.136.10 (US East)
Meeting ID: 160 851 8798
Passcode: 205601

Agenda:

1. Announcements
   1. The initial manuscript outlining our project has been submitted to the EPJ.
   2. The JIRIAF LDRD project has been chosen to receive funding for its second year of operation.
2. Update on developments related to JFE.
   1. The Angular front-end has been successfully integrated with the Java back-end, enabling efficient data exchange and form processing by using Angular forms.
      1. The backend system has successfully integrated and acknowledged the REST API requests.
   2. The back-end interraction with the JIRIAF database.
3. Progress update on developments related to JRM
   1. Is it possible to utilize SLURM/SWIF to execute the kubelet within the user space on the remote server?
   2. Can we use Singularity immage to avoid root access?
      1. Create a Singularity immage
      2. Use kubelet to create a pod that will use Singularity immage: "kubectl apply -f deployment_with_singularity_image.yaml".
   3. Run a SLURM job that runs a virtual kubelet that can run a shell cmmand.
   4. What is the procedure for running a command-line interface within an active SLURM job on a distant server, and subsequently invoking kubectl commands?
4. Preparations are underway for the upcoming integration test at NERSC.
   1. NERSC accounts and login procedures.
   2. Notable enhancements to the CLAS12 reconstruction ERSAP workflow
      1. New ET source actor (completed)
      2. New PID visualization actor (completed).
   3. Local deployment testing on indra-s2 -> ejfat1,3,5,6 successfully conducted.
   4. Progress on the ERSAP workflow container, incorporating EJFAT transport components.
5. AOT

Useful References

• JIRIAF Meetings
• JIRIAF Channel

---