There are also some smaller old disk spaces (close
to be full) which are intended as scratch area for releases, log files
and smaller nutpules etc. together with some historical old datasets:

Access Path

Physical disk

Total size (Gbtyes)

dq2 share

/nfs/surrey13/atlaswork

/a/surrey13/vol/vol0/f.atlas_data1

130

/nfs/surrey14/atlaswork

/a/surrey14/vol/vol0/f.atlas_data1

130

$ATLROOT/work/data1

/nfs/sulky51/atlaswork.u1

1240

$ATLROOT/work/data2

/nfs/sulky51/atlaswork.u2

1240

Y

Note: Again, for normal datasets you should think about the
XROOTD space first. Any dataset you wish to move into the above
disks
will be sharing with user working space which are spread out on the
last 4 disks, and the dq2 operations space on the two disks indicated
by the last column of the table. So
it is
important to take a look at the space left on the disk you are
targeting for storing samples (with command df -k .) to make sure it
won't be close to full, before shipping a large sample.
ATLROOT is /afs/slac.stanford.edu/g/atlas/ at SLAC.

New datasets at SLAC, including pileup
datasets

These datasets reside
in the XROOTD storage element at SLAC. In order to use XROOTD, please
take a look at the instructions below. Other useful links are
provided at the top of this page.

I have also slightly separated the pileup samples reconstructed
with Release 12 from those done with Release 13. The differences are
non-trivial, both in the EDM itself as well as in the pileup
digitization and reconstruction. A discussion is ongoing as to some
subtle yet perhaps very important differences in the pileup
digitization, as can be read about in this meeting: