Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • This isn't an explanation how to do the data analysis
  • This is not a Users or Reference Guide for the interactive framework

Attention pyana users!

As it's been announced earlier, the pyana framework will be phased out at some point. There is a variety of reason why:

  • first of all, as our understanding of what kind of analysis framework would work better for our users and for ourselves as developers grew over time we realized that we needed to develop a tool which would have a better interface to the data, a better internal architecture and be much easy to maintain and extend for new data types of LCLS instruments. Hence we ended up with psana.
  • for its users, the psana framework has a number of advantages, among which:
    • better API to the data
    • a possibility of writing (mixing) modules in C++ and Python. Modules written in different languages will still the same data, and they can also exchange data within the framework.
    • supporting data sets in both XTC and HDF5
    • an ability to read the "live" files (while they're being recorded by the DAQ system or data movers)
    • and ability to read data from shared memory of the DAQ (DSS) machines

The last two features open are opening an interesting possibility of using psana for real-time monitoring of data while benefiting from reusing
the same code which might be developed for the traditional OFFLINE processing/analysis.

Here be the section body.

Subsection 1.1.1

Inner section 1.1.1.1

And this is where we're supposed to have the main material of the section.

Section 1.2

Here be the section body.

Subsection 1.2.1

Inner section 1.1.1.2

Here be the body

Chapter 2

Section 2.1

Subsection 2.1.1

...

Setting up your environment

The location of examples

We put all examples for today's session at the following diretory:

Code Block

/reg/g/psdm/tutorials

Data files used in the examples

In order to make our examples as close to the "real" analysis environment as possible we chose to create 6 pseudo experiments (one per instrument):

  • AMO/amotut13
  • SXR/sxrtut13
  • XPP/xpptut13
  • XCS/xcstut13
  • CXI/cxitut13
  • MEC/mectut13

Each experiment has the standard structure of directories at the OFFLINE storage:

Code Block

ls -al ls -al /reg/d/psdm/XPP/xpptut13/
drwxr-sr-x   8 psdatmgr ps-data 4096 Jun  4 12:02 .
drwxrwsr-x  30 psdatmgr ps-data 4096 Jun  4 12:02 ..
drwxrwsr-x+  3 psdatmgr ps-data 4096 Jun  5 10:53 calib
drwxrwsr-x+  2 psdatmgr ps-data 4096 Jun  4 12:02 ftc
drwxr-sr-x   2 psdatmgr ps-data 4096 Jun  6 16:41 hdf5
drwxrwsr-x+  2 psdatmgr ps-data 4096 Jun  4 12:02 res
drwxrwsr-x+  2 psdatmgr ps-data 4096 Jun  4 12:03 scratch
drwxr-sr-x   2 psdatmgr ps-data 4096 Jun  6 16:33 xtc


ls -al /reg/d/psdm/XPP/xpptut13/hdf5/
drwxr-sr-x 2 psdatmgr ps-data       4096 Jun  6 16:41 .
drwxr-sr-x 8 psdatmgr ps-data       4096 Jun  4 12:02 ..
-r--r--r-- 1 psdatmgr ps-data 1765036151 Jun  6 16:39 xpptut13-r0178.h5
-r--r--r-- 1 psdatmgr ps-data  394528165 Jun  6 16:39 xpptut13-r0179.h5
-r--r--r-- 1 psdatmgr ps-data  128185688 Jun  6 16:39 xpptut13-r0180.h5
-r--r--r-- 1 psdatmgr ps-data  912811050 Jun  6 16:39 xpptut13-r0181.h5

And yes, one can also see these experiments in the Web Portal.