Table of Contents

Moving data between the GRID and Aurora

The recommended mode to move data is using the special fs2-hep storage node.
The SLURM method described below is deprecated, to be used only if the other method doesn't work.

Using GRID tools on ''fs2-hep'' (recommended)

From the GRID point of view, our local GRID storage is a storage element and from ATLAS information system
it has a special name, SE-SNIC-T2_LUND_LOCALGROUPDISK . I will use this name in the documentation below.
Such storage can be accessed in many ways and protocols, or endpoints, depending on what task you need to carry on. More details about this below.
If you already know how datatransfer works in ATLAS, just follow this quick reference card by Oxana:

Downloading data from any ATLAS SE to Aurora

If you omit the –rse parameter in any of the commands above, rucio will automatically search for the best Storage Element. However the speed and duration of such download is not guaranteed. Please ask the collaboration for their policies regarding such transfers.

Uploading data from Aurora to any other GRID Storage Element

Using SLURM Scripts (inefficient, deprecated)

This was a workaround when there was no data mover frontend (fs2-hep). The reason why this technique is discontinued is because it uses the 1GB link of the node to perform the download, while fs2-hep has a dedicated 10GB link just to do the transfers.

Particle Physicists were submitting grid downloads using the SLURM batch system with
a script created by Will Kalderon. He kindly provided a link to the scripts:

It is mainly intended for Particle Physicist and if you need to access the script you should request
clearance to Will. If you see a 404 not found error when clicking the link it means you have no clearance.