Page History
...
- Set up your release work directory:
You should always run this code from your own release working directory. It might work from other directories, but be aware that configuration files will be written to your current directory. Look out for files with names xb_pyana_XXXX.cfg, where XXXX is a random four-digit number. You can use them to run pyana directly from the command line. But they accumulate, so you might want to remove these regularly...
See the Account Setup section to set up the analysis environment. Set up your release working directory frompslogin
:Code Block none none [user@pslogin ~] newrel ana-current myrelease [user@pslogin ~] cd myrelease [user@pslogin myrelease] sit_setup
- Add the package:
Next you want to add the XtcExplorer package to your analysis release. Once the package exists in the release, this will be optional. But you might want to have a local copy anyway to be able to edit the source files to tweak your analysis.
Note that you need to have an afs token to check out the package, so if you didn't already you need to run 'kinit' first:
Now you're ready to check out the package and "compile":Code Block none none [user@pslogin myrelease] kinit Password for user@SLAC.STANFORD.EDU:
Note! You can omit the "tag" (VXX-XX-XX) to get the latest and greatest version in the svn repository, but this may look different from described here, and might have more problems.Code Block none none [user@pslogin myrelease] addpkg XtcExplorer V00-01-0203 [user@pslogin myrelease] scons
- Run the program:
Launch the GUI with the command 'xtcexplorer' and optionally give the input xtc files that you want to read as arguments. You can also browse to find files after launching the browser.
To have access to the xtc files, you need to login topsana
for this:Code Block [user@psanaXXX myrelease] sit_setup [user@psanaXXX myrelease] xtcexplorer /reg/d/psdm/CXI/cxi22010/xtc/e60-r0465-s0*
...
Overview
Content Tools