Page History
...
Either source the the environment setup script on every logon: . /reg/g/psdm/etc/ana_env.sh or add this command to the shell login script as explained in Account Setup section.
3. Kerberos ticket (Freq: every day or as necessary)
If you work with code repository and use commands like svn, addpkg, etc. then for authorization you will need to obtain a Kerberos ticket. Ticket can be obtained at any time by running command kinit which will prompt your for your regular password. Ticket is valid for 25 hours after which time one needs to re-run the command.
4. Create a test release (Freq: once)
Releases are explained in Packages and Releases section. Create new test release with the command like this:
...
Below we refer to this directory as a "test release". Usually separate analyses use separate test releases, and each test release should bear unique name if they are located in the same directory.
...
5. Change to the test release (Freq: every logon or whenever needed)
| Code Block |
|---|
cd analisys-rel sit_setup |
The last sit_setup command is very important and must be executed from the release directory every time you change the directory.
...
6. Create new analysis package (Freq: once)
Choose sufficiently unique name for your analysis package and create the package.
...
| Code Block |
|---|
.../analisys-rel/
./my_ana_pkg/
SConscript
doc/
README
ChangeLog
|
...
7. Add analysis module (Freq: once)
This step depends on which specific analysis framework is used:
...
| Note |
|---|
Like with the package name it's better to use names containing letters, digits, and underscores only. |
...
8. Modify analysis code (Freq: as much as you need)
Use your favorite editor to add or modify code the analysis module. For Python modules see section Writing User Modules in Pyana User Manual for examples. For C++ modules see Psana User Manual for examples.
...
9. Build (Freq: after every edit)
Run the command which builds all necessary software in your test release:
| Code Block |
|---|
scons |
...
10. 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:
...
The file will contain both the names of the modules you want to load and parameters you want to pass to those modules, exact content of the configuration file is explained in Pyana User Manual.
...
11. 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):
...
Overview
Content Tools