You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 19 Next »

Unable to render {include} The included page could not be found.

Recommended Next Topics

  Exploring LCLS Data:

  Getting Started with Data Analysis:

  Advanced Topic:

Unable to render {include} The included page could not be found.
 
Unable to render {include} The included page could not be found.
 
 
Unable to render {include} The included page could not be found.

Accounts and Resources

A description of the LCLS computing resources can be found at the PCDS Computing page.

Setting Up the Software Environment

For the analysis software to work correctly it has to run in a correct environment. LCLS Analysis environment consists of few environment variables that either point to a location of specific directories or define some configuration options such as type of the machine, compiler versions, etc. Users do not need to set environment variables manually, instead users need to execute just one simple command which defines the complete environment. The command that needs to be run from Bourne-type shell (e.g. bash) is:

. /reg/g/psdm/etc/ana_env.sh

For C-type shell (e.g. tcsh) the command should be:

source /reg/g/psdm/etc/ana_env.csh

The above command needs to be executed every time when user logs in, for convenience it should be added to the user's shell login script. In case of bash shell here is the line of code that should be placed into ~/.bashrc file:

test -f /reg/g/psdm/etc/ana_env.sh && . /reg/g/psdm/etc/ana_env.sh

For tcsh the following code should be added to ~/.cshrc:

if ( -f /reg/g/psdm/etc/ana_env.csh ) source /reg/g/psdm/etc/ana_env.csh

Advanced setup

Environment variables and setup scripts are documented on the separate Advanced Environment Setup page.

Obtaining Kerberos ticket

If you plan to work with code repository and use commands like svnaddpkg, etc. then for authorization you will need to obtain a Kerberos ticket. Ticket can be obtained at any time after you logged in by running command kinit which will prompt your for your regular password. Kerberos ticket is valid for 25 hours after which time one needs to re-run the command. Without ticket svn will print an error message "authorization failed" when it tries to access repository (some svn commands do not require repository access).

An overview of the framework

To be completed...

Topics covered in this document tree:

  • No labels