Differences between G3 and G4 in eta.pi #101
Comments
|
Carlos,
Can you share the generator output hddm file with me, that you are
injecting into hdgeant and hdgeant4?
…-Richard
On Thu, Apr 4, 2019 at 12:15 PM Carlos Salgado ***@***.***> wrote:
geantProblem.pdf
<https://github.com/JeffersonLab/HDGeant4/files/3044467/geantProblem.pdf>
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#101>, or mute the thread
<https://github.com/notifications/unsubscribe-auth/AHeFWPMP19wXdoyKnMJzg5Qysg19LSk6ks5vdiUYgaJpZM4cdMUY>
.
|
|
Carlos,
Ok, got it, will take a look when I get a chance.
…-Richard
On Thu, Apr 4, 2019 at 2:48 PM Carlos Salgado <notifications@github.com>
wrote:
Hello Richard,
The input file is at:
/w/halld-scifs17exp/halld2/home/salgado/EtaPi-W2MC/eventsW.hddm
That file was produced by genr8_2_hddm. Thank you for your help.
-Carlos
On Apr 4, 2019, at 1:44 PM, Richard Jones ***@***.***
***@***.***>> wrote:
Carlos,
Can you share the generator output hddm file with me, that you are
injecting into hdgeant and hdgeant4?
-Richard
On Thu, Apr 4, 2019 at 12:15 PM Carlos Salgado ***@***.***
***@***.***>>
wrote:
> geantProblem.pdf
> <https://github.com/JeffersonLab/HDGeant4/files/3044467/geantProblem.pdf>
>
> —
> You are receiving this because you are subscribed to this thread.
> Reply to this email directly, view it on GitHub
> <#101>, or mute the
thread
> <
https://github.com/notifications/unsubscribe-auth/AHeFWPMP19wXdoyKnMJzg5Qysg19LSk6ks5vdiUYgaJpZM4cdMUY>
> .
>
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub<
https://gcc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FJeffersonLab%2FHDGeant4%2Fissues%2F101%23issuecomment-479995813&data=02%7C01%7Csalgado%40jlab.org%7C990901ff662b49278cdd08d6b92523b7%7Cb4d7ee1f4fb34f0690372b5b522042ab%7C1%7C1%7C636899966495900328&sdata=AFPFDN0VXbb5TaKFJp5k6kxVsxwaNsR2dX9wsne3ZCo%3D&reserved=0>,
or mute the thread<
https://gcc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAIbNvit_Np3m0opSJRG0_e2ZROeyO38dks5vdjnngaJpZM4cdMUY&data=02%7C01%7Csalgado%40jlab.org%7C990901ff662b49278cdd08d6b92523b7%7Cb4d7ee1f4fb34f0690372b5b522042ab%7C1%7C1%7C636899966495910333&sdata=Y0cRrLDjvL6rYTYRRRfJeCkjRQuTfq%2BFhzeQGNNT8n4%3D&reserved=0>.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#101 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AHeFWI18OzPXSSw9arXNyBjIqerEh_oSks5vdkj4gaJpZM4cdMUY>
.
|
|
I believe #103 is the culprit. MCwrapper uses SKIP with input hddm files to ensure that when the project is split each job doesn't run over the same exact events repeatedly. My hypothesis is that for hdgeant4 the thrown is missing because they were never processed. Carlos can you rerun both G3 and G4 with only say, 1000 events. This will keep everything in one single file (SKIP=0) and would be a good way to test whether this is the issue or not |
|
I sat with Carlos and compared the first file produced which is essentially the test I recommended. I can confirm this is due to the broken SKIP in hdgeant4. Closing this issue |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
geantProblem.pdf
The text was updated successfully, but these errors were encountered: