calibrations.xml: use HTTPS(epic-data) instead of XRootD for Low-Q2_Steering_Reconstruction.onnx#1062
calibrations.xml: use HTTPS(epic-data) instead of XRootD for Low-Q2_Steering_Reconstruction.onnx#1062
Low-Q2_Steering_Reconstruction.onnx#1062Conversation
…Steering_Reconstruction.onnx` I'm told `xrdtest` is not a great path for the file. While we are moving out (to Rucio), I'd like to suggest decommissioning the direct URL for XRootD. We have a CI action that may upload to XRootD, but we can agree that it's still okay to write to xrdtest for temporary artifacts.
There was a problem hiding this comment.
Pull request overview
Updates the ONNX calibration artifact source to avoid using the xrdtest XRootD path by switching to an HTTPS URL hosted in eic/epic-data.
Changes:
- Replaced the XRootD
root://.../xrdtest/...URL forLow-Q2_Steering_Reconstruction.onnxwith an HTTPS GitHub-hosted URL. - Keeps the existing
epic_FileLoadercaching + local path behavior intact.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
|
What is motivating moving away from XRootD? Are we already able to move to a rucio based solution, do you know what that will look like yet? |
There was an effort on cleaning up the disks, and I was told to consider a better name than xrdtest. There is no threat of these files being deleted or anything, but I'm also trying to think ahead. Move from XRootD to epic-data consolidates our points of failure in one place. As far as Rucio readiness, I discussed with @panta-123 towards Rucio paths like |
I'm told
xrdtestis not a great path for the file. While we are moving out (to Rucio), I'd like to suggest decommissioning the direct URL for XRootD.We have a CI action that may upload to XRootD, but we can agree that it's still okay to write to xrdtest for temporary artifacts.