-
Notifications
You must be signed in to change notification settings - Fork 5
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
Expand vertex file reader to parse particle type and momenta #156
Comments
I dont think the table necessarily needs to be jagged, we just need to include the evtid (and time?). I think the option to read kinematics as a table like:
would be useful and only a relatively small modification of the current code. It might be nice to read LH5 not h5 files however. |
Yes, I meant that the number of particles originating at the vertex is not fixed. |
Started prototyping a vertex generator here: pyvertexgen. |
yes, but you will need to write it in geant4's ugly HDF5 ntuple format (are there even docs for it?). An LH5 reader would be very hard to add to the geant4 "analysis framework". |
I don't know much about it, maybe we can write a simple converter like is done for the output? |
I had a look and I am not sure how to create the Geant4 Ntuple inputs. Maybe we should go for something like the |
|
This would make remage support a wide range of external event generators through
RMGVertexFromFile
. The implementation would need to be a bit more complex than what it is right now, since the input file structure is "jagged". I guess a lot of this is already implemented inRMGGrabmayrGCReader
.Actually, "vertex" in
RMGVertexFromFile
was originally intended to refer only to vertex position. We should maybe implement all of this as an additional generator.The text was updated successfully, but these errors were encountered: