Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Segmentation fault with RooTracker file #20

Closed
soleti opened this issue Mar 17, 2021 · 3 comments
Closed

Segmentation fault with RooTracker file #20

soleti opened this issue Mar 17, 2021 · 3 comments

Comments

@soleti
Copy link

soleti commented Mar 17, 2021

Hello,

I am trying to generate a sample of cosmic rays with edep-sim starting from a CORSIKA file. I wrote a converter that creates a RooTracker file starting from the CORSIKA output and I feed it to edep-sim using this macro:

/generator/kinematics/rooTracker/input DAT000001.root
/generator/kinematics/set rooTracker
/generator/position/set free
/generator/add

However, I get a Segmentation fault so I am not sure how to debug it further. You can find the DAT000001.root file here.

Thank you,
Roberto

@ClarkMcGrew
Copy link
Owner

I've downloaded the file if you want to delete it. I notice that it's missing a lot of the rooTracker branches. The edep-sim rootracker code assumes that all the branches are present, so I'll add traps for that (there may still be other problems).

@soleti
Copy link
Author

soleti commented Mar 18, 2021

Hi Clark, thank you, I didn't know all the branches were compulsory. Adding them indeed fixes the issue (for now, I still haven't verified if the output makes sense).

@ClarkMcGrew
Copy link
Owner

Sorry for the radio silence. I've just pushed an improved version of the EDepSimRooTrackerKinemGenerator class to master. This adds error traps while setting the branch addresses so it should catch errors sooner. It will fail if there is an error with a "critical" branch, but will continue otherwise. I'm closing the since I think this fixes the fundamental problem (failing without an error message). The fix is in 1518196.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants