get_source_id break in both analyzer.C and ecal.C

[ghost]

When running the daqprocessor_single_calibrate.py I get an error
*** Break *** segmentation violation
after both analyzer.C and ecal.C went into get_source_id. I figured out that the following lines seem to break down (which are identical in both files)

analyzer.C: line 822
ecal.C: line 144

_f_tmp->cd("info/active");

Peter also had a look at it but we couldn't figure out what's wrong, maybe the code is trying to get into the directory info/active which isn't there, but we don't know where it would be either. Has anyone encountered this before and knows a solution? Thanks!

[acolijn]

Did you check in the root file whether the directory “info/active” exists?

AP

On 19 Apr 2016, at 11:33, Magnus Gienal [email protected] wrote:

When running the daqprocessor_single_calibrate.py I get an error
*** Break *** segmentation violation
after both analyzer.C and ecal.C went into get_source_id. I figured out that the following lines seem to break down (which are identical in both files)

analyzer.C: line 822
ecal.C: line 144

_f_tmp->cd("info/active");

Peter also had a look at it but we couldn't figure out what's wrong, maybe the code is trying to get into the directory info/active which isn't there, but we don't know where it would be either. Has anyone encountered this before and knows a solution? Thanks!

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub #3

[ghost]

Whick root file do you mean? There is no root file created in the output directory if that's the one I should look for.

Magnus

[acolijn]

the ecal.C and analyzer.C use a root file (or chain) as an input for the calibration and analysis actions.

In any case the _f_tmp->cd(“info/active”) command is trying to change directory…

AP

On 19 Apr 2016, at 13:43, Magnus Gienal [email protected] wrote:

Whick root file do you mean? There is no root file created in the output directory if that's the one I should look for.

Magnus

—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub #3 (comment)

[cassie-fletcher]

It sounds like get_source_id is trying to access a path that doesn't exist,
which is why it is seg faulting. So, you should check your file paths
(should be hardcoded in daqprocessor_single_calibrate.py) and see if these
match the path of the tree get_source_id is trying to read.

On Tue, Apr 19, 2016 at 7:59 AM, Auke Colijn [email protected]
wrote:

the ecal.C and analyzer.C use a root file (or chain) as an input for the
calibration and analysis actions.

In any case the _f_tmp->cd(“info/active”) command is trying to change
directory…

AP

On 19 Apr 2016, at 13:43, Magnus Gienal [email protected]
wrote:

Whick root file do you mean? There is no root file created in the output
directory if that's the one I should look for.

Magnus

—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub <
https://github.com/modexp/analysis/issues/3#issuecomment-211875037>

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
#3 (comment)

[ghost]

Thank you all for your efforts! It turned out that there was something wrong on a more fundamental level with my daqana installation. It's still not working properly, but there is at least some data I can now start to have a look on.

[cassie-fletcher]

Something regarding the root installation? You should be more specific so
we can identify the problem if it comes up again. :)

On Thu, Apr 21, 2016 at 10:07 AM, Magnus Gienal [email protected]
wrote:

Thank you all for your efforts! It turned out that there was something
wrong on a more fundamental level with my daqana installation. It's still
not working properly, but there is at least some data I can now start to
have a look on.

—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub
#3 (comment)

[ghost]

So, the major issue was that my daqana file wasn't compiled correctly. After solving this I now at least get a .root file in the calibration folder.
But there is still a crash in the whole run I have not yet figured out what could be the cause. The analyzer script drops dead when it tries to reach the slow file .sroot which he can't find, but should have been created according to some output earlier in the run. So maybe I still missed some hardcoded part in the code, although I went through it with Peter yesterday.
I will go through it again and keep you updated. It's my first time working with such a big code/scripts, so I may overlooking something obvious.