(r6) TroubleshootingMC < NA62

TWiki>

NA62 Web>NA62MonteCarlo>TroubleshootingMC (revision 6) ~~Edit~~ Raw edit ~~Attach~~ Print version

Troubleshooting MC

This page lists the most common problems encoutered with the NA62 MC code, along with more or less general solutions.

Troubleshooting MC

GGUS tickets

Some of the problems encountered are available as GGUS tickets:

83133: CERN FTS channel problem - https://ggus.eu/ws/ticket_info.php?ticket=83133
82327: NA62 VO not in the CIC portal - https://ggus.eu/ws/ticket_info.php?ticket=82327
83159: Can't create directories on castor at RAL - https://ggus.eu/ws/ticket_info.php?ticket=83159
82901: Authz error when submitting na62 jobs to RAL - https://ggus.eu/ws/ticket_info.php?ticket=82901
81669: FTS channel for na62.vo.gridpp.ac.uk - https://ggus.eu/ws/ticket_info.php?ticket=81669
83768: Request for FTS channel from LIV to RAL - https://ggus.eu/ws/ticket_info.php?ticket=83768

Code compilation

Shared object portability issue. In Generator/GNUmakefile, define a new variable CMCLIBNAME, just above the existing CMCLIB definition:

CMCLIBNAME := libcmc.so
CMCLIB := $(CMCDIR)/libcmc.so

and then the target:

Generator: $(CMCLIB)

$(CMCLIB): $(OBJF) $(OBJC) $(COMMONOBJ) $(OBJCC)
       $(FC) -shared -Wl,-soname,$(CMCLIBNAME) -o $(CMCLIB) $^

This way the .so is linked w/o the full path, which ensures portability of the executable. Same trick in Beam/GNUmakefile, but variable names BEAMLIBNAME and BEAMLIB.

Access permissions

Many errors came from read/write access permissions either for the local software area on sites, or for storage paths on various SEs. Using two certificates - one for jobs submission (and writing to the local storage) and the other for output replication to RAL and CERN complicates things somewhat.

Topic revision: r6 - 2012-10-08 - DanProtopopescu

NA62