...

This page will describe the setup at S3DF that will be used starting in summer of '23.

Details can be found on Running at S3DF.

Overview

Many MEC user group rely on tiff files for each detector in each event/shot taken. The necessary jobs are setup in the elog/ARP and are typically automatically triggered. A standard experiment has the following jobs:

...

To reach s3df, you can access 's3dflogin' via ssh (or from a NoMachine/nx server). To be able to read data/run code, you need to go to the 'psana' machine pool (ssh psana).

Copy data to your home institution (or laptop):

To copy data to your home institute, if you used to use psexport, you will need to switch to:

s3dfdtn.slac.stanford.edu

More information can be found on Downloading Data

Working directories

in S3DF, we have a single space for each experiment. The data can be read from two different locations: the ffb and the offline. The data is first available in the ffb and will then move towards the offline. The limited size of the ffb means that data will only be available there temporarily. As rule of thumb, use the offline if data is present there.

The directory structure is as follows:

...

The ffb is a mount of the filesystem in the DRPSRCF used already in the previous years:

/sdf/data/lcls/drpsrcf/ffb/mec/<experiment>/

Be aware that data will only kept there as long as there is space. It is unlikely to contain your all of the data and data may need to be cleaned off before the end of the ongoing shift.

The results folder should hosts most of users' code, notebooks, etc. 

...