I’m running a RooFit script to create a likelihood, minimize it and set limits. However, whenever I add systematics in the calculation, root exits to command line silently somewhere inside the hesse part. Up to this point everything in the output seems normal, and it always exits around the same number of iterations (almost 2 hours in the running). I’m working through a X11 connection (but guess this is irrelevant).
Could you give me some hint or suggest some ways to monitor root’s activity?
I’d like to politely remind you that I have no hints on how to tackle this issue yet
you could use gdb to see where it exits. Additionally I will move your post to increase its visibility with the relevant developers
Meanwhile I ran it on the batch and unfortunately found what’s going on:
TERM_CPULIMIT: job killed after reaching LSF CPU usage limit.
Exited with signal termination: CPU time limit exceeded, and core dumped.
So, would someone know how to circumvent this issue?
please talk to your batch system administrators. They impose the limit; it is completely unrelated to ROOT.
You are right if it is strictly a batch issue. Anyway I’m glad to see that a CPU issue during Hesse doesn’t make anyone raise an eyebrow, so I’ll quit looking into it in programming terms.