User Tools

Site Tools




Account Request

The CNAF is the main computing center of the INFN. In order to access the computing resources you need an account that can be request following the instructions provided here. An example of the form is here.

Account Password Reset

In case you lost your password, just send an email to indicating your account and asking for password reset.

CNAF User Guide

CNAF provides a very usefull user guide for Tier1.


CNAF provides a very usefull user guide for Monitoring. Monitoring is provide by a Grafana.

Below are direct link to:

The overall status of GPFS can be found here


In order to access any CNAF machine, you first have to login in From there you can login to ICARUS UIs machines:


The filesystems are:

  • /cvmfs: CernVM File System (CernVM-FS)
  • /storage/gpfs_archive/icarus: tape (not accessible from UIs)
  • /storage/gpfs_data/icarus/local: disk
  • /storage/gpfs_data/icarus: disk (not writable from UIs apart fileset: /storage/gpfs_data/icarus/local)
  • /opt/exp_software/icarus: dedicated to software
  • /home/ICARUS: home directories

The disk area readable from UIs are:

  • /storage/gpfs_data/icarus/plain
  • /storage/gpfs_data/icarus/plain/user/<username>

Personal Certificate and VO Enrollment

To read and write the storage areas using gfal tools first you need be enrolled in the ICARUS experiment VO: The enrollment requires a valid personal certificate. Instructions on how to obtain it are here. Once you have a valid certificate, you have to install it in a browser and point (with that browser) to the Enrollment Url reported in operation portal site. Select the valid personal certificate just installed when asked for by the browser. Once you have filled the enrollment form, you have to wait for the VO manager to approve your enrollment.

Read/Write storage areas

Once enrolled, you need create a proxy. Instructions on how to create it are here.

The usefull tools to handle files are:

  • gfal-ls: List information about the file
  • gfal-copy: Copy file
  • gfal-rm: Remove file
  • gfal-mkdir: Create a directory

Detailed information about gfal utils can be found here

Job submission

Instructions on how to submit jobs are here. Be aware if the job needs your certificate (e.g. if the job uses gfal tools) add the following lines to the submitting script:

x509userproxy           = $(X509_USER_PROXY)
use_x509userproxy       = true

In a nutshell:

  • Launch job:
condor_submit -name -spool run.sub
  • Monitor user jobs:
condor_q -name <user>
  • Monitor single job:
condor_q -name <cluster id>
  • Deeper monitoring of a job:
condor_q -better-analyze -name <cluster id>
  • Get the output:
condor_transfer_data -name <cluster id>

Submitting simple test production

To test everything is working correctly, clone this repository in your home and follow the istructions in "Launch the test production".


Here is the machinary to submit a production.

Setup icaruscode

In order to setup icarucode version vXX_YY_ZZ with qualifier eNN:PPP, just do:

source /cvmfs/
setup icaruscode vXX_YY_ZZ -q eNN:PPP

Install icaruscode for development

mkdir -p ${wd}
cd ${wd}
source /cvmfs/
setup icaruscode ${vers} -q ${qual}
export MRB_PROJECT=icaruscode
mrb n -v ${vers} -q ${qual}
source ${wd}/localProducts_icaruscode_${vers}_${qual/:/_}/setup
cd srcs
mrb g -t ${vers} icaruscode
mrb install -j 2

Create proxy with fermilab VOMS extensions

Being fnal_user your username at FNAL:

source /cvmfs/
setup cigetcert
cigetcert -i 'Fermi National Accelerator Laboratory' --myproxyretrievers='/DC=org/DC=incommon/C=US/ST=Illinois/O=Fermi Research Alliance/CN=(fifebatch|(hepcjobsub0(1|2))|jobsubdevgpvm01)' --myproxyhours=24 --hours=672 -u <fnal_user>
voms-proxy-init -noregen -rfc -voms 'fermilab:/fermilab/icarus/Role=Analysis'


It is possible to use samweb at CNAF. First create a proxy with fermilab VOMS extensions, then:

source /cvmfs/
setup fife_utils

In the following links to webpage with usefull info:

Locate a file

To locate a file which filename is filename.root, do:

md5=$(echo -n "user.icaruspro:${filename}" | md5sum)
ls -lrt /storage/gpfs_data/icarus/plain/user/icaruspro/${md5:0:2}/${md5:2:2}/${filename}  

Example: how to get the list of the file paths for a samweb selection

  • First, you get the list of the files from samweb
samweb -e icarus list-files "run_number = 8460 and data_stream = bnbmajority and data_tier = raw" > list_filenames.txt
  • Then, you have to convert the filename into filepath using the following commands:
for filename in $(cat list_filenames.txt); 
  md5=$(echo -n "user.icaruspro:${filename}" | md5sum); 
  if [ -f ${filepath} ]; 
    echo ${filepath} >> list_filepaths.txt; 
    echo ${filename} >> list_missing_files.txt; 
  • You will have:
    • the list of the path of the existing files in list_filepaths.txt
    • the list of the name of the missing files in list_missing_files.txt

File transfer from FNAL machines

To be able to copy files from FNAL to CNAF you need (only once):

  • to be enrolled in the VO. See session above.
  • copy ~/.globes folder in your home in the FNAL machines, using the following command on the CNAF machines:
scp -r ~/.globes "fnal_user"
  • to create vomses folder in your home in the FNAL machines, using the following command on the FNAL machines:
mkdir -p ~/vomses
  • copy the content of /etc/vomses in the CNAF machines in the created folder, using the following command on the CNAF machines:
scp -r /etc/vomses/* "fnal_user"

Then, you do, ignoring possible errors:

voms-proxy-init --voms --valid 72:00 -vomses ~/vomses/
gfal-ls srm://<space token>

where <space token> can be:

  • icarus for tape (i.e. /storage/gpfs_archive/icarus)
  • icarusplain for plain area on disk (i.e. /storage/gpfs_data/icarus/plain) [deprecated]
  • icarusdata for not plain area on disk (i.e. /storage/gpfs_data/icarus)

File transfer\access from CNAF machines

  • First, you create a proxy with fermilab VOMS extensions, then you should be able to copy files from FNAL:
xrdcp xroots:// .
xrdcp file-test.root xroots://
gfal-copy file-test.root
  • you can also access remote file:
$> root -l
root [0] TFile *_file0 = TFile::Open("xroot://")

TITUS Event Display

source /opt/exp_software/icarus/titus/titus_v09_37_02_06/ -i <file.root>


For any kind of support refer to

progetti/icarus/home.txt · Last modified: 2023/05/29 07:38 by