Using Skeleton functions in Root and Paw (2)

Thank you for the previous replies, I know how do the analogous analysis in PAW. Perhaps the difference in the execution time is due to the fact that the loop in PAW is in the command I give in the environment i.e.

PAW>nt/plot IDntuple.variable $cuts.and.loop.f=1

while in Root I execute a macro (see attachment) i.e.

root [1].x loop.C

I can’t keep the Tree files in a public area because they are that of the experiment I’m working on, so I think they are “internal”
(the experiment is KASCADE-Grande)

Again thanks for any suggestion,
cuts-exp-chains.C (6.46 KB)

I have no answer about the ROOT vs PAW performance problem. But I can answer the PAW question you asked. The PAW command you are looking for is “UWFUNC”. Have a look to the help for details.

Anyway, it would be better to stick with ROOT and unserstand the difference in speed.

Could you put in some public area the ROOT data file as well as the shortest possible script reproducing your speed problem?


[quote]while in Root I execute a macro (see attachment) i.e.
root [1].x loop.C [/quote]You are running your main loop in the interpreter. To speed things up you can simply compile your code (for example via ACliC). You will of course need to update the code to change it from an unnamed macro to a name macro (add the proper #include, the code should be the body of a function name ‘loop’.

It looks like you generated the skeleton using MakeCode. I strongly recommend you use either MakeSelector or MakeProxy instead. (for one thing those skeleton are compile ready :slight_smile: )