Page History

...

This will create directory my_ana_pkg and populate it with few files and sub-directories.

6. Add analysis module (Freq: once)

This step depends on which specific analysis framework is used, currently we only support Python-based analysis and for this framework you need to execute following commands:

mkdir my_ana_pkg/src   # only if src directory does not exist yet
codegen -l pyana-module -o my_ana_pkg/src my_ana_pkg my_ana_mod

This will create file my_ana_pkg/src/my_ana_mod.py which contains boilerplate code for analysis module.

7. Modify analysis code (Freq: as much as you need)

Use your favorite editor to add or modify code the the analysis module.

8. Build (Freq: after every edit)

Run the command which builds all necessary software in your test release:

scons

9. Create configuration file (Freq: once)

In addition to analysis module the job usually needs a separate configuration file. The name and location of the file could be arbitrary. By default Python-based analysis uses file named pyana.cfg in current directory so the simplest would be to create it inside the release directory:

vi pyana.cfg

The file will contain both the names of the modules you want to load and parameters you want to pass to those modules.

10. Run the analysis (Freq: as much as you need)

Chose the data you want to process and start analysis job. For Pyana it would be something like (assuming properly prepared pyana.cfg in current directory):

pyana /reg/d/psdm/AMO/amo14410/xtc/e23-r0406-*.xtc