common HDDM interface for generator level output #43
Assignees
Comments
|
Hello Sean and all,
I am working on the following utility that reads in any hddm file and
prints out in plain text what was generated and what happened to the
primaries. I have already written this program, and would like your
feedback on how it works. This is a sample output from it, at present,
reading from a bggen generated hddm file. The vertex is 0,0,65 because it
has not yet been simulated. Further decay vertices will show up as soon as
these events are simulated. They will appear under their parent particle in
the listing as further indented lines. Please let me know if there are
improvements you would like to see to this scheme. I was planning to
release this over the weekend, but got distracted by another HDGeant4 bug.
Run 50141, event 2: Photon (8.564 GeV) Proton (0.938 GeV) ->
Pi+, 1.104 GeV, beta=(-0.412,-0.035,0.902)
Pi-, 6.723 GeV, beta=(0.070,0.043,0.996)
Proton, 1.257 GeV, beta=(-0.011,-0.103,0.658)
Pi+, 0.211 GeV, beta=(0.029,-0.544,-0.516)
Pi-, 0.207 GeV, beta=(-0.052,-0.017,0.737)
in the LiqH target (0.000,0.000,65.000)cm at 0.000 ns
Run 50141, event 4: Photon (8.452 GeV) Proton (0.938 GeV) ->
Pi+, 1.633 GeV, beta=(-0.161,0.050,0.982)
Pi-, 1.795 GeV, beta=(0.421,-0.247,0.869)
Pi0, 0.236 GeV, beta=(0.075,-0.060,0.815)
Eta, 3.735 GeV, beta=(-0.045,0.043,0.987)
Neutron, 1.703 GeV, beta=(-0.243,-0.012,0.798)
Pi+, 0.289 GeV, beta=(0.243,0.823,0.174)
in the liqH target (0.000,0.000,65.000)cm at 0.000 ns
Run 50141, event 6: Photon (8.460 GeV) Proton (0.938 GeV) ->
KShort, 2.929 GeV, beta=(-0.080,-0.025,0.982)
KLong, 4.261 GeV, beta=(-0.033,0.053,0.991)
Sigma+, 1.517 GeV, beta=(0.164,-0.084,0.593)
KLong, 0.691 GeV, beta=(0.183,-0.041,0.668)
in the GlueX spectrometer (0.000,0.000,65.000)cm at 0.000 ns
…On Tue, Mar 5, 2019 at 4:18 PM Sean Dobbs ***@***.***> wrote:
From Eugene:
A common class for writing out HDDM thrown-level output would be very
useful.
This could be implemented as a standalone library.
Sean's suggestion: it would also be good to have a standalone program to
do this as well from some common input format
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#43>, or mute the thread
<https://github.com/notifications/unsubscribe-auth/AHeFWM1qMDsimC27zlcjoBPuaxGbTXnsks5vTt8WgaJpZM4bfhQ3>
.
|
|
Hi Richard,
That sounds like a great utility. For the record, Eugene's request was
more specifically about writing to HDDM, for example, for people writing
their own event generator.
…---Sean
On Tue, Mar 5, 2019 at 5:08 PM Richard Jones <[email protected]>
wrote:
Hello Sean and all,
I am working on the following utility that reads in any hddm file and
prints out in plain text what was generated and what happened to the
primaries. I have already written this program, and would like your
feedback on how it works. This is a sample output from it, at present,
reading from a bggen generated hddm file. The vertex is 0,0,65 because it
has not yet been simulated. Further decay vertices will show up as soon as
these events are simulated. They will appear under their parent particle in
the listing as further indented lines. Please let me know if there are
improvements you would like to see to this scheme. I was planning to
release this over the weekend, but got distracted by another HDGeant4 bug.
Run 50141, event 2: Photon (8.564 GeV) Proton (0.938 GeV) ->
Pi+, 1.104 GeV, beta=(-0.412,-0.035,0.902)
Pi-, 6.723 GeV, beta=(0.070,0.043,0.996)
Proton, 1.257 GeV, beta=(-0.011,-0.103,0.658)
Pi+, 0.211 GeV, beta=(0.029,-0.544,-0.516)
Pi-, 0.207 GeV, beta=(-0.052,-0.017,0.737)
in the LiqH target (0.000,0.000,65.000)cm at 0.000 ns
Run 50141, event 4: Photon (8.452 GeV) Proton (0.938 GeV) ->
Pi+, 1.633 GeV, beta=(-0.161,0.050,0.982)
Pi-, 1.795 GeV, beta=(0.421,-0.247,0.869)
Pi0, 0.236 GeV, beta=(0.075,-0.060,0.815)
Eta, 3.735 GeV, beta=(-0.045,0.043,0.987)
Neutron, 1.703 GeV, beta=(-0.243,-0.012,0.798)
Pi+, 0.289 GeV, beta=(0.243,0.823,0.174)
in the liqH target (0.000,0.000,65.000)cm at 0.000 ns
Run 50141, event 6: Photon (8.460 GeV) Proton (0.938 GeV) ->
KShort, 2.929 GeV, beta=(-0.080,-0.025,0.982)
KLong, 4.261 GeV, beta=(-0.033,0.053,0.991)
Sigma+, 1.517 GeV, beta=(0.164,-0.084,0.593)
KLong, 0.691 GeV, beta=(0.183,-0.041,0.668)
in the GlueX spectrometer (0.000,0.000,65.000)cm at 0.000 ns
On Tue, Mar 5, 2019 at 4:18 PM Sean Dobbs ***@***.***>
wrote:
> From Eugene:
>
> A common class for writing out HDDM thrown-level output would be very
> useful.
> This could be implemented as a standalone library.
>
> Sean's suggestion: it would also be good to have a standalone program to
> do this as well from some common input format
>
> —
> You are receiving this because you are subscribed to this thread.
> Reply to this email directly, view it on GitHub
> <#43>, or mute the
thread
> <
https://github.com/notifications/unsubscribe-auth/AHeFWM1qMDsimC27zlcjoBPuaxGbTXnsks5vTt8WgaJpZM4bfhQ3
>
> .
>
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
<#43 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABIJaj46yBQMt9xOCvXHEKq8gzk0tl-Qks5vTurRgaJpZM4bfhQ3>
.
|
|
Sean,
Would it be useful for me to write a short example program for writing an
event generator?
…-Richard
On Tue, Mar 5, 2019 at 5:11 PM Sean Dobbs ***@***.***> wrote:
Hi Richard,
That sounds like a great utility. For the record, Eugene's request was
more specifically about writing to HDDM, for example, for people writing
their own event generator.
---Sean
On Tue, Mar 5, 2019 at 5:08 PM Richard Jones ***@***.***>
wrote:
> Hello Sean and all,
>
> I am working on the following utility that reads in any hddm file and
> prints out in plain text what was generated and what happened to the
> primaries. I have already written this program, and would like your
> feedback on how it works. This is a sample output from it, at present,
> reading from a bggen generated hddm file. The vertex is 0,0,65 because it
> has not yet been simulated. Further decay vertices will show up as soon
as
> these events are simulated. They will appear under their parent particle
in
> the listing as further indented lines. Please let me know if there are
> improvements you would like to see to this scheme. I was planning to
> release this over the weekend, but got distracted by another HDGeant4
bug.
>
> Run 50141, event 2: Photon (8.564 GeV) Proton (0.938 GeV) ->
> Pi+, 1.104 GeV, beta=(-0.412,-0.035,0.902)
> Pi-, 6.723 GeV, beta=(0.070,0.043,0.996)
> Proton, 1.257 GeV, beta=(-0.011,-0.103,0.658)
> Pi+, 0.211 GeV, beta=(0.029,-0.544,-0.516)
> Pi-, 0.207 GeV, beta=(-0.052,-0.017,0.737)
> in the LiqH target (0.000,0.000,65.000)cm at 0.000 ns
> Run 50141, event 4: Photon (8.452 GeV) Proton (0.938 GeV) ->
> Pi+, 1.633 GeV, beta=(-0.161,0.050,0.982)
> Pi-, 1.795 GeV, beta=(0.421,-0.247,0.869)
> Pi0, 0.236 GeV, beta=(0.075,-0.060,0.815)
> Eta, 3.735 GeV, beta=(-0.045,0.043,0.987)
> Neutron, 1.703 GeV, beta=(-0.243,-0.012,0.798)
> Pi+, 0.289 GeV, beta=(0.243,0.823,0.174)
> in the liqH target (0.000,0.000,65.000)cm at 0.000 ns
> Run 50141, event 6: Photon (8.460 GeV) Proton (0.938 GeV) ->
> KShort, 2.929 GeV, beta=(-0.080,-0.025,0.982)
> KLong, 4.261 GeV, beta=(-0.033,0.053,0.991)
> Sigma+, 1.517 GeV, beta=(0.164,-0.084,0.593)
> KLong, 0.691 GeV, beta=(0.183,-0.041,0.668)
> in the GlueX spectrometer (0.000,0.000,65.000)cm at 0.000 ns
>
>
> On Tue, Mar 5, 2019 at 4:18 PM Sean Dobbs ***@***.***>
> wrote:
>
> > From Eugene:
> >
> > A common class for writing out HDDM thrown-level output would be very
> > useful.
> > This could be implemented as a standalone library.
> >
> > Sean's suggestion: it would also be good to have a standalone program
to
> > do this as well from some common input format
> >
> > —
> > You are receiving this because you are subscribed to this thread.
> > Reply to this email directly, view it on GitHub
> > <#43>, or mute the
> thread
> > <
>
https://github.com/notifications/unsubscribe-auth/AHeFWM1qMDsimC27zlcjoBPuaxGbTXnsks5vTt8WgaJpZM4bfhQ3
> >
> > .
> >
>
> —
> You are receiving this because you were assigned.
> Reply to this email directly, view it on GitHub
> <
#43 (comment)
>,
> or mute the thread
> <
https://github.com/notifications/unsubscribe-auth/ABIJaj46yBQMt9xOCvXHEKq8gzk0tl-Qks5vTurRgaJpZM4bfhQ3
>
> .
>
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#43 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AHeFWNwsg7E_8mlP3UxcewL8vQJv9lCxks5vTuuhgaJpZM4bfhQ3>
.
|
|
Richard,
That sounds like a good idea. The only requirement is that the HDDM output
be modular (or at least that is what I got from the discussion at the
meeting!)
…---Sean
On Tue, Mar 5, 2019 at 10:41 PM Richard Jones <[email protected]>
wrote:
Sean,
Would it be useful for me to write a short example program for writing an
event generator?
-Richard
On Tue, Mar 5, 2019 at 5:11 PM Sean Dobbs ***@***.***>
wrote:
> Hi Richard,
>
> That sounds like a great utility. For the record, Eugene's request was
> more specifically about writing to HDDM, for example, for people writing
> their own event generator.
>
> ---Sean
>
> On Tue, Mar 5, 2019 at 5:08 PM Richard Jones ***@***.***>
> wrote:
>
> > Hello Sean and all,
> >
> > I am working on the following utility that reads in any hddm file and
> > prints out in plain text what was generated and what happened to the
> > primaries. I have already written this program, and would like your
> > feedback on how it works. This is a sample output from it, at present,
> > reading from a bggen generated hddm file. The vertex is 0,0,65 because
it
> > has not yet been simulated. Further decay vertices will show up as soon
> as
> > these events are simulated. They will appear under their parent
particle
> in
> > the listing as further indented lines. Please let me know if there are
> > improvements you would like to see to this scheme. I was planning to
> > release this over the weekend, but got distracted by another HDGeant4
> bug.
> >
> > Run 50141, event 2: Photon (8.564 GeV) Proton (0.938 GeV) ->
> > Pi+, 1.104 GeV, beta=(-0.412,-0.035,0.902)
> > Pi-, 6.723 GeV, beta=(0.070,0.043,0.996)
> > Proton, 1.257 GeV, beta=(-0.011,-0.103,0.658)
> > Pi+, 0.211 GeV, beta=(0.029,-0.544,-0.516)
> > Pi-, 0.207 GeV, beta=(-0.052,-0.017,0.737)
> > in the LiqH target (0.000,0.000,65.000)cm at 0.000 ns
> > Run 50141, event 4: Photon (8.452 GeV) Proton (0.938 GeV) ->
> > Pi+, 1.633 GeV, beta=(-0.161,0.050,0.982)
> > Pi-, 1.795 GeV, beta=(0.421,-0.247,0.869)
> > Pi0, 0.236 GeV, beta=(0.075,-0.060,0.815)
> > Eta, 3.735 GeV, beta=(-0.045,0.043,0.987)
> > Neutron, 1.703 GeV, beta=(-0.243,-0.012,0.798)
> > Pi+, 0.289 GeV, beta=(0.243,0.823,0.174)
> > in the liqH target (0.000,0.000,65.000)cm at 0.000 ns
> > Run 50141, event 6: Photon (8.460 GeV) Proton (0.938 GeV) ->
> > KShort, 2.929 GeV, beta=(-0.080,-0.025,0.982)
> > KLong, 4.261 GeV, beta=(-0.033,0.053,0.991)
> > Sigma+, 1.517 GeV, beta=(0.164,-0.084,0.593)
> > KLong, 0.691 GeV, beta=(0.183,-0.041,0.668)
> > in the GlueX spectrometer (0.000,0.000,65.000)cm at 0.000 ns
> >
> >
> > On Tue, Mar 5, 2019 at 4:18 PM Sean Dobbs ***@***.***>
> > wrote:
> >
> > > From Eugene:
> > >
> > > A common class for writing out HDDM thrown-level output would be very
> > > useful.
> > > This could be implemented as a standalone library.
> > >
> > > Sean's suggestion: it would also be good to have a standalone program
> to
> > > do this as well from some common input format
> > >
> > > —
> > > You are receiving this because you are subscribed to this thread.
> > > Reply to this email directly, view it on GitHub
> > > <#43>, or mute the
> > thread
> > > <
> >
>
https://github.com/notifications/unsubscribe-auth/AHeFWM1qMDsimC27zlcjoBPuaxGbTXnsks5vTt8WgaJpZM4bfhQ3
> > >
> > > .
> > >
> >
> > —
> > You are receiving this because you were assigned.
> > Reply to this email directly, view it on GitHub
> > <
>
#43 (comment)
> >,
> > or mute the thread
> > <
>
https://github.com/notifications/unsubscribe-auth/ABIJaj46yBQMt9xOCvXHEKq8gzk0tl-Qks5vTurRgaJpZM4bfhQ3
> >
> > .
> >
>
> —
> You are receiving this because you commented.
> Reply to this email directly, view it on GitHub
> <
#43 (comment)
>,
> or mute the thread
> <
https://github.com/notifications/unsubscribe-auth/AHeFWNwsg7E_8mlP3UxcewL8vQJv9lCxks5vTuuhgaJpZM4bfhQ3
>
> .
>
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
<#43 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABIJaonKcw5yBtjZIRfj-XTX5u0Ur5ziks5vTzjXgaJpZM4bfhQ3>
.
|
|
Hello Sean,
What do you mean by "modular". Would a python module fit that description?
…-Richard
On Tue, Mar 5, 2019 at 10:53 PM Sean Dobbs ***@***.***> wrote:
Richard,
That sounds like a good idea. The only requirement is that the HDDM output
be modular (or at least that is what I got from the discussion at the
meeting!)
---Sean
On Tue, Mar 5, 2019 at 10:41 PM Richard Jones ***@***.***>
wrote:
> Sean,
>
> Would it be useful for me to write a short example program for writing an
> event generator?
>
> -Richard
>
> On Tue, Mar 5, 2019 at 5:11 PM Sean Dobbs ***@***.***>
> wrote:
>
> > Hi Richard,
> >
> > That sounds like a great utility. For the record, Eugene's request was
> > more specifically about writing to HDDM, for example, for people
writing
> > their own event generator.
> >
> > ---Sean
> >
> > On Tue, Mar 5, 2019 at 5:08 PM Richard Jones ***@***.***
>
> > wrote:
> >
> > > Hello Sean and all,
> > >
> > > I am working on the following utility that reads in any hddm file and
> > > prints out in plain text what was generated and what happened to the
> > > primaries. I have already written this program, and would like your
> > > feedback on how it works. This is a sample output from it, at
present,
> > > reading from a bggen generated hddm file. The vertex is 0,0,65
because
> it
> > > has not yet been simulated. Further decay vertices will show up as
soon
> > as
> > > these events are simulated. They will appear under their parent
> particle
> > in
> > > the listing as further indented lines. Please let me know if there
are
> > > improvements you would like to see to this scheme. I was planning to
> > > release this over the weekend, but got distracted by another HDGeant4
> > bug.
> > >
> > > Run 50141, event 2: Photon (8.564 GeV) Proton (0.938 GeV) ->
> > > Pi+, 1.104 GeV, beta=(-0.412,-0.035,0.902)
> > > Pi-, 6.723 GeV, beta=(0.070,0.043,0.996)
> > > Proton, 1.257 GeV, beta=(-0.011,-0.103,0.658)
> > > Pi+, 0.211 GeV, beta=(0.029,-0.544,-0.516)
> > > Pi-, 0.207 GeV, beta=(-0.052,-0.017,0.737)
> > > in the LiqH target (0.000,0.000,65.000)cm at 0.000 ns
> > > Run 50141, event 4: Photon (8.452 GeV) Proton (0.938 GeV) ->
> > > Pi+, 1.633 GeV, beta=(-0.161,0.050,0.982)
> > > Pi-, 1.795 GeV, beta=(0.421,-0.247,0.869)
> > > Pi0, 0.236 GeV, beta=(0.075,-0.060,0.815)
> > > Eta, 3.735 GeV, beta=(-0.045,0.043,0.987)
> > > Neutron, 1.703 GeV, beta=(-0.243,-0.012,0.798)
> > > Pi+, 0.289 GeV, beta=(0.243,0.823,0.174)
> > > in the liqH target (0.000,0.000,65.000)cm at 0.000 ns
> > > Run 50141, event 6: Photon (8.460 GeV) Proton (0.938 GeV) ->
> > > KShort, 2.929 GeV, beta=(-0.080,-0.025,0.982)
> > > KLong, 4.261 GeV, beta=(-0.033,0.053,0.991)
> > > Sigma+, 1.517 GeV, beta=(0.164,-0.084,0.593)
> > > KLong, 0.691 GeV, beta=(0.183,-0.041,0.668)
> > > in the GlueX spectrometer (0.000,0.000,65.000)cm at 0.000 ns
> > >
> > >
> > > On Tue, Mar 5, 2019 at 4:18 PM Sean Dobbs ***@***.***>
> > > wrote:
> > >
> > > > From Eugene:
> > > >
> > > > A common class for writing out HDDM thrown-level output would be
very
> > > > useful.
> > > > This could be implemented as a standalone library.
> > > >
> > > > Sean's suggestion: it would also be good to have a standalone
program
> > to
> > > > do this as well from some common input format
> > > >
> > > > —
> > > > You are receiving this because you are subscribed to this thread.
> > > > Reply to this email directly, view it on GitHub
> > > > <#43>, or mute the
> > > thread
> > > > <
> > >
> >
>
https://github.com/notifications/unsubscribe-auth/AHeFWM1qMDsimC27zlcjoBPuaxGbTXnsks5vTt8WgaJpZM4bfhQ3
> > > >
> > > > .
> > > >
> > >
> > > —
> > > You are receiving this because you were assigned.
> > > Reply to this email directly, view it on GitHub
> > > <
> >
>
#43 (comment)
> > >,
> > > or mute the thread
> > > <
> >
>
https://github.com/notifications/unsubscribe-auth/ABIJaj46yBQMt9xOCvXHEKq8gzk0tl-Qks5vTurRgaJpZM4bfhQ3
> > >
> > > .
> > >
> >
> > —
> > You are receiving this because you commented.
> > Reply to this email directly, view it on GitHub
> > <
>
#43 (comment)
> >,
> > or mute the thread
> > <
>
https://github.com/notifications/unsubscribe-auth/AHeFWNwsg7E_8mlP3UxcewL8vQJv9lCxks5vTuuhgaJpZM4bfhQ3
> >
> > .
> >
>
> —
> You are receiving this because you were assigned.
> Reply to this email directly, view it on GitHub
> <
#43 (comment)
>,
> or mute the thread
> <
https://github.com/notifications/unsubscribe-auth/ABIJaonKcw5yBtjZIRfj-XTX5u0Ur5ziks5vTzjXgaJpZM4bfhQ3
>
> .
>
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#43 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AHeFWKANwRcYpcwVT6wEK5PR-kK5Mk6uks5vTzvMgaJpZM4bfhQ3>
.
|
|
Well, the request was for a standard C++ class which could easily be used
by, for example, an already existing event generator.
…---Sean
On Tue, Mar 5, 2019 at 10:56 PM Richard Jones <[email protected]>
wrote:
Hello Sean,
What do you mean by "modular". Would a python module fit that description?
-Richard
On Tue, Mar 5, 2019 at 10:53 PM Sean Dobbs ***@***.***>
wrote:
> Richard,
>
> That sounds like a good idea. The only requirement is that the HDDM
output
> be modular (or at least that is what I got from the discussion at the
> meeting!)
>
> ---Sean
>
> On Tue, Mar 5, 2019 at 10:41 PM Richard Jones ***@***.***>
> wrote:
>
> > Sean,
> >
> > Would it be useful for me to write a short example program for writing
an
> > event generator?
> >
> > -Richard
> >
> > On Tue, Mar 5, 2019 at 5:11 PM Sean Dobbs ***@***.***>
> > wrote:
> >
> > > Hi Richard,
> > >
> > > That sounds like a great utility. For the record, Eugene's request
was
> > > more specifically about writing to HDDM, for example, for people
> writing
> > > their own event generator.
> > >
> > > ---Sean
> > >
> > > On Tue, Mar 5, 2019 at 5:08 PM Richard Jones <
***@***.***
> >
> > > wrote:
> > >
> > > > Hello Sean and all,
> > > >
> > > > I am working on the following utility that reads in any hddm file
and
> > > > prints out in plain text what was generated and what happened to
the
> > > > primaries. I have already written this program, and would like your
> > > > feedback on how it works. This is a sample output from it, at
> present,
> > > > reading from a bggen generated hddm file. The vertex is 0,0,65
> because
> > it
> > > > has not yet been simulated. Further decay vertices will show up as
> soon
> > > as
> > > > these events are simulated. They will appear under their parent
> > particle
> > > in
> > > > the listing as further indented lines. Please let me know if there
> are
> > > > improvements you would like to see to this scheme. I was planning
to
> > > > release this over the weekend, but got distracted by another
HDGeant4
> > > bug.
> > > >
> > > > Run 50141, event 2: Photon (8.564 GeV) Proton (0.938 GeV) ->
> > > > Pi+, 1.104 GeV, beta=(-0.412,-0.035,0.902)
> > > > Pi-, 6.723 GeV, beta=(0.070,0.043,0.996)
> > > > Proton, 1.257 GeV, beta=(-0.011,-0.103,0.658)
> > > > Pi+, 0.211 GeV, beta=(0.029,-0.544,-0.516)
> > > > Pi-, 0.207 GeV, beta=(-0.052,-0.017,0.737)
> > > > in the LiqH target (0.000,0.000,65.000)cm at 0.000 ns
> > > > Run 50141, event 4: Photon (8.452 GeV) Proton (0.938 GeV) ->
> > > > Pi+, 1.633 GeV, beta=(-0.161,0.050,0.982)
> > > > Pi-, 1.795 GeV, beta=(0.421,-0.247,0.869)
> > > > Pi0, 0.236 GeV, beta=(0.075,-0.060,0.815)
> > > > Eta, 3.735 GeV, beta=(-0.045,0.043,0.987)
> > > > Neutron, 1.703 GeV, beta=(-0.243,-0.012,0.798)
> > > > Pi+, 0.289 GeV, beta=(0.243,0.823,0.174)
> > > > in the liqH target (0.000,0.000,65.000)cm at 0.000 ns
> > > > Run 50141, event 6: Photon (8.460 GeV) Proton (0.938 GeV) ->
> > > > KShort, 2.929 GeV, beta=(-0.080,-0.025,0.982)
> > > > KLong, 4.261 GeV, beta=(-0.033,0.053,0.991)
> > > > Sigma+, 1.517 GeV, beta=(0.164,-0.084,0.593)
> > > > KLong, 0.691 GeV, beta=(0.183,-0.041,0.668)
> > > > in the GlueX spectrometer (0.000,0.000,65.000)cm at 0.000 ns
> > > >
> > > >
> > > > On Tue, Mar 5, 2019 at 4:18 PM Sean Dobbs <
***@***.***>
> > > > wrote:
> > > >
> > > > > From Eugene:
> > > > >
> > > > > A common class for writing out HDDM thrown-level output would be
> very
> > > > > useful.
> > > > > This could be implemented as a standalone library.
> > > > >
> > > > > Sean's suggestion: it would also be good to have a standalone
> program
> > > to
> > > > > do this as well from some common input format
> > > > >
> > > > > —
> > > > > You are receiving this because you are subscribed to this thread.
> > > > > Reply to this email directly, view it on GitHub
> > > > > <#43>, or mute
the
> > > > thread
> > > > > <
> > > >
> > >
> >
>
https://github.com/notifications/unsubscribe-auth/AHeFWM1qMDsimC27zlcjoBPuaxGbTXnsks5vTt8WgaJpZM4bfhQ3
> > > > >
> > > > > .
> > > > >
> > > >
> > > > —
> > > > You are receiving this because you were assigned.
> > > > Reply to this email directly, view it on GitHub
> > > > <
> > >
> >
>
#43 (comment)
> > > >,
> > > > or mute the thread
> > > > <
> > >
> >
>
https://github.com/notifications/unsubscribe-auth/ABIJaj46yBQMt9xOCvXHEKq8gzk0tl-Qks5vTurRgaJpZM4bfhQ3
> > > >
> > > > .
> > > >
> > >
> > > —
> > > You are receiving this because you commented.
> > > Reply to this email directly, view it on GitHub
> > > <
> >
>
#43 (comment)
> > >,
> > > or mute the thread
> > > <
> >
>
https://github.com/notifications/unsubscribe-auth/AHeFWNwsg7E_8mlP3UxcewL8vQJv9lCxks5vTuuhgaJpZM4bfhQ3
> > >
> > > .
> > >
> >
> > —
> > You are receiving this because you were assigned.
> > Reply to this email directly, view it on GitHub
> > <
>
#43 (comment)
> >,
> > or mute the thread
> > <
>
https://github.com/notifications/unsubscribe-auth/ABIJaonKcw5yBtjZIRfj-XTX5u0Ur5ziks5vTzjXgaJpZM4bfhQ3
> >
> > .
> >
>
> —
> You are receiving this because you commented.
> Reply to this email directly, view it on GitHub
> <
#43 (comment)
>,
> or mute the thread
> <
https://github.com/notifications/unsubscribe-auth/AHeFWKANwRcYpcwVT6wEK5PR-kK5Mk6uks5vTzvMgaJpZM4bfhQ3
>
> .
>
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
<#43 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABIJahTO0q2H8xQzCgPNlCRrIR7KP4uGks5vTzyJgaJpZM4bfhQ3>
.
|
|
Sean and all,
If someone else (not me) would write the interface spec for this class, I
will write the implementation part. Just the class definition part of the
header would be sufficient, I will fill in the necessary includes.
…-Richard J.
On Tue, Mar 5, 2019 at 10:59 PM Sean Dobbs ***@***.***> wrote:
Well, the request was for a standard C++ class which could easily be used
by, for example, an already existing event generator.
---Sean
On Tue, Mar 5, 2019 at 10:56 PM Richard Jones ***@***.***>
wrote:
> Hello Sean,
>
> What do you mean by "modular". Would a python module fit that
description?
>
> -Richard
>
> On Tue, Mar 5, 2019 at 10:53 PM Sean Dobbs ***@***.***>
> wrote:
>
> > Richard,
> >
> > That sounds like a good idea. The only requirement is that the HDDM
> output
> > be modular (or at least that is what I got from the discussion at the
> > meeting!)
> >
> > ---Sean
> >
> > On Tue, Mar 5, 2019 at 10:41 PM Richard Jones <
***@***.***>
> > wrote:
> >
> > > Sean,
> > >
> > > Would it be useful for me to write a short example program for
writing
> an
> > > event generator?
> > >
> > > -Richard
> > >
> > > On Tue, Mar 5, 2019 at 5:11 PM Sean Dobbs ***@***.***>
> > > wrote:
> > >
> > > > Hi Richard,
> > > >
> > > > That sounds like a great utility. For the record, Eugene's request
> was
> > > > more specifically about writing to HDDM, for example, for people
> > writing
> > > > their own event generator.
> > > >
> > > > ---Sean
> > > >
> > > > On Tue, Mar 5, 2019 at 5:08 PM Richard Jones <
> ***@***.***
> > >
> > > > wrote:
> > > >
> > > > > Hello Sean and all,
> > > > >
> > > > > I am working on the following utility that reads in any hddm file
> and
> > > > > prints out in plain text what was generated and what happened to
> the
> > > > > primaries. I have already written this program, and would like
your
> > > > > feedback on how it works. This is a sample output from it, at
> > present,
> > > > > reading from a bggen generated hddm file. The vertex is 0,0,65
> > because
> > > it
> > > > > has not yet been simulated. Further decay vertices will show up
as
> > soon
> > > > as
> > > > > these events are simulated. They will appear under their parent
> > > particle
> > > > in
> > > > > the listing as further indented lines. Please let me know if
there
> > are
> > > > > improvements you would like to see to this scheme. I was planning
> to
> > > > > release this over the weekend, but got distracted by another
> HDGeant4
> > > > bug.
> > > > >
> > > > > Run 50141, event 2: Photon (8.564 GeV) Proton (0.938 GeV) ->
> > > > > Pi+, 1.104 GeV, beta=(-0.412,-0.035,0.902)
> > > > > Pi-, 6.723 GeV, beta=(0.070,0.043,0.996)
> > > > > Proton, 1.257 GeV, beta=(-0.011,-0.103,0.658)
> > > > > Pi+, 0.211 GeV, beta=(0.029,-0.544,-0.516)
> > > > > Pi-, 0.207 GeV, beta=(-0.052,-0.017,0.737)
> > > > > in the LiqH target (0.000,0.000,65.000)cm at 0.000 ns
> > > > > Run 50141, event 4: Photon (8.452 GeV) Proton (0.938 GeV) ->
> > > > > Pi+, 1.633 GeV, beta=(-0.161,0.050,0.982)
> > > > > Pi-, 1.795 GeV, beta=(0.421,-0.247,0.869)
> > > > > Pi0, 0.236 GeV, beta=(0.075,-0.060,0.815)
> > > > > Eta, 3.735 GeV, beta=(-0.045,0.043,0.987)
> > > > > Neutron, 1.703 GeV, beta=(-0.243,-0.012,0.798)
> > > > > Pi+, 0.289 GeV, beta=(0.243,0.823,0.174)
> > > > > in the liqH target (0.000,0.000,65.000)cm at 0.000 ns
> > > > > Run 50141, event 6: Photon (8.460 GeV) Proton (0.938 GeV) ->
> > > > > KShort, 2.929 GeV, beta=(-0.080,-0.025,0.982)
> > > > > KLong, 4.261 GeV, beta=(-0.033,0.053,0.991)
> > > > > Sigma+, 1.517 GeV, beta=(0.164,-0.084,0.593)
> > > > > KLong, 0.691 GeV, beta=(0.183,-0.041,0.668)
> > > > > in the GlueX spectrometer (0.000,0.000,65.000)cm at 0.000 ns
> > > > >
> > > > >
> > > > > On Tue, Mar 5, 2019 at 4:18 PM Sean Dobbs <
> ***@***.***>
> > > > > wrote:
> > > > >
> > > > > > From Eugene:
> > > > > >
> > > > > > A common class for writing out HDDM thrown-level output would
be
> > very
> > > > > > useful.
> > > > > > This could be implemented as a standalone library.
> > > > > >
> > > > > > Sean's suggestion: it would also be good to have a standalone
> > program
> > > > to
> > > > > > do this as well from some common input format
> > > > > >
> > > > > > —
> > > > > > You are receiving this because you are subscribed to this
thread.
> > > > > > Reply to this email directly, view it on GitHub
> > > > > > <#43>, or mute
> the
> > > > > thread
> > > > > > <
> > > > >
> > > >
> > >
> >
>
https://github.com/notifications/unsubscribe-auth/AHeFWM1qMDsimC27zlcjoBPuaxGbTXnsks5vTt8WgaJpZM4bfhQ3
> > > > > >
> > > > > > .
> > > > > >
> > > > >
> > > > > —
> > > > > You are receiving this because you were assigned.
> > > > > Reply to this email directly, view it on GitHub
> > > > > <
> > > >
> > >
> >
>
#43 (comment)
> > > > >,
> > > > > or mute the thread
> > > > > <
> > > >
> > >
> >
>
https://github.com/notifications/unsubscribe-auth/ABIJaj46yBQMt9xOCvXHEKq8gzk0tl-Qks5vTurRgaJpZM4bfhQ3
> > > > >
> > > > > .
> > > > >
> > > >
> > > > —
> > > > You are receiving this because you commented.
> > > > Reply to this email directly, view it on GitHub
> > > > <
> > >
> >
>
#43 (comment)
> > > >,
> > > > or mute the thread
> > > > <
> > >
> >
>
https://github.com/notifications/unsubscribe-auth/AHeFWNwsg7E_8mlP3UxcewL8vQJv9lCxks5vTuuhgaJpZM4bfhQ3
> > > >
> > > > .
> > > >
> > >
> > > —
> > > You are receiving this because you were assigned.
> > > Reply to this email directly, view it on GitHub
> > > <
> >
>
#43 (comment)
> > >,
> > > or mute the thread
> > > <
> >
>
https://github.com/notifications/unsubscribe-auth/ABIJaonKcw5yBtjZIRfj-XTX5u0Ur5ziks5vTzjXgaJpZM4bfhQ3
> > >
> > > .
> > >
> >
> > —
> > You are receiving this because you commented.
> > Reply to this email directly, view it on GitHub
> > <
>
#43 (comment)
> >,
> > or mute the thread
> > <
>
https://github.com/notifications/unsubscribe-auth/AHeFWKANwRcYpcwVT6wEK5PR-kK5Mk6uks5vTzvMgaJpZM4bfhQ3
> >
> > .
> >
>
> —
> You are receiving this because you were assigned.
> Reply to this email directly, view it on GitHub
> <
#43 (comment)
>,
> or mute the thread
> <
https://github.com/notifications/unsubscribe-auth/ABIJahTO0q2H8xQzCgPNlCRrIR7KP4uGks5vTzyJgaJpZM4bfhQ3
>
> .
>
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#43 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AHeFWDVsRXSW79H-GyOJO-aEYQ8is7h8ks5vTz0wgaJpZM4bfhQ3>
.
|
|
Richard, |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
From Eugene:
A common class for writing out HDDM thrown-level output would be very useful.
This could be implemented as a standalone library.
Sean's suggestion: it would also be good to have a standalone program to do this as well from some common input format
The text was updated successfully, but these errors were encountered: