Using NOvASoft on the GPVM nodes » History » Version 8

Version 7 (Mayly Sanchez, 05/23/2011 02:29 PM) → Version 8/38 (Gavin Davies, 06/08/2011 04:54 PM)


h1. Using NOvASoft on the GPVM nodes

h2. Available nodes

The new GPVM nodes are virtual machines that are accessible by the intensity frontier experiments. The list of nodes for NOvA is


These nodes will give us access to the FermiGrid.

If you have just received notification that you have an account on one of these machines, your login shell is likely bash. If you prefer a different login shell you need to submit a ServiceDesk ticket to get it changed.

h2. Kerberos

Users must have a valid kerberos ticket to access Fermilab computing at the time an attempt to log into a Fermilab machine. The ticket is obtained by executing the following command at a terminal prompt:

$ kinit principal @FNAL.GOV

where principal is the user's kerberos principal. If a user is attempting to access the repository from a non-Fermilab machine, the following lines must be in the users' user's .ssh/config:

Host *
ForwardAgent yes
ForwardX11 yes
ForwardX11Trusted yes
GSSAPIAuthentication yes
GSSAPIDelegateCredentials yes

In case of trouble when connecting via ssh (permission denied error) the reason can be in the OpenSSH client, the following client is compatible with Fermilab Kerberos authentification:
OpenSSH_4.3p2, OpenSSL 0.9.8e-fips-rhel5 01 Jul 2008

h2. Setting up NOvASoft

There is a setup script provided to get the environment ready for using NOvASoft on these machines. To use it, one does (for tags S11.04.30 and later including development):
$ source


If you are using tagged release S11.04.09 and earlier do:

@$source /grid/fermiapp/nova/novaart/novasoft/releases/development/setup/setup_novasoft_ifcluster.(c)sh@

The above commands will set your $PATH and $LD_LIBRARY_PATH variables as well as the variables that define the locations of the necessary external packages.

While the public release of the code is located in /grid/fermiapp/nova/novaart/novasoft/releases/development/, the average user should _never_ make any files in that directory. It has limited space and is only for code releases. Instead, use the disk space described in the next section.

h2. Disk Space

The user space for those logging into these nodes is


This is where users should store their test releases as well as any analysis files.

Any data or Monte Carlo files for general consumption by the experiment should be stored in


When operating on the grid, the /data directories cannot have executables run from them, executables can only be run from the /app directories.